GNOME Bugzilla – Bug 478582
crash in Evolution: changing gnome theme
Last modified: 2007-10-03 00:35:55 UTC
What were you doing when the application crashed? changing gnome theme Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22.1 #2 SMP Thu Aug 16 10:02:38 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 558534656 vsize: 558534656 resident: 51822592 share: 22278144 rss: 51822592 rss_rlim: 18446744073709551615 CPU usage: start_time: 1190201151 rtime: 1020 utime: 926 stime: 94 cutime:2 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' (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 47771619051600 (LWP 1811)] [New Thread 1157933392 (LWP 1890)] [New Thread 1157667152 (LWP 1888)] [New Thread 1149274448 (LWP 1855)] [New Thread 1140881744 (LWP 1854)] [New Thread 1132489040 (LWP 1852)] [New Thread 1124096336 (LWP 1851)] [New Thread 1115703632 (LWP 1833)] [New Thread 1107310928 (LWP 1832)] [New Thread 1098918224 (LWP 1831)] [New Thread 1090525520 (LWP 1830)] [New Thread 1082132816 (LWP 1828)] (no debugging symbols found) 0x00002b72aac1fc7f in waitpid () from /lib/libpthread.so.0
+ Trace 164124
Thread 1 (Thread 47771619051600 (LWP 1811))
----------- .xsession-errors (447 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 --------------------------------------------------
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 426496 ***