GNOME Bugzilla – Bug 359182
crash in Theme: This is a followup to bu...
Last modified: 2006-10-03 02:15:30 UTC
Version: 2.16.1 What were you doing when the application crashed? This is a followup to bug 352490. I ran from gnome-terminal as requested: justin@justin01:~$ gnome-theme-manager ** (bug-buddy:12650): WARNING **: Couldn't load icon for Decrypt File ** (bug-buddy:12650): WARNING **: Couldn't load icon for Import Key ** (bug-buddy:12650): WARNING **: Couldn't load icon for Open Folder ** (bug-buddy:12650): WARNING **: Couldn't load icon for Verify Signature That is the only output. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 50724864 vsize: 0 resident: 50724864 share: 0 rss: 15425536 rss_rlim: 0 CPU usage: start_time: 1159840311 rtime: 0 utime: 85 stime: 0 cutime:75 cstime: 0 timeout: 10 it_real_value: 0 frequency: 1 Backtrace was generated from '/usr/bin/gnome-theme-manager' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225140560 (LWP 12199)] [New Thread -1244210272 (LWP 12641)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 74195
Thread 1 (Thread -1225140560 (LWP 12199))
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 352490 ***
Justin: Your responses are less likely to get lost if you just go to the bugzilla website and enter your comments there, rather than filing a new bug every time. I'll add the info this time, but it's likely to be missed next time...
Thanks for providing the requested terminal output, Justin. :) Added a note to bug 352490.
Eliah, *no* additional info is missed, while I am triaging bugs. (If only I would have not been caught by tw mid-air collisions... ;) *** This bug has been marked as a duplicate of 352490 ***
Karsten: True, but assuming *you* will be the one to triage the bug (while not too bad an assumption right now) is not always going to be true. ;)