GNOME Bugzilla – Bug 415011
crash in Evolution: Reading mail
Last modified: 2007-04-16 20:17:11 UTC
What were you doing when the application crashed? Reading mail Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 203968512 vsize: 0 resident: 203968512 share: 0 rss: 44875776 rss_rlim: 0 CPU usage: start_time: 1173120731 rtime: 0 utime: 769 stime: 0 cutime:739 cstime: 0 timeout: 30 it_real_value: 0 frequency: 0 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 -1232644432 (LWP 9416)] [New Thread -1331909728 (LWP 9451)] [New Thread -1319965792 (LWP 9435)] [New Thread -1311376480 (LWP 9434)] [New Thread -1302983776 (LWP 9433)] [New Thread -1279132768 (LWP 9432)] [New Thread -1270158432 (LWP 9427)] [New Thread -1261765728 (LWP 9424)] [New Thread -1253246048 (LWP 9423)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 116084
Thread 9 (Thread -1253246048 (LWP 9423))
Stack trace looks similar to Bug 367091 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! [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
Havent ben abel to redo the crash, but it sems to be the same as the other one. Evolution locks up when trying to open a mail whit an 8584x480 .jpg atachment. This is al the info i could grab from the terminal. (evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.8:7376): GdkPixbuf-CRITICAL **: gdk_pixbuf_loader_write: assertion `buf != NULL' failed (evolution-2.8:7376): e-attachment-bar.c-WARNING **: GdkPixbufLoader Error (evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter. (evolution-2.8:7376): camel-WARNING **: camel_exception_get_id called with NULL parameter.
Thanks, but we really need a stacktrace with debugging packages installed, as Akhil already asked for. The terminal output is unfortunately not enough information.
Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 206753792 vsize: 0 resident: 206753792 share: 0 rss: 49975296 rss_rlim: 0 CPU usage: start_time: 1173225965 rtime: 0 utime: 953 stime: 0 cutime:918 cstime: 0 timeout: 35 it_real_value: 0 frequency: 0 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 -1232963920 (LWP 12946)] [New Thread -1318978656 (LWP 12957)] [New Thread -1297020000 (LWP 12956)] [New Thread -1287902304 (LWP 12954)] [New Thread -1278870624 (LWP 12953)] [New Thread -1262085216 (LWP 12950)] [New Thread -1253565536 (LWP 12949)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 116475
Thread 1 (Thread -1232963920 (LWP 12946))
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 273386 ***