GNOME Bugzilla – Bug 344391
Evolution repeatedly crashes
Last modified: 2006-06-26 10:33:35 UTC
Distribution: Fedora Core release 5 (Bordeaux) Package: Evolution Severity: major Version: GNOME2.14.2 2.6.x Gnome-Distributor: Red Hat, Inc Synopsis: Evolution repeatedly crashes Bugzilla-Product: Evolution Bugzilla-Component: Miscellaneous Bugzilla-Version: 2.6.x BugBuddy-GnomeVersion: 2.0 (2.14.1) Description: Description of the crash: Started the evolution client; then it crashed. Not sure why Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/evolution-2.6' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208777024 (LWP 8118)] [New Thread -1416922208 (LWP 8131)] [New Thread -1406432352 (LWP 8130)] [New Thread -1329681504 (LWP 8128)] [New Thread -1319191648 (LWP 8127)] [New Thread -1308496992 (LWP 8126)] [New Thread -1287124064 (LWP 8125)] [New Thread -1298007136 (LWP 8124)] [New Thread -1276617824 (LWP 8121)] (no debugging symbols found) 0x480aa402 in __kernel_vsyscall ()
+ Trace 68751
Thread 3 (Thread -1406432352 (LWP 8130))
------- Bug created by bug-buddy at 2006-06-09 12:41 -------
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug. How often does this happen? Always, often, sometimes? Do you start in mailer view? What kind of accounts do you use? Exchange, i guess? Unique stacktrace according to simple-dup-finder.
(Bug 344700 looks like it has a similar stack trace that may be a duplicate)
*** Bug 344700 has been marked as a duplicate of this bug. ***
Aditional information: It happens all the time. I would say since upgrading to this version (from whatever was stable 1 month ago) it happens every 15 min. I always start in mailer view, but it seems to crash/hang when its communicating with the exchange server. Mostly when its reveicing a message. Yes it is using the exchange connector.
*** Bug 344762 has been marked as a duplicate of this bug. ***
*** Bug 344763 has been marked as a duplicate of this bug. ***
Created attachment 67263 [details] strace of evolution I did an `strace -f` on evolution. This is an example of when evolution would hang forever. I had to kill it after a quite a few min. It looks like a deadlock on a futex.
Created attachment 67266 [details] `strace -f` example of when it crashed This is the `strace -f` output from when evolution crashed. I started evolution and waited for it to refresh all its exchange folders.
*** Bug 345364 has been marked as a duplicate of this bug. ***
switching from mail to calendar view displays the following error: (evolution-2.6:5884): libecal-WARNING **: e-cal.c:291: Unexpected response
Opening up the preferences window to comfirm auto completion is of displays the following error: (evolution-2.6:5884): e-utils-WARNING **: Cannot resolve symbol 'org_gnome_new_mail_config' in plugin '/usr/lib/evolution/2.6/plugins/liborg-gnome-new-mail-notify.so' (not exported?) BBDB spinning up...
Test mail sent to mailbox on exchange was sent but has not appeared in evolution. The mail is visable in the web interface. I don't see any obvious errors when doing Send/Receive. I have another user also experiencing a similar thing on aother upto date FC5 install. Will try and see if gdb trace will show any problems.
restarting evolution does refresh the mailbox contents correctly
While running `gdb evolution`, moved some mail between exchange mailbox and a local imap mailbox and CPU utilization of evolution hits 99%+. (I think I have done this write) Ctrl-c to get back to gdb prompt and ran "thread apply all bt" output follows. <<< 9 <<< 100 <<< 0 <<< 10 <<< personal/Trash <<< 11 <<< (personal/Trash) [Thread -1366324320 (LWP 6270) exited] >>> 9 >>> personal/Inbox >>> "0000007c4921" --- <<< 1 <<< 192556 bytes <<< 0 >>> 7 >>> (personal/Inbox) >>> "0000007c4921" >>> 16 >>> 16 --- >>> 7 >>> (personal/Inbox) >>> "0000007c4921" >>> 4294967295 >>> 18 --- >>> 9 >>> (personal/Inbox) >>> "0000007c491c" --- <<< 1 <<< 84884 bytes Program received signal SIGINT, Interrupt. [Switching to Thread -1208371520 (LWP 6258)] 0x4d2cb402 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 68937
Assigning it to Sushma and adding whiteboard term evolution[connector]. I have used this term for consistency - but think exchange would be a better alternative.
One other piece of information, at least with my crash, our IT department upgraded the exchange server to Service Pack 2. It was after then that the evolution began to fail. I then upgraded evolution to the latest released version and now it crashes everytime I start it.
Not sure if this has any effect on the issue but looked into errors I get regarding the NetworkManager: libnm_glib_nm_state_cb: dbus returned an error. (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files Started the NetworkManager daemon and they have gone away. It looks like this is not started by default on an FC5 install.
FYI: We are running Exchange 2000, SP3 (version 6.0 - Built 6429.4) We have the latest hotfix over SP3. (that was done long time ago, more than 1 year ago). But the three of us in this department who use evolution started noticing major issues with evolution after a recent evolution/gnome upgrade done a couple weeks ago. I would also say that the exchange server a few weeks ago got considerably slower (even for those using outlook), so perhaps there is something to do with the timeouts.
I would agree with Paul here, my failures did coincide with the latest evolution upgrade I did around the same time frame ( ~2 weeks ago). The exchange server was also updated that weekend, so wasn't sure which came first. My version of evolution is: evolution-2.6.2-1.fc5.5
Same here, did not experience the level of problems with the original FC5 evolution version evolution-2.6.0-1.i386.rpm evolution-connector-2.5.92-1.i386.rpm evolution-data-server-1.5.92-1.i386.rpm Currently running: evolution-data-server-1.6.2-1.fc5.1 evolution-connector-2.6.2-1.fc5.4 evolution-2.6.2-1.fc5.5
firewall problem ? enabled all udp traffic between client and server and look to now have a more stable connection. Have been seeing ICMP Dest unreachable in ethereal output.
Seeing the following errors while moving mail: (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: x1bdd7cd (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: x1e3b35d (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: xde69d (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: xd8e8d (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: xd8e8d (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: xd8e8d (evolution-2.6:18425): gtkhtml-WARNING **: invalid character value: xd8e8d
Hmmm, Still getting this and loosing connection: camel-exchange-provider-ERROR **: file camel-exchange-store.c: line 1098 (stub_notification): should not be reached aborting... Xlib: unexpected async reply (sequence 0x7e600)!
Latest debug output: Backtrace was generated from '/usr/libexec/evolution-exchange' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209026880 (LWP 25026)] [New Thread -1211126880 (LWP 25027)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x4d2cb402 in ?? ()
+ Trace 69062
Thread 1 (Thread -1209026880 (LWP 25026))
run Starting program: /usr/bin/evolution Reading symbols from shared object read from target memory...done. Loaded system supplied DSO at 0x4d2cb000 [Thread debugging using libthread_db enabled] [New Thread -1208211776 (LWP 25945)] CalDAV Eplugin starting up ... [New Thread -1266799712 (LWP 25948)] [Thread -1266799712 (LWP 25948) exited] Detaching after fork from child process 25952. [New Thread -1266799712 (LWP 25953)] [New Thread -1277682784 (LWP 25954)] [Thread -1266799712 (LWP 25953) exited] [New Thread -1266799712 (LWP 25955)] [New Thread -1288193120 (LWP 25956)] [New Thread -1298682976 (LWP 25957)] [New Thread -1309172832 (LWP 25958)] [New Thread -1330152544 (LWP 25960)] [New Thread -1319662688 (LWP 25959)] [New Thread -1340642400 (LWP 25961)] [Thread -1340642400 (LWP 25961) exited] [New Thread -1340642400 (LWP 25962)] Program received signal SIGPIPE, Broken pipe. [Switching to Thread -1309172832 (LWP 25958)] 0x4d2cb402 in __kernel_vsyscall () (gdb) (gdb) thread apply all bt
+ Trace 69063
Another set of duplicates of 344196 *** This bug has been marked as a duplicate of 344196 ***