GNOME Bugzilla – Bug 513153
crash in Volume Control:
Last modified: 2008-01-30 18:08:10 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-486 #1 Mon Nov 12 07:53:08 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: 33034240 vsize: 33034240 resident: 13365248 share: 9424896 rss: 13365248 rss_rlim: 4294967295 CPU usage: start_time: 1201655386 rtime: 24 utime: 18 stime: 6 cutime:0 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 0xb6e246b0 (LWP 4866)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187398
Thread 1 (Thread 0xb6e246b0 (LWP 4866))
----------- .xsession-errors --------------------- This is normally a bug in some application using the D-Bus library. process 4833: arguments to dbus_connection_send() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3050. This is normally a bug in some application using the D-Bus library. 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 ** (nm-applet:4764): WARNING **: <WARN> nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory ** (gnome-panel:4732): WARNING **: Failed to establish a connection with GDM: No such file or directory --------------------------------------------------
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 ***