GNOME Bugzilla – Bug 440451
crash in Tasks:
Last modified: 2008-02-06 08:18:02 UTC
What were you doing when the application crashed? Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3167.fc7 #1 SMP Thu May 17 23:05:53 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 99172352 vsize: 99172352 resident: 37965824 share: 15659008 rss: 37965824 rss_rlim: 4294967295 CPU usage: start_time: 1179841130 rtime: 789 utime: 665 stime: 124 cutime:56 cstime: 24 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 -1208650016 (LWP 5236)] [New Thread -1278215280 (LWP 5335)] [New Thread -1247806576 (LWP 5280)] (no debugging symbols found) 0x0053d402 in __kernel_vsyscall ()
+ Trace 135523
Thread 2 (Thread -1278215280 (LWP 5335))
----------- .xsession-errors --------------------- Major opcode: 158 Minor opcode: 6 Resource id: 0x1408fbd X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1407ec0 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1407e61 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 Minor opcode: 0 Resource id: 0x1407e11 --------------------------------------------------
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, libgnome and libgnomeui (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
Unfortunately the stacktrace does not have any hints about the real cause of the crash and does not help in debugging this issue. For some yet unknown reason, such stacktraces are pretty common currently on certain distributions. However, almost all of them do turn out to be filed already, once we managed to gather a useful stacktrace. To do so, simply install the corresponding debugging packages and reproduce the issue, if possible. The resulting stacktrace (see bug-buddy details) will help us to identify and fix the issue. Just in case you ever can reproduce this crash later, please consider installing debugging packages [1] and either reopen this bug report or simply file a new one with the resulting stacktrace. Thanks! Closing this bug report as no further information has been provided.
*** Bug 460959 has been marked as a duplicate of this bug. ***
*** Bug 459714 has been marked as a duplicate of this bug. ***
*** Bug 470311 has been marked as a duplicate of this bug. ***
*** Bug 470173 has been marked as a duplicate of this bug. ***
*** Bug 470794 has been marked as a duplicate of this bug. ***
*** Bug 475191 has been marked as a duplicate of this bug. ***
*** Bug 508833 has been marked as a duplicate of this bug. ***