GNOME Bugzilla – Bug 513177
crash in Volume Control: Logging into my Gnome se...
Last modified: 2008-01-30 18:08:48 UTC
What were you doing when the application crashed? Logging into my Gnome session 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: Clearlooks Icon Theme: Tango Memory status: size: 43577344 vsize: 43577344 resident: 14548992 share: 9936896 rss: 14548992 rss_rlim: 4294967295 CPU usage: start_time: 1201710523 rtime: 28 utime: 22 stime: 6 cutime:3 cstime: 2 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 0xb6da76b0 (LWP 6136)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187416
Thread 1 (Thread 0xb6da76b0 (LWP 6136))
----------- .xsession-errors (32 sec old) --------------------- Warning: No symbols defined for <I7F> (keycode 255) ** (gnome-session:5930): WARNING **: Failed to start sound. ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 ALSA lib control.c:909:(snd_ctl_open_noupdate) Invalid CTL front:0 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 11 Initializing gnome-mount extension seahorse nautilus module initialized (gnome-panel:6057): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 --------------------------------------------------
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 ***