GNOME Bugzilla – Bug 383959
crash in Theme: I had made a duplicate o...
Last modified: 2006-12-14 07:57:04 UTC
Version: 2.16.2 What were you doing when the application crashed? I had made a duplicate of an icon theme I was working on, done some work on it and opened the theme manager to test it. I had forgotten to change the name of the theme in the index.theme file, so I opened that file, edited it and saved it. The theme manager was running while I did this, and it subsequently crashed. Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.16.2 2006-11-22 (Dropline GNOME) BugBuddy Version: 2.16.0 Memory status: size: 29155328 vsize: 0 resident: 29155328 share: 0 rss: 12816384 rss_rlim: 0 CPU usage: start_time: 1165642995 rtime: 0 utime: 98 stime: 0 cutime:88 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-theme-manager' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225681216 (LWP 6465)] 0xb79c004e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 92727
Thread 1 (Thread -1225681216 (LWP 6465))
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!
From the description, this sounds like a duplicate of bug 349471. *** This bug has been marked as a duplicate of 349471 ***