GNOME Bugzilla – Bug 513233
crash in Volume Control: I logged in, then it alr...
Last modified: 2008-01-30 22:06:27 UTC
What were you doing when the application crashed? I logged in, then it already crashed. Happened after today's libgstreamer updates.... Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 35176448 vsize: 35176448 resident: 11931648 share: 8912896 rss: 11931648 rss_rlim: 4294967295 CPU usage: start_time: 1201720920 rtime: 15 utime: 12 stime: 3 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6e396b0 (LWP 9391)] 0xb7794321 in waitpid () from /lib/libpthread.so.0
+ Trace 187450
Thread 1 (Thread 0xb6e396b0 (LWP 9391))
----------- .xsession-errors --------------------- 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 ** (gsynaptics-init:9349): WARNING **: Using synclient ** (nautilus:9317): WARNING **: Can not get _NET_WORKAREA ** (nautilus:9317): WARNING **: Can not determine workarea, guessing at layout Connection failure: Connection refused system-config-printer-applet: failed to start NewPrinterNotification service (gnome-panel:9312): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 Unknown parameter CoastingSpeedThreshold --------------------------------------------------
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 ***