Bug 918680

Summary: [abrt] evolution-3.6.3-2.fc18: e_client_get_dbus_proxy: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Eric Harney <eharney>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: brian, jones.peter.busi, lucilanga, mail, mbarnes, mcatanzaro, mcrha, pebolle
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b46b0e595f5ef4d659d5531b8ad56314c548b486
Fixed In Version: evolution-data-server-3.8.0-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-06 18:58:54 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: build_ids
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
File: var_log_messages none

Description Eric Harney 2013-03-06 17:58:18 UTC 
Version-Release number of selected component:
evolution-3.6.3-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        evolution
crash_function: e_client_get_dbus_proxy
executable:     /usr/bin/evolution
kernel:         3.8.1-201.fc18.x86_64
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 e_client_get_dbus_proxy at e-client.c:1783
 #1 async_result_ready_cb at e-client.c:2025
 #2 g_simple_async_result_complete at gsimpleasyncresult.c:775
 #3 complete_in_idle_cb at gsimpleasyncresult.c:787
 #8 gtk_main at gtkmain.c:1160
Comment 1 Eric Harney 2013-03-06 17:58:20 UTC 
Created attachment 706175 [details]
File: backtrace
Comment 2 Eric Harney 2013-03-06 17:58:22 UTC 
Created attachment 706176 [details]
File: build_ids
Comment 3 Eric Harney 2013-03-06 17:58:24 UTC 
Created attachment 706177 [details]
File: cgroup
Comment 4 Eric Harney 2013-03-06 17:58:26 UTC 
Created attachment 706178 [details]
File: core_backtrace
Comment 5 Eric Harney 2013-03-06 17:58:28 UTC 
Created attachment 706179 [details]
File: dso_list
Comment 6 Eric Harney 2013-03-06 17:58:29 UTC 
Created attachment 706180 [details]
File: environ
Comment 7 Eric Harney 2013-03-06 17:58:31 UTC 
Created attachment 706181 [details]
File: limits
Comment 8 Eric Harney 2013-03-06 17:58:33 UTC 
Created attachment 706182 [details]
File: maps
Comment 9 Eric Harney 2013-03-06 17:58:34 UTC 
Created attachment 706183 [details]
File: open_fds
Comment 10 Eric Harney 2013-03-06 17:58:36 UTC 
Created attachment 706184 [details]
File: proc_pid_status
Comment 11 Eric Harney 2013-03-06 17:58:38 UTC 
Created attachment 706185 [details]
File: var_log_messages
Comment 12 Milan Crha 2013-03-06 18:58:54 UTC 
Thanks for a bug report. I think this is addressed with a change which is part of 3.6.4, which will be available in few days in updates testing. Please reopen, in case you'll see it with evolution-data-server-3.6.4-1. Thanks in advance.
Comment 13 Michael Catanzaro 2013-03-28 00:31:02 UTC 
Milan, I just got this with evolution 3.6.4-2 and evolution-data-server 3.6.4-2. I was switching from Calendar to email view (though I'm not sure if that's related). I don't seem to have permission to reopen the bug.
Comment 14 Milan Crha 2013-03-28 08:51:01 UTC 
Hrm, that's unfortunate. The change I was thinking of was about cancelling, where a similar crash could happen when a client cancelled pending operation. I thought this one was caused by something similar.

The code in question is gone in current upstream stable version, 3.8.0, which will be part of Fedora 19, which made the 3.6.x technically unsupported by upstream, thus I'm afraid there is noone able to look on this.
Comment 15 Milan Crha 2013-03-28 08:57:13 UTC 
*** Bug 927209 has been marked as a duplicate of this bug. ***
Comment 16 Brian J. Murrell 2013-03-28 12:30:48 UTC 
I guess there's no chance of getting an updated evolution to fix this in FC18?

It's really not feasible for me (or probably most users) to chase Rawhide.  :-(
Comment 17 Milan Crha 2013-03-29 08:27:04 UTC 
Evolution 3.8.x is buildable on Fedora 18, but we usually stick evolution version with Fedora version base don the time of release. I would look on this, but I cannot reproduce this on my will, I got it ~once per month, sometimes even not that "often".

