Bug 490116 – 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 490116 - 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-25 12:10 UTC by ddamours
Modified:	2007-10-27 18:10 UTC

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

Description ddamours 2007-10-25 12:10:51 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 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 38490112 vsize: 38490112 resident: 17825792 share: 15106048 rss: 17825792 rss_rlim: 4294967295
CPU usage: start_time: 1193314173 rtime: 12 utime: 10 stime: 2 cutime:4 cstime: 1 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 -1208284848 (LWP 3563)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 172749

Thread 1 (Thread -1208284848 (LWP 3563))

#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 (20 sec old) ---------------------
localuser:damoursda being added to access control list
SESSION_MANAGER=local/unix:/tmp/.ICE-unix/3349
(gnome-panel:3466): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x81e4958
(gnome-panel:3466): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x81e4958
seahorse nautilus module initialized
** (nm-applet:3495): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed
** (nm-applet:3495): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed
** (nm-applet:3495): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' failed
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
--------------------------------------------------

Comment 1 Marc-Andre Lureau 2007-10-27 18:10:00 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 ***