GNOME Bugzilla – Bug 404001
crash in Theme: Installed one of the the...
Last modified: 2007-02-03 19:21:55 UTC
Version: 2.16.0 What were you doing when the application crashed? Installed one of the themes - by doing an install theme. (Icons is what I was installing) - UnofficialTango I guess. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:32:37 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors (6517 sec old) --------------------- Lost connection to Evolution Exchange backend process (evolution:5201): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:5201): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:5201): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process (evolution:5201): evolution-mail-WARNING **: Error occurred while existing dialogue active: Lost connection to Evolution Exchange backend process ...Too much output, ignoring rest... -------------------------------------------------- Memory status: size: 259362816 vsize: 0 resident: 259362816 share: 0 rss: 20434944 rss_rlim: 0 CPU usage: start_time: 1170524327 rtime: 0 utime: 1151 stime: 0 cutime:1014 cstime: 0 timeout: 137 it_real_value: 0 frequency: 673 Backtrace was generated from '/usr/bin/gnome-theme-manager' (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 -1208863024 (LWP 9779)] [New Thread -1470604400 (LWP 10231)] (no debugging symbols found) 0x0091b402 in __kernel_vsyscall ()
+ Trace 107707
Thread 1 (Thread -1208863024 (LWP 9779))
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 349471 ***