GNOME Bugzilla – Bug 317687
gnome-panel crash by clicking on settings
Last modified: 2011-02-04 16:20:07 UTC
From: <> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.10.0 Subject: gnome-panel crash by clicking on settings Distribution: Debian testing/unstable Package: gnome-panel Severity: critical Version: GNOME2.10.2 2.10.x Gnome-Distributor: Debian Synopsis: gnome-panel crash by clicking on settings Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: Steps to reproduce the crash: 1. On panel right-click for settings 2. The settings dialog appears but also gnome-panel crashes. 3. Expected Results: Dialog appears and settings to the panel can be made. How often does this happen? always. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223317280 (LWP 3769)] [New Thread -1236407376 (LWP 5519)] [New Thread -1235686480 (LWP 5518)] [New Thread -1226237008 (LWP 3783)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7914201 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 63299
Thread 1 (Thread -1223317280 (LWP 3769))
------- Bug moved to this database by unknown@gnome.bugs 2005-10-01 13:07 UTC -------
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Seems to be a GTK issue, Ubuntu http://bugzilla.ubuntu.com/show_bug.cgi?id=21509 has the same backtrace happening with the background capplet
Somewhat the comment didn't get commited yesterday: Program received signal SIGSEGV, Segmentation fault.
+ Trace 64823
Thread 16384 (LWP 8581)
Indeed, in gtk_file_filter_filter(), there's no check for filter_info->mime_type being non-NULL in the case for FILTER_RULE_PIXBUF_FORMATS. I'll put in a fix shortly.
Created attachment 56444 [details] [review] Patch for this bug I've committed this to HEAD and gtk-2-8: 2005-12-27 Federico Mena Quintero <federico@ximian.com> * gtk/gtkfilefilter.c (gtk_file_filter_filter): In the case for FILTER_RULE_PIXBUF_FORMATS, check that filter_info->mime_type is not NULL. Fixes bug #317687.
*** Bug 325099 has been marked as a duplicate of this bug. ***
*** Bug 325435 has been marked as a duplicate of this bug. ***
*** Bug 330900 has been marked as a duplicate of this bug. ***