Bug 486866 – crash in Volume Control: starting skype

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 486866 - crash in Volume Control: starting skype


Summary:	crash in Volume Control: starting skype


Status:	RESOLVED DUPLICATE of bug 463147

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:	2007-10-15 16:10 UTC by ken.lee
Modified:	2007-10-19 17:45 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description ken.lee 2007-10-15 16:10:55 UTC

What were you doing when the application crashed?
starting skype


Distribution: Red Hat Enterprise Linux AS release 3 (Taroon)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 34041856 vsize: 34041856 resident: 16007168 share: 13213696 rss: 16007168 rss_rlim: 4294967295
CPU usage: start_time: 1192463127 rtime: 20 utime: 15 stime: 5 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/mixer_applet2'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208440496 (LWP 4014)]
0x00df5402 in __kernel_vsyscall ()

+ Trace 170361

Thread 1 (Thread -1208440496 (LWP 4014))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/libc.so.6
#6 abort
from /lib/libc.so.6
#7 __assert_fail
from /lib/libc.so.6
#8 snd_hctl_handle_events
from /lib/libasound.so.2
#9 snd_mixer_handle_events
from /lib/libasound.so.2
#10 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#11 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#12 ??
from /usr/lib/gstreamer-0.10/libgstalsa.so
#13 gst_mixer_get_volume
from /usr/lib/libgstinterfaces-0.10.so.0
#14 ??
#15 ??
#16 ??
#17 ??
from /lib/libglib-2.0.so.0
#18 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#19 ??
from /lib/libglib-2.0.so.0
#20 g_main_loop_run
from /lib/libglib-2.0.so.0
#21 bonobo_main
from /usr/lib/libbonobo-2.so.0
#22 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#23 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#24 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#25 panel_applet_factory_main
from /usr/lib/libpanel-applet-2.so.0
#26 main
#0 __kernel_vsyscall



----------- .xsession-errors (470 sec old) ---------------------
--- Hash table keys for warning below:
--> file:///home/klee
(nautilus:6322): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
SARegisterProtocolApp(nntp,/usr/bin/konqueror)
SARegisterProtocolApp(http,/usr/bin/konqueror)
SARegisterProtocolApp(https,/usr/bin/konqueror)
SARegisterProtocolApp(ftp,/usr/bin/konqueror)
SARegisterProtocolApp(mailto,fcc)
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x80 specified for 0x4000008 (fcc).
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x80 specified for 0x400001a (fcc).
(gnome-terminal:4025): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x80 specified for 0x1202ac9 ().
--------------------------------------------------

Comment 1 Christian Kirbach 2007-10-19 17:45:36 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 463147 ***