GNOME Bugzilla – Bug 501132
crash in Evolution: mse_get_folder_online_sync_updates at mail-stub-exchange.c:579?
Last modified: 2011-05-02 16:34:27 UTC
What were you doing when the application crashed? Starting up evolution with an exchange account attached. The evolution backend consistently crashes (every time). The front end continues to operate fine, although I can't use the exchange account of course. Before the crash there is usually time for evolution to grab a few new emails from the exchange server so there is some communication successfully occuring. Sorry this isn't with a -dbg build. Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22custom1.0 #1 SMP Sun Dec 2 14:17:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Default Icon Theme: gnome Memory status: size: 66375680 vsize: 66375680 resident: 15241216 share: 10153984 rss: 15241216 rss_rlim: 4294967295 CPU usage: start_time: 1196640048 rtime: 47 utime: 41 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb66666b0 (LWP 16871)] [New Thread 0xb4bb8b90 (LWP 16927)] [New Thread 0xb63fcb90 (LWP 16872)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 180475
Thread 2 (Thread 0xb4bb8b90 (LWP 16927))
----------- .xsession-errors --------------------- cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer cairo context error: NULL pointer Playing WAVE '/home/jamesm/sounds/pop.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono Playing WAVE '/home/jamesm/sounds/pop.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono Playing WAVE '/home/jamesm/sounds/pop.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono (gnome-terminal:4190): Vte-WARNING **: No handler for control sequence `device-control-string' defined. Playing WAVE '/home/jamesm/sounds/pop.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono --------------------------------------------------
Hi. Thanks for that bugreport. Although you don't have debug symbols we can see it's the function mse_get_folder_online_sync_updates which crashes and it seems as if its not know so far. At least bugzilla doesn't return any hits for that query string. But could you please get us a stacktrace with debug symbols? And what version of exchange are you using? Do you have any 'special' mails in your inbox? Like with uncommon subjects or the like..?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
Oh, sorry, somehow I never saw the comment on 4/12/2008 (maybe it got eaten by my spam filter). Apologies. I'll answer all questions I can. I've updated exchange since then and the problem still occurs. 1) Version of exchange (currently) is 2.12.2 (debian build 2.12.2-1+b1 on i386) 2) There are no special symbols in any of the emails in my inbox...in fact, there are just 7 emails. There are a few hundred emails in two other folders (Saved Items and Sent Items) though...but none have anything but standard ascii characters in the subject lines. 3) Debug info - sorry for my ignorance, but how on earth do I provide this information. Debian provides evolution-dbg and evolution-exchange-dbg packages that I can install. I gather that they simply populate /usr/lib/debug/usr/...with unstripped binaries and libraries but I can't figure out how to actually use them...If you can provide some guidance I'll get you the stacktrace.
Hi :) with respect to debug info: You are right with that -dgb packages. Just install them and make evolution crash. Then bugbuddy pops up and you can gather a stacktrace with a click on "Review Crash Details" or the like. Please see http://live.gnome.org/GettingTraces for more details. Thanks in advance! @bruno: would you mind to NOT CLOSE bugs after 4 weeks of no response?
Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23custom1.0 #1 SMP Tue Dec 18 16:04:06 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Default Icon Theme: gnome Memory status: size: 39137280 vsize: 39137280 resident: 12161024 share: 9695232 rss: 12161024 rss_rlim: 4294967295 CPU usage: start_time: 1200013186 rtime: 24 utime: 20 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb66516b0 (LWP 24514)] [New Thread 0xb63e2b90 (LWP 24516)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 184878
Thread 1 (Thread 0xb66516b0 (LWP 24514))
----------- .xsession-errors (527 sec old) --------------------- gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00c9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00da gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 00e9 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0144 gpilotd-Message: Using net TRUE gpilotd-Message: Found 054c, 0169 gpilotd-Message: Using net TRUE gpilotd-Message: Found 12ef, 0100 gpilotd-Message: Using net TRUE --------------------------------------------------
Thanks for that stacktrace. But it seems to be another crash :( I am sorry for not having mentioned that I'd like you to not paste the stacktrace as a message but rather attach it to the bug. Also, it would be nice to have debug symbols for evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, libgnome and libgnomeui (as far as those packages are provided by your distribution). The second stacktrace might be bug 506838 or bug 484101. But I'd like you to collect further stacktraces and attach them here in order to determine the issue for your crashers. You say, you can't use Evolution-Exchange at all. Have tried to start over by moving your ~/.evolution/ directory out and removing (after saving of course) your /apps/evolution/ gconf keys?
Created attachment 102561 [details] Evolution crash stack trace I've installed dbg packages (no libgnome-*-dbg packages seem to exist): $dpkg -l *-dbg |grep ii ii evolution-data-server-dbg 1.12.2-1 ii evolution-dbg 2.12.2-1+b1 ii evolution-exchange-dbg 2.12.2.dfsg-1 ii libglib1.2-dbg 1.2.10-19 ii libgnomeui-0-dbg 2.20.1.1-1 ii libgnomevfs2-0-dbg 1:2.20.1-1 ii libgtk2.0-0-dbg 2.12.3-2 ii libgtkhtml3.14-dbg 3.16.1-1
I agree that the behaviour I'm reporting is very similar to that in bug 484101 and possibly 506838 but the latter has not much information in the "what were you doing" section. I have in the past tried moving .evolution out of the way and, for various other evolution instabilities it has helped. I'm not sure if I attempted to do so to fix this problem, but I suspect I did. However, I'll do so again and also clear out the gconf data. I'll get back to you with the results of that as soon as I can. Thank you.
Good news... I've just restarted evolution with a fresh (apart from local mail store which contains 10,000+ messages which I can't delete) ~/.evolution and a clean out of gconf keys, and, for the time being, I can access my exchange account. So, I've managed to "fix" the crashes I was experiencing, but it seems there may be something interesting in the traces I've provided you that indicates some underlying bug. I'll re-post to this bug if evolution develops the problem again. I hope the stack traces I sent are of some use. Cheers James
Hi :) Thanks for your contributions! Have you backed up your gconf keys and ~/.evolution and can you make Evolution crash by restoring them? If so, I guess the data would be interesting for reproducing the issue. Adding STACKTRACE in order to make developers notice this bugreport having a good stacktrace.
*** Bug 543185 has been marked as a duplicate of this bug. ***
last dup in 2.22.x
I've upgraded to Evolution 2.22.3.1, and this appears to resolve the issue I reported in Bug 543185 (marked DUPLICATE of this case).
*** Bug 527335 has been marked as a duplicate of this bug. ***
bug 527335 has really good traces
*** Bug 573372 has been marked as a duplicate of this bug. ***
I uploaded a test patch to bug #561332, which touches this part as well. Maybe we will be able to mark as a duplicate, once confirmed it is.
https://bugs.launchpad.net/bugs/358227 has a similar crash on GNOME 2.26
*** Bug 603618 has been marked as a duplicate of this bug. ***
Setting to need-info, please retest with actual stable, which is 2.32.2.