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


Summary:	crash in Volume Control:


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-28 07:41 UTC by renato.tonielli
Modified:	2007-10-28 12:39 UTC

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

Description renato.tonielli 2007-10-28 07:41:48 UTC

What were you doing when the application crashed?



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: Crux
Icon Theme: Crux

Memory status: size: 279744512 vsize: 279744512 resident: 18857984 share: 14893056 rss: 18857984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193559399 rtime: 60 utime: 16 stime: 44 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496365232 (LWP 3293)]
(no debugging symbols found)
0x0000003a2380d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 173374

Thread 1 (Thread 46912496365232 (LWP 3293))

#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 (21 sec old) ---------------------
09:40:10 : Package Queue:
09:40:10 :  Packages to install
09:40:10 :  ---> amsn - 0.96-7.fc7.x86_64 
09:40:10 :  ---> amsn-debuginfo - 0.96-1.fc7.rf.x86_64 
09:40:10 :  ---> amsn-plugins - 0.96-7.fc7.x86_64 
09:40:10 :  ---> amsn-skins - 0.91-1.2.fc7.rf.noarch 
09:40:10 : Preparazione all'installazione/rimozione/aggiornamento
09:40:10 : -> Preparazione all'installazione
09:40:11 : --> Avvio controllo transazione
09:40:11 : ---> Pacchetto amsn-skins.noarch 0:0.91-1.2.fc7.rf impostato per essere updated
09:40:11 : ---> Pacchetto amsn-plugins.x86_64 0:0.96-7.fc7 impostato per essere updated
09:40:11 : ---> Pacchetto amsn-debuginfo.x86_64 0:0.96-1.fc7.rf impostato per essere updated
09:40:11 : ---> Pacchetto amsn.x86_64 0:0.96-7.fc7 impostato per essere updated
09:40:11 : --> Risoluzione della dipendenza terminata
09:40:20 : Scaricamento pacchetti:
--------------------------------------------------

Comment 1 Christoph Wolk 2007-10-28 12:39:37 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 ***