GNOME Bugzilla – Bug 513104
crash in Volume Control: logging in
Last modified: 2008-01-30 18:13:33 UTC
What were you doing when the application crashed? logging in Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-amd64 #1 SMP Fri Dec 21 12:00:17 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 274513920 vsize: 274513920 resident: 15343616 share: 10391552 rss: 15343616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1201695926 rtime: 12 utime: 10 stime: 2 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' (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 0x2ace9fe36b50 (LWP 672)] (no debugging symbols found) 0x00002ace98af534f in waitpid () from /lib/libpthread.so.0
+ Trace 187380
Thread 1 (Thread 0x2ace9fe36b50 (LWP 672))
----------- .xsession-errors --------------------- ** (gnome-settings-daemon:601): WARNING **: The system configuration changed - but we remain silent wswatch: error while loading shared libraries: libwnck-1.so.18: cannot open shared object file: No such file or directory (gnome-panel:609): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x6ba460 (gnome-panel:609): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x6ba460 seahorse nautilus module initialized Initializing gnome-mount extension Initializing nautilus-open-terminal extension xrdb: "*Label.background" on line 220 overrides entry on line 150 xrdb: "*Text.background" on line 226 overrides entry on line 191 xrdb: "*Label.foreground" on line 232 overrides entry on line 151 xrdb: "*Text.foreground" on line 238 overrides entry on line 192 --------------------------------------------------
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 513018 ***