Bug 513040 – 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 513040 - crash in Volume Control:


Summary:	crash in Volume Control:


Status:	RESOLVED DUPLICATE of bug 512924

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 09:26 UTC by komur
Modified:	2008-01-30 10:55 UTC

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

Description komur 2008-01-30 09:26:14 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.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: MurrinaAquaIsh
Icon Theme: Nuvola

Memory status: size: 36872192 vsize: 36872192 resident: 13045760 share: 9895936 rss: 13045760 rss_rlim: 4294967295
CPU usage: start_time: 1201685112 rtime: 18 utime: 14 stime: 4 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 0xb6ef76b0 (LWP 7881)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 187340

Thread 1 (Thread 0xb6ef76b0 (LWP 7881))

#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 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#18 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#19 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#20 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#21 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#22 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#23 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#24 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#25 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#26 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#27 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#28 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#29 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#30 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#31 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#32 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#33 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#34 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#35 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#36 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#37 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#38 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#39 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#40 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#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

Comment 1 Gianluca Borello 2008-01-30 10:55:26 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 512924 ***