GNOME Bugzilla – Bug 473819
crash in Evolution Mail: I was simply reading mes...
Last modified: 2007-09-05 21:48:02 UTC
What were you doing when the application crashed? I was simply reading messages, switching beetwen few of them. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 547909632 vsize: 547909632 resident: 36118528 share: 20692992 rss: 36118528 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188977609 rtime: 146 utime: 134 stime: 12 cutime:0 cstime: 4 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46977650460816 (LWP 4008)] [New Thread 1115703632 (LWP 4239)] [New Thread 1157667152 (LWP 4224)] [New Thread 1149274448 (LWP 4220)] [New Thread 1140881744 (LWP 4219)] [New Thread 1132489040 (LWP 4193)] [New Thread 1124096336 (LWP 4174)] [New Thread 1107310928 (LWP 4167)] [New Thread 1098918224 (LWP 4166)] [New Thread 1090525520 (LWP 4153)] [New Thread 1082132816 (LWP 4152)] (no debugging symbols found) 0x00002ab9ce6a2c7f in waitpid () from /lib/libpthread.so.0
+ Trace 160576
Thread 1 (Thread 46977650460816 (LWP 4008))
----------- .xsession-errors (93 sec old) --------------------- ** 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 ** Message: drive = 0 ** Message: volume = 0 evolution-shell-Message: Killing old version of evolution-data-server... --------------------------------------------------
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 431459 ***