GNOME Bugzilla – Bug 516296
crash in Tasks: selecting a message (sin...
Last modified: 2008-02-14 18:19:43 UTC
What were you doing when the application crashed? selecting a message (single-click) Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Crux Memory status: size: 105000960 vsize: 105000960 resident: 23773184 share: 16875520 rss: 23773184 rss_rlim: 4294967295 CPU usage: start_time: 1202933941 rtime: 247 utime: 229 stime: 18 cutime:2 cstime: 3 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 -1209149728 (LWP 3108)] [New Thread -1253049456 (LWP 3203)] [New Thread -1283638384 (LWP 3202)] [New Thread -1230509168 (LWP 3145)] (no debugging symbols found) 0x00d12402 in __kernel_vsyscall ()
+ Trace 189102
Thread 1 (Thread -1209149728 (LWP 3108))
----------- .xsession-errors (2024 sec old) --------------------- gw connection dispose gw connection finalize gw connection dispose gw connection finalize gw connection dispose gw connection finalize gw connection dispose gw connection finalize gw connection dispose gw connection finalize gw connection dispose gw connection finalize gw connection dispose gw connection ...Too much output, ignoring rest... --------------------------------------------------
I think this bug could use a better trace report.
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 431459 ***