GNOME Bugzilla – Bug 434074
crash in Panel: changing a background im...
Last modified: 2007-07-03 12:22:42 UTC
Version: 2.18.1 What were you doing when the application crashed? changing a background image Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.1 2007-04-27 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.20-ck1 #4 SMP Sat Apr 28 03:09:26 Local time zone must be set--see zic x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 158744576 vsize: 158744576 resident: 19705856 share: 13869056 rss: 19705856 rss_rlim: 18446744073709551615 CPU usage: start_time: 1177762661 rtime: 136 utime: 125 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-panel' (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 47911741501200 (LWP 6283)] 0x00002b9350a0b502 in waitpid () from /lib/libpthread.so.0
+ Trace 131060
Thread 1 (Thread 47911741501200 (LWP 6283))
----------- .xsession-errors --------------------- ++DOMWINDOW == 3 ++DOMWINDOW == 4 ++WEBSHELL == 3 ++DOMWINDOW == 5 ++DOMWINDOW == 6 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsStringBundle.cpp, line 273 Bonobo-Activation-Message: Reset cache Bonobo-Activation-Message: Reset cache Bonobo-Activation-Message: Reset cache --------------------------------------------------
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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 434126 has been marked as a duplicate of this bug. ***
*** Bug 439760 has been marked as a duplicate of this bug. ***
*** Bug 439761 has been marked as a duplicate of this bug. ***
*** Bug 440655 has been marked as a duplicate of this bug. ***
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. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! (Since bugzilla policy for bad_stacktrace is now to mark as INCOMPLETE. Mass changing all of these. Search for "dieguito-doing-incomplete-spam" to delete all this from your inbox.)
*** Bug 450127 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, 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. *** This bug has been marked as a duplicate of 422966 ***