Bug 892336

Summary: [abrt] evolution-data-server-3.6.2-3.fc18: g_malloc0: Process /usr/libexec/evolution-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Troy <troyatlarge>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: mbarnes, mcrha, mjs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:c7efe91db98bba720c6442ffd7c1e15047daaff3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:28:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Troy 2013-01-06 18:34:06 UTC 
Version-Release number of selected component:
evolution-data-server-3.6.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/evolution-calendar-factory
crash_function: g_malloc0
executable:     /usr/libexec/evolution-calendar-factory
kernel:         3.6.11-3.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Jan  3 10:16:30 localhost abrt[8567]: Saved core dump of pid 3806 (/usr/libexec/evolution-calendar-factory) to /var/spool/abrt/ccpp-2013-01-03-10:16:29-3806 (97665024 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_malloc0 at gmem.c:189
 #3 _g_dbus_worker_send_message at gdbusprivate.c:1621
 #4 g_dbus_connection_send_message_unlocked at gdbusconnection.c:1701
 #5 g_dbus_connection_send_message at gdbusconnection.c:1764
 #6 g_dbus_connection_emit_signal at gdbusconnection.c:5185
 #7 e_gdbus_signal_emission_hook_boolean at e-gdbus-templates.c:99
 #11 e_gdbus_cal_emit_readonly at e-gdbus-cal.c:1349
 #12 e_data_cal_report_readonly at e-data-cal.c:1468
 #13 e_cal_backend_notify_readonly at e-cal-backend.c:1904
 #19 g_object_notify_queue_thaw at gobject.c:291
Comment 1 Troy 2013-01-06 18:34:16 UTC 
Created attachment 673418 [details]
File: backtrace
Comment 2 Troy 2013-01-06 18:34:18 UTC 
Created attachment 673419 [details]
File: cgroup
Comment 3 Troy 2013-01-06 18:34:20 UTC 
Created attachment 673420 [details]
File: core_backtrace
Comment 4 Troy 2013-01-06 18:34:23 UTC 
Created attachment 673421 [details]
File: dso_list
Comment 5 Troy 2013-01-06 18:34:25 UTC 
Created attachment 673422 [details]
File: environ
Comment 6 Troy 2013-01-06 18:34:27 UTC 
Created attachment 673423 [details]
File: limits
Comment 7 Troy 2013-01-06 18:34:32 UTC 
Created attachment 673424 [details]
File: maps
Comment 8 Troy 2013-01-06 18:34:33 UTC 
Created attachment 673425 [details]
File: open_fds
Comment 9 Troy 2013-01-06 18:34:35 UTC 
Created attachment 673426 [details]
File: proc_pid_status
Comment 10 Milan Crha 2013-01-07 14:27:13 UTC 
Thanks for a bug report. I see this happened as a memory corruption bug, but the only thing I see in the backtrace is that you have setup two CalDAV calendars, which are currently idle, and the crashing thread is about to notify the client side about writability of one of your calendars after a network availability changed (when you either connected to the Internet/network, or disconnected from one).

Can you reproduce this (or similar crash, as memory corruption can reveal in any place) after certain steps, please?
Comment 11 Matthew Saltzman 2013-03-07 00:58:59 UTC 
Problem occurred when resuming from suspend.  The evolution window was open and evo was reconnecting to the network after NetworkManager reconnected.

backtrace_rating: 4
Package: evolution-data-server-3.6.3-2.fc18
OS Release: Fedora release 18 (Spherical Cow)
Comment 12 Fedora End Of Life 2013-12-21 10:13:02 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Fedora End Of Life 2014-02-05 14:28:11 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 14 Red Hat Bugzilla 2023-09-14 01:40:00 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days