GNOME Bugzilla – Bug 485694
crash in Tasks: sending an email
Last modified: 2007-10-14 15:34:02 UTC
What were you doing when the application crashed? sending an email 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: No Accessibility: Enabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 166109184 vsize: 166109184 resident: 38920192 share: 22609920 rss: 38920192 rss_rlim: 4294967295 CPU usage: start_time: 1192099913 rtime: 1734 utime: 1390 stime: 344 cutime:29 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 -1208916256 (LWP 31788)] [New Thread -1288926320 (LWP 32055)] [New Thread -1343153264 (LWP 32053)] [New Thread -1353643120 (LWP 32047)] [New Thread -1256563824 (LWP 31898)] [New Thread -1267180656 (LWP 31850)] [New Thread -1278436464 (LWP 31846)] (no debugging symbols found) 0x00a95402 in __kernel_vsyscall ()
+ Trace 169472
Thread 1 (Thread -1208916256 (LWP 31788))
----------- .xsession-errors --------------------- ** (evolution:31788): WARNING **: failure: no device event controller found. ** (evolution:31788): WARNING **: failure: no device event controller found. ** (evolution:31788): WARNING **: failure: no device event controller found. ** (evolution:31788): WARNING **: failure: no device event controller found. Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 426227 ***