GNOME Bugzilla – Bug 513127
crash in Volume Control: I've just turn on the pc
Last modified: 2008-01-30 18:06:37 UTC
What were you doing when the application crashed? I've just turn on the pc Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: SphereCrystal Memory status: size: 34816000 vsize: 34816000 resident: 13959168 share: 9814016 rss: 13959168 rss_rlim: 4294967295 CPU usage: start_time: 1201701495 rtime: 20 utime: 14 stime: 6 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e6d6b0 (LWP 3617)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187389
Thread 1 (Thread 0xb6e6d6b0 (LWP 3617))
----------- .xsession-errors (9 sec old) --------------------- Checking for nVidia: not present. Checking for FBConfig: present. Checking for Xgl: not present. Starting gtk-window-decorator ** (gnome-cups-icon:3518): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:3518): WARNING **: IPP request failed with status 1280 Initializing gnome-mount 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 seahorse nautilus module initialized /usr/bin/compiz.real (snow) - Info: Loaded Texture snowflake.png --------------------------------------------------
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 ***