I understand the issue with rawhide, I picked this resolution only due to lack of "will be in Fedora 19", which will be released in couple weeks (it's in alpha stage currently).
Comment 18 Paul Bolle 2013-06-03 07:52:32 UTC 
(In reply to Milan Crha from comment #17)
> I would look on this, but I cannot reproduce this on my will, I got it ~once
> per month, sometimes even not that "often".

0) I just switched (from F17) to F18 two days ago (I finally got bored enough to set myself to make that switch). So now I'm running evolution-3.6.4-3.fc18 and  evolution-data-server-3.6.4-4.fc18. And since the switch I seem to hit this crash at least once a day. abrt gets a bit in the way of seeing what happened when, but my short two day experience puts the hit rate between once every hour of uptime and once per calendar day.

1) Is there anything particular I should test?
Comment 19 Peter H. Jones 2013-07-11 23:04:17 UTC 
I got this when I tried to get a Week display with and event on Sunday that would run beyond the window. Evolution crashed when I tried to use the scroll bar to see the event in question. Haven't tried more than once, yet.
Comment 20 Peter H. Jones 2013-11-21 20:41:10 UTC 
I've just hit this bug several times in a row. If the bug isn't going to be fixed in FC18, is there a way to check the calendar files for corruption that would be triggering the bug?
Comment 21 Peter H. Jones 2013-11-21 21:09:49 UTC 
When I started evolution from a command line, I got the following messages:

"(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare

(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare

(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare

(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare

(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare

(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare

(evolution:2855): libecal-CRITICAL **: UID 20121011T205647Z-2198-1000-2196-260: instance RECURRENCE-ID (null) + detached instance RECURRENCE-ID 20131121T120000: cannot compare"

Also, I note that the versions of the client, 3.6.4-3, and server, 3.6.4-4 seem misaligned:
"# yum list 'evolution*'
Loaded plugins: changelog, fastestmirror, langpacks, presto, refresh-packagekit, security
Loading mirror speeds from cached hostfile
 * fedora: fedora.mirror.iweb.com
 * rpmfusion-free: mirror.us.leaseweb.net
 * rpmfusion-free-updates: mirror.us.leaseweb.net
 * rpmfusion-nonfree: mirror.us.leaseweb.net
 * rpmfusion-nonfree-updates: mirror.us.leaseweb.net
 * updates: fedora.mirror.iweb.com
Installed Packages
evolution.x86_64                   3.6.4-3.fc18    @/evolution-3.6.4-3.fc18.x86_64               
evolution-data-server.x86_64       3.6.4-4.fc18    @/evolution-data-server-3.6.4-4.fc18.x86_64   
evolution-data-server-devel.x86_64 3.6.4-4.fc18    @/evolution-data-server-devel-3.6.4-4.fc18.x86_64
evolution-ews.x86_64               3.6.4-1.fc18    @/evolution-ews-3.6.4-1.fc18.x86_64           
evolution-help.noarch              3.6.4-3.fc18    @/evolution-help-3.6.4-3.fc18.noarch          
Available Packages
evolution.i686                     3.6.4-3.fc18    updates                                       
evolution-bogofilter.x86_64        3.6.4-3.fc18    updates                                       
evolution-data-server.i686         3.6.4-4.fc18    updates                                       
evolution-data-server-devel.i686   3.6.4-4.fc18    updates                                       
evolution-data-server-doc.noarch   3.6.4-4.fc18    updates                                       
evolution-devel.i686               3.6.4-3.fc18    updates                                       
evolution-devel.x86_64             3.6.4-3.fc18    updates                                       
evolution-ews.i686                 3.6.4-1.fc18    updates                                       
evolution-mapi.i686                3.6.4-1.fc18    updates                                       
evolution-mapi.x86_64              3.6.4-1.fc18    updates                                       
evolution-mapi-devel.i686          3.6.4-1.fc18    updates                                       
evolution-mapi-devel.x86_64        3.6.4-1.fc18    updates                                       
evolution-perl.x86_64              3.6.4-3.fc18    updates                                       
evolution-pst.x86_64               3.6.4-3.fc18    updates                                       
evolution-rspam.x86_64             0.6.0-3.fc18    updates                                       
evolution-rss.x86_64               1:0.3.92-2.fc18 updates                                       
evolution-spamassassin.x86_64      3.6.4-3.fc18    updates                                       
#"

Would that explain the problems?
Comment 22 Peter H. Jones 2013-11-21 21:22:50 UTC 
According to http://fedoraforum.org/forum/showthread.php?t=274384, my calendar is at $HOME/.local/share/evolution/calendar.ics. Perhaps I could edit the file to get rid of the error messages. Of course, I'd make backups of all the files listed in the aformentioned article.
Comment 23 Milan Crha 2013-11-22 10:15:14 UTC 
(In reply to Peter H. Jones from comment #21)
> Also, I note that the versions of the client, 3.6.4-3, and server, 3.6.4-4
> seem misaligned:

They are still 3.6.4, and the micro version difference (-3 versus -4) is not problem, it only means that one of them has been built more times than the other).

(In reply to Peter H. Jones from comment #22)
> According to http://fedoraforum.org/forum/showthread.php?t=274384, my
> calendar is at $HOME/.local/share/evolution/calendar.ics. Perhaps I could
> edit the file to get rid of the error messages. Of course, I'd make backups
> of all the files listed in the aformentioned article.

Well, it depends on the calendar type. Those under On This Computer are there, others are at ~/.cache/evolution/calendar, but those are updated from the server when the calendar is opened.