GNOME Bugzilla – Bug 469626
crash in 3x?? / g_slice_free1 / libgtk-x11 / g_list_foreach
Last modified: 2008-01-18 21:32:44 UTC
Version: 2.10 What were you doing when the application crashed? 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Gion Memory status: size: 692355072 vsize: 692355072 resident: 70234112 share: 47124480 rss: 70234112 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187882141 rtime: 542 utime: 412 stime: 130 cutime:61 cstime: 86 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496476304 (LWP 6440)] [New Thread 1168415056 (LWP 6819)] [New Thread 1157925200 (LWP 6818)] [New Thread 1136945488 (LWP 6545)] [New Thread 1105475920 (LWP 6537)] [New Thread 1094719824 (LWP 6536)] (no debugging symbols found) 0x0000003016e0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 157397
Thread 1 (Thread 46912496476304 (LWP 6440))
----------- .xsession-errors (17187 sec old) --------------------- (gnome-background-properties:4062): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-background-properties:4062): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-background-properties:4062): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-background-properties:4062): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid ...Too much output, ignoring rest... --------------------------------------------------
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
Probably fedora specific and related to bug 426227 or bug 426807 or bug 426807 and their friends.
*** Bug 457231 has been marked as a duplicate of this bug. ***
*** Bug 470915 has been marked as a duplicate of this bug. ***
*** Bug 475933 has been marked as a duplicate of this bug. ***
*** Bug 477670 has been marked as a duplicate of this bug. ***
*** Bug 476780 has been marked as a duplicate of this bug. ***
Created attachment 96120 [details] Data from bugbuddy on this crash which occured while receiving email
*** Bug 494855 has been marked as a duplicate of this bug. ***
It's most likely that this particular bug is the fedora specific bug 447591 since 4 out of 6 dups show: GLib-GObject-WARNING **: gsignal.c:1669: signal `source_selected' is invalid for instance 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. As debug symbols are missing, it's just a guess anyway since we can't determine the issue without debug information. Feel free to install debug information and open a new bug. See http://live.gnome.org/GettingTraces for details *** This bug has been marked as a duplicate of 447591 ***
*** Bug 508322 has been marked as a duplicate of this bug. ***
*** Bug 510293 has been marked as a duplicate of this bug. ***