GNOME Bugzilla – Bug 448630
crash in Tasks: I brought up the message...
Last modified: 2007-06-19 14:59:34 UTC
What were you doing when the application crashed? I brought up the message filters, then clicked cancel. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (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: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 136241152 vsize: 136241152 resident: 51863552 share: 34263040 rss: 51863552 rss_rlim: 4294967295 CPU usage: start_time: 1182060592 rtime: 4836 utime: 4331 stime: 505 cutime:56 cstime: 14 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 -1208437024 (LWP 3062)] [New Thread -1228428400 (LWP 18403)] [New Thread -1239585904 (LWP 12519)] [New Thread -1249408112 (LWP 3075)] (no debugging symbols found) 0x00b91402 in __kernel_vsyscall ()
+ Trace 141759
Thread 1 (Thread -1208437024 (LWP 3062))
----------- .xsession-errors (62120 sec old) --------------------- Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". Xlib: extension "DPMS" missing on display ":0.0". Xlib: extension "MIT-SCREEN-SAVER" missing on display ":0.0". ...Too much output, ignoring rest... --------------------------------------------------
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. Could you please install some debugging packages [1], start the application as normal, 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 in advance! [1] debugging packages for evolution, evolution-data-server, gtkhtml, gtk, glib, gnome-vfs, pango, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
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 436128 ***