GNOME Bugzilla – Bug 513427
crash in Volume Control:
Last modified: 2008-01-31 18:58:50 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Vista-Gray Icon Theme: Vista Memory status: size: 34385920 vsize: 34385920 resident: 12943360 share: 9764864 rss: 12943360 rss_rlim: 4294967295 CPU usage: start_time: 1201780928 rtime: 26 utime: 22 stime: 4 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 0xb6ed06b0 (LWP 2800)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187573
Thread 1 (Thread 0xb6ed06b0 (LWP 2800))
----------- .xsession-errors (8 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/ws001:/tmp/.ICE-unix/2660 Aviso do gerenciador de janelas: Falha ao ler o arquivo de sessão salvo /home/rocha/.metacity/sessions/default0.ms: Failed to open file '/home/rocha/.metacity/sessions/default0.ms': No such file or d Initializing nautilus-open-terminal extension ** (gnome-cups-icon:2757): WARNING **: IPP request failed with status 1280 Initializing nautilus-image-converter extension 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 --------------------------------------------------
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 ***