GNOME Bugzilla – Bug 409670
crash in Trash: Change Themes
Last modified: 2007-03-31 00:58:08 UTC
What were you doing when the application crashed? Change Themes Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:51:47 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 57507840 vsize: 0 resident: 57507840 share: 0 rss: 9412608 rss_rlim: 0 CPU usage: start_time: 1171904698 rtime: 0 utime: 30 stime: 0 cutime:27 cstime: 0 timeout: 3 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/libexec/trashapplet' (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 -1208248624 (LWP 20744)] (no debugging symbols found) 0x00f19402 in __kernel_vsyscall ()
+ Trace 112032
Thread 1 (Thread -1208248624 (LWP 20744))
----------- .xsession-errors --------------------- Failed to initialize Panel Agent! Failed to initialize Panel Agent! (pam-panel-icon:20951): Gtk-WARNING **: module_path にはテーマ・エンジンがありません: "rezlooks", /home/sato/.themes/Rezlooks-Royale/gtk-2.0/gtkrc:186: error: invalid string constant "panel", expected valid string constant ** (bug-buddy:20957): WARNING **: フォルダを開く のアイコンを読み込めませんでした (bug-buddy:20953): Gtk-WARNING **: module_path にはテーマ・エンジンがありません: "rezlooks", /home/sato/.themes/Rezlooks-Royale/gtk-2.0/gtkrc:186: error: invalid string constant "panel", expected valid string constant ** (bug-buddy:20964): WARNING **: フォルダを開く のアイコンを読み込めませんでした (gnome-theme-manager:20812): Gtk-WARNING **: module_path にはテーマ・エンジンがありません: "rezlooks", /home/sato/.themes/Rezlooks-Royale/gtk-2.0/gtkrc:186: error: invalid string constant "panel", expected valid string constant --------------------------------------------------
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 410124 has been marked as a duplicate of this bug. ***
*** Bug 411494 has been marked as a duplicate of this bug. ***
*** Bug 418432 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 356181 ***