Bug 503826 – crash in Volume Control: trying to start it

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 503826 - crash in Volume Control: trying to start it


Summary:	crash in Volume Control: trying to start it


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-12-16 09:55 UTC by jerry.carter
Modified:	2007-12-16 18:01 UTC

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

Description jerry.carter 2007-12-16 09:55:51 UTC

What were you doing when the application crashed?
trying to start it		


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 278413312 vsize: 278413312 resident: 17936384 share: 14143488 rss: 17936384 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196666159 rtime: 30124 utime: 3659 stime: 26465 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 46912496311984 (LWP 2954)]
(no debugging symbols found)
0x0000003cbec0d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 182002

Thread 1 (Thread 46912496311984 (LWP 2954))

#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 (1127349 sec old) ---------------------
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
Max failures exceeded, exiting now
--------------------------------------------------

Comment 1 Susana 2007-12-16 18:01:31 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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