Bug 488430 – crash in Volume Control: I opened Skype 1.4.0.74.

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 488430 - crash in Volume Control: I opened Skype 1.4.0.74.


Summary:	crash in Volume Control: I opened Skype 1.4.0.74.


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-19 21:18 UTC by Max Kanat-Alexander
Modified:	2007-10-19 22:34 UTC

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

Description Max Kanat-Alexander 2007-10-19 21:18:16 UTC

What were you doing when the application crashed?
I opened Skype 1.4.0.74.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 279363584 vsize: 279363584 resident: 18022400 share: 14368768 rss: 18022400 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192822193 rtime: 206 utime: 117 stime: 89 cutime:1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496381616 (LWP 3181)]
(no debugging symbols found)
0x00000033dc00d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 171541

Thread 1 (Thread 46912496381616 (LWP 3181))

#0 waitpid
from /lib64/libpthread.so.0
#1 gtk_vscale_new
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 __assert_fail
from /lib64/libc.so.6
#6 snd_hctl_handle_events
from /lib64/libasound.so.2
#7 snd_mixer_handle_events
from /lib64/libasound.so.2
#8 gtk_vscale_new
from /usr/lib64/gstreamer-0.10/libgstalsa.so
#9 gtk_vscale_new
from /usr/lib64/gstreamer-0.10/libgstalsa.so
#10 ??
#11 ??
#12 ??
#13 gtk_vscale_new
from /lib64/libglib-2.0.so.0
#14 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#15 gtk_vscale_new
from /lib64/libglib-2.0.so.0
#16 g_main_loop_run
from /lib64/libglib-2.0.so.0
#17 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#18 bonobo_generic_factory_main_timeout
from /usr/lib64/libbonobo-2.so.0
#19 panel_applet_factory_main_closure
from /usr/lib64/libpanel-applet-2.so.0
#20 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (237 sec old) ---------------------
** (claws-mail:3194): WARNING **: [13:53:00] IMAP4 connection to mail.trusthosting.net has been disconnected. Reconnecting...
** (claws-mail:3194): WARNING **: [14:03:04] IMAP4 connection to mail.trusthosting.net has been disconnected. Reconnecting...
** (claws-mail:3194): WARNING **: [14:03:07] IMAP4 connection to mail.trusthosting.net has been disconnected. Reconnecting...
** (claws-mail:3194): WARNING **: [14:03:14] IMAP4 connection to mail.trusthosting.net has been disconnected. Reconnecting...
** (claws-mail:3194): WARNING **: [14:13:25] IMAP4 connection to mail.trusthosting.net has been disconnected. Reconnecting...
--------------------------------------------------

Comment 1 Christoph Wolk 2007-10-19 22:34:12 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 ***