Bug 471057 – crash in Volume Control: clicking the upper rhs i...

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 471057 - crash in Volume Control: clicking the upper rhs i...


Summary:	crash in Volume Control: clicking the upper rhs i...


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-08-28 10:03 UTC by kesltock
Modified:	2007-08-28 19:08 UTC

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

Description kesltock 2007-08-28 10:03:03 UTC

What were you doing when the application crashed?
clicking the upper rhs icon


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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Clearlooks

Memory status: size: 49893376 vsize: 49893376 resident: 24903680 share: 21999616 rss: 24903680 rss_rlim: 4294967295
CPU usage: start_time: 1188379464 rtime: 212 utime: 165 stime: 47 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208633008 (LWP 2867)]
(no debugging symbols found)
0x0012d402 in __kernel_vsyscall ()

+ Trace 158463

Thread 1 (Thread -1208633008 (LWP 2867))

#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 (26 sec old) ---------------------
(nautilus:2797): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:2797): libgnomevfs-WARNING **: Failed to create service browser: Bad state
(nautilus:2797): gnome-vfs-modules-WARNING **: Failed to create client: Daemon not running
** Message: Hit unexpected error "Operation not permitted" while doing a file operation.
** Message: Hit unexpected error "Operation not permitted" while doing a file operation.
warning: rpmts_HdrFromFdno: Header V3 DSA signature: NOKEY, key ID d66b746e
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
--------------------------------------------------

Comment 1 Susana 2007-08-28 19:08: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 ***