GNOME Bugzilla – Bug 368272
evolution-exchange crashed checking mail
Last modified: 2008-02-07 06:13:18 UTC
Steps to reproduce: It can't be reproduced reliably. Just during regular use, or non-use, it will crash. This time, I came back to my machine, unlocked my screensaver, and bug buddy was up showing me the crash. At that point evo was useless, so I closed it and started it again. It brought up the user interface, loaded my inbox, began filtering messages for junk, and poof! crashed again. Stack trace: Memory status: size: 80900096 vsize: 0 resident: 80900096 share: 0 rss: 22720512 rss_rlim: 0 CPU usage: start_time: 1162232125 rtime: 0 utime: 1134 stime: 0 cutime:965 cstime: 0 timeout: 169 it_real_value: 0 frequency: 0 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 -1208419984 (LWP 4620)] [New Thread -1210520688 (LWP 4622)] (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) (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) 0x00b5f402 in __kernel_vsyscall ()
+ Trace 80953
Thread 1 (Thread -1208419984 (LWP 4620))
Other information:
confirming as per duplicate
*** Bug 371986 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance! Also, attach gdb traces of evolution when evolution-exchange crashes and vice versa.
Ok, I've applied a bunch of FC6 updates since the original bug report, and our sysadmin rebooted the Exchange server to fix a faulty spam filter program ;), so the frequency of the crashes went down considerably, but it still happened again. I loaded the *-debug rpm packages and got what appears to be a more thorough stack trace. System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 67198976 vsize: 0 resident: 67198976 share: 0 rss: 12795904 rss_rlim: 0 CPU usage: start_time: 1164641605 rtime: 0 utime: 41 stime: 0 cutime:33 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/evolution-exchange' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208362640 (LWP 2297)] [New Thread -1210463344 (LWP 2298)] 0x00710402 in __kernel_vsyscall ()
+ Trace 89765
Thread 1 (Thread -1208362640 (LWP 2297))
I have also had this issue. Using 2.8.1 on Kubuntu Edgy on a 32bit dualcore system. Every session ends when Evolution loses connection to the Exchange connector. Since evolution does not crash there is no backtrace, but I did manage to get this from kdbg: (evolution-2.8:25593): libecal-WARNING **: e-cal.c:318: Unexpected response calendar-gui-Message: Check if default client matches (1170171835.19156.12@justin01 1170171835.19156.12@justin01) calendar-gui-Message: Check if default client matches (1170171835.19156.12@justin01 1170171835.19156.12@justin01) calendar-gui-Message: Check if default client matches (1170171835.19156.12@justin01 1170171835.19156.12@justin01) calendar-gui-Message: Check if default client matches (1170171835.19156.12@justin01 1170171835.19156.12@justin01) <exchange connector died here> There is no pattern to get the exchange connector to crash, but it happens anywhere from seconds to 15 minutes after opening evolution. The only fix is to kill all evolution-* processes and relaunch. This makes the program all but useless. Since I use an Exchange server and want an integrated client, it seems like having an XP VM is my only choice right now. This makes me unhappy. Thanks for the work, though. It is appreciated.
(In reply to comment #5) > I have also had this issue. Using 2.8.1 on Kubuntu Edgy on a 32bit dualcore > system. Every session ends when Evolution loses connection to the Exchange > connector. Since evolution does not crash there is no backtrace, but I did > manage to get this from kdbg: > > (evolution-2.8:25593): libecal-WARNING **: e-cal.c:318: Unexpected response > calendar-gui-Message: Check if default client matches > (1170171835.19156.12@justin01 1170171835.19156.12@justin01) > calendar-gui-Message: Check if default client matches > (1170171835.19156.12@justin01 1170171835.19156.12@justin01) > calendar-gui-Message: Check if default client matches > (1170171835.19156.12@justin01 1170171835.19156.12@justin01) > calendar-gui-Message: Check if default client matches > (1170171835.19156.12@justin01 1170171835.19156.12@justin01) > > <exchange connector died here> > > There is no pattern to get the exchange connector to crash, but it happens > anywhere from seconds to 15 minutes after opening evolution. The only fix is to > kill all evolution-* processes and relaunch. > > This makes the program all but useless. Since I use an Exchange server and want > an integrated client, it seems like having an XP VM is my only choice right > now. This makes me unhappy. > > Thanks for the work, though. It is appreciated. > Justin: Thanks for trying out exchange connection. A fix has been committed to 2.10.3 and 2.11.x branches for this. It is similar to bug#406155 and I have attached a fix in that bug. Would you mind giving it a try? TIA.
*** Bug 417967 has been marked as a duplicate of this bug. ***
*** Bug 467008 has been marked as a duplicate of this bug. ***
*** Bug 507562 has been marked as a duplicate of this bug. ***
bug 507562 was in 2.12
This would happen, if a mail would hit your mailbox and a filter action is triggered on it. This was a consistent crash and as reported could happen anytime and result in the storage process being killed. Already fixed in bug #420503. *** This bug has been marked as a duplicate of 420503 ***