GNOME Bugzilla – Bug 460713
crash in Evolution Mail: sending a goddamn email.
Last modified: 2007-08-01 14:05:52 UTC
What were you doing when the application crashed? sending a goddamn email. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-686 #1 SMP Wed Jul 11 03:53:02 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: Mist Memory status: size: 238620672 vsize: 238620672 resident: 100913152 share: 20799488 rss: 100913152 rss_rlim: 4294967295 CPU usage: start_time: 1185295105 rtime: 14266 utime: 13098 stime: 1168 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232255312 (LWP 5955)] [New Thread -1318138992 (LWP 17363)] [New Thread -1328002160 (LWP 6438)] [New Thread -1309357168 (LWP 5977)] [New Thread -1300968560 (LWP 5976)] [New Thread -1292579952 (LWP 5975)] [New Thread -1284191344 (LWP 5973)] [New Thread -1274020976 (LWP 5972)] [New Thread -1265632368 (LWP 5971)] [New Thread -1257243760 (LWP 5970)] [New Thread -1247347824 (LWP 5969)] [New Thread -1237836912 (LWP 5961)] 0xb77eeae1 in ?? () from /lib/libpthread.so.0
+ Trace 150782
Thread 1 (Thread -1232255312 (LWP 5955))
----------- .xsession-errors (94034 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 410823 ***