Bug 513147 – crash in Volume Control:

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 513147 - crash in Volume Control:


Summary:	crash in Volume Control:


Status:	RESOLVED DUPLICATE of bug 513018

Product:	gnome-applets
Classification:	Other
Component:	mixer
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-applets Maintainers
QA Contact:	gnome-applets Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-30 14:47 UTC by stefano
Modified:	2008-01-30 18:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description stefano 2008-01-30 14:47:16 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-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: Glider
Icon Theme: gnome

Memory status: size: 33378304 vsize: 33378304 resident: 12849152 share: 9715712 rss: 12849152 rss_rlim: 4294967295
CPU usage: start_time: 1201704326 rtime: 24 utime: 20 stime: 4 cutime:1 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 0xb6eb36b0 (LWP 3920)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 187395

Thread 1 (Thread 0xb6eb36b0 (LWP 3920))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
from /usr/lib/libgthread-2.0.so.0
#12 ??
#13 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#14 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#15 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#40 ??
#41 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#42 gst_structure_set_parent_refcount
from /usr/lib/libgstreamer-0.10.so.0
#43 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#44 ??
#45 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(gnome-settings-daemon:3813): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
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:3853): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.22" is not allowed to own the service "org.freedesktop.Networ
/usr/share/themes/Glider/gtk-2.0/gtkrc:107: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Glider/gtk-2.0/gtkrc:107: error: invalid identifier `tooltip_bg_color', expected valid identifier
(update-notifier:3843): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** (nm-applet:3853): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.22" is not allowed to own the service "org.freedesktop.Networ
--------------------------------------------------

Comment 1 Gianluca Borello 2008-01-30 18:07:53 UTC

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 ***