Bug 494140 – crash in Volume Control: nothing

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 494140 - crash in Volume Control: nothing


Summary:	crash in Volume Control: nothing


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-11-06 13:16 UTC by ak
Modified:	2007-11-18 03:26 UTC

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

Description ak 2007-11-06 13:16:57 UTC

What were you doing when the application crashed?
nothing


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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 41590784 vsize: 41590784 resident: 19300352 share: 16375808 rss: 19300352 rss_rlim: 4294967295
CPU usage: start_time: 1194353120 rtime: 146 utime: 29 stime: 117 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 -1208432304 (LWP 3194)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 175710

Thread 1 (Thread -1208432304 (LWP 3194))

#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 ---------------------
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
Error: Document has not the mandatory ending %EOF
--------------------------------------------------

Comment 1 André Klapper 2007-11-18 03:26:32 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 ***