GNOME Bugzilla – Bug 467199
crash in Tasks:
Last modified: 2007-09-21 18:51:29 UTC
What were you doing when the application crashed? 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 161787904 vsize: 161787904 resident: 54386688 share: 23580672 rss: 54386688 rss_rlim: 4294967295 CPU usage: start_time: 1187092809 rtime: 8952 utime: 7424 stime: 1528 cutime:73 cstime: 41 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209002272 (LWP 3173)] [New Thread -1296143472 (LWP 4304)] [New Thread -1317123184 (LWP 3528)] [New Thread -1294419056 (LWP 3249)] [New Thread -1225634928 (LWP 3205)] (no debugging symbols found) 0x00cbd402 in __kernel_vsyscall ()
+ Trace 155574
Thread 2 (Thread -1296143472 (LWP 4304))
----------- .xsession-errors --------------------- ** (evolution:3173): WARNING **: failure: no device event controller found. (l)user is reading mail formatting out ** (evolution:3173): WARNING **: failure: no device event controller found. Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized ** (bug-buddy:4307): WARNING **: failure: no device event controller found. --------------------------------------------------
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to this bug. Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Could you please install some debugging packages [1] and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks! [1] debugging packages for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
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 460409 ***