GNOME Bugzilla – Bug 462101
crash in Tasks: checking email on a huge...
Last modified: 2007-09-29 00:05:11 UTC
Version: 2.10 What were you doing when the application crashed? checking email on a huge INBOX Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 216092672 vsize: 216092672 resident: 122167296 share: 38629376 rss: 122167296 rss_rlim: 4294967295 CPU usage: start_time: 1185882408 rtime: 1844 utime: 1536 stime: 308 cutime:3 cstime: 8 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 -1208629536 (LWP 12607)] [New Thread -1269830768 (LWP 14204)] [New Thread -1305388144 (LWP 14122)] [New Thread -1259340912 (LWP 12641)] (no debugging symbols found) 0x0071c402 in __kernel_vsyscall ()
+ Trace 151794
Thread 1 (Thread -1208629536 (LWP 12607))
----------- .xsession-errors (52835 sec old) --------------------- ** (emerald:3276): WARNING **: failure: no device event controller found. ** (emerald:3276): WARNING **: failure: no device event controller found. ** (emerald:3276): WARNING **: failure: no device event controller found. ** (emerald:3276): WARNING **: failure: no device event controller found. (emerald:3276): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 ***