GNOME Bugzilla – Bug 372798
crash in Evolution:
Last modified: 2006-11-12 23:55:12 UTC
What were you doing when the application crashed? Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 224768000 vsize: 0 resident: 224768000 share: 0 rss: 39714816 rss_rlim: 0 CPU usage: start_time: 1162962045 rtime: 0 utime: 7974 stime: 0 cutime:6061 cstime: 0 timeout: 1913 it_real_value: 0 frequency: 2928 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232157008 (LWP 1795)] [New Thread -1359905888 (LWP 2014)] [New Thread -1350722656 (LWP 1950)] [New Thread -1305719904 (LWP 1949)] [New Thread -1350456416 (LWP 1942)] [New Thread -1255236704 (LWP 1940)] [New Thread -1288934496 (LWP 1918)] [New Thread -1330898016 (LWP 1908)] [New Thread -1322505312 (LWP 1907)] [New Thread -1314112608 (LWP 1906)] [New Thread -1297327200 (LWP 1904)] [New Thread -1280414816 (LWP 1902)] [New Thread -1272022112 (LWP 1901)] [New Thread -1263629408 (LWP 1899)] [New Thread -1246844000 (LWP 1897)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 84618
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! Also, could you please add a description, what you were doing when the application crashed? [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
I've installed the following dbgsym packages and dependencies: evolution-plugins libgmime-2.0-2 libopensync0 mail-notification mail-notification-evolution opensync-plugin-evolution evolution-data-server-dbgsym evolution-dbgsym evolution-plugins evolution-plugins-dbgsym libgmime-2.0-2 libopensync0 mail-notification mail-notification-evolution mail-notification-evolution-dbgsym opensync-plugin-evolution opensync-plugin-evolution-dbgsym At the time of the crash I was viewing an email with two images (jpegs). I expanded the first to view inline, then hid it again. I then expanded the second to view inline at which point evolution crashed. In attempting to recreate the crash, I followed the same steps 3 times with no crash. However on completely opening the message (rather than using the preview pane) and using the same view tactics (preview inline, hide, preview second) I managed to cause the crash. Here's the output: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 209334272 vsize: 0 resident: 209334272 share: 0 rss: 32661504 rss_rlim: 0 CPU usage: start_time: 1163134972 rtime: 0 utime: 1955 stime: 0 cutime:1809 cstime: 0 timeout: 146 it_real_value: 0 frequency: 36 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232636240 (LWP 18990)] [New Thread -1289061472 (LWP 19019)] [New Thread -1359713376 (LWP 19018)] [New Thread -1331414112 (LWP 19017)] [New Thread -1339806816 (LWP 19015)] [New Thread -1348199520 (LWP 19008)] [New Thread -1322984544 (LWP 19003)] [New Thread -1314591840 (LWP 19002)] [New Thread -1306199136 (LWP 19001)] [New Thread -1297806432 (LWP 19000)] [New Thread -1272501344 (LWP 18997)] [New Thread -1264108640 (LWP 18996)] [New Thread -1255715936 (LWP 18995)] [New Thread -1247323232 (LWP 18994)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 84959
Thread 1 (Thread -1232636240 (LWP 18990))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 359803 ***