Bug 510601 – crash in Volume Control: Turn Volume Down

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 510601 - crash in Volume Control: Turn Volume Down


Summary:	crash in Volume Control: Turn Volume Down


Status:	RESOLVED DUPLICATE of bug 471133

Product:	gnome-media
Classification:	Deprecated
Component:	gnome-volume-control
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome media maintainers
QA Contact:	gnome media maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-01-19 13:49 UTC by richard
Modified:	2008-01-19 14:03 UTC

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

Description richard 2008-01-19 13:49:56 UTC

Version: 2.18.0

What were you doing when the application crashed?
Turn Volume Down


Distribution: Gentoo Base System release 1.12.10
Gnome Release: 2.18.1 2007-05-04 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-sabayon #1 SMP Mon Sep 3 00:33:06 UTC 2007 x86_64
X Vendor: The X.Org Group
X Vendor Release: 6600
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Human-Graphite
Icon Theme: Tango

Memory status: size: 110436352 vsize: 110436352 resident: 20226048 share: 12398592 rss: 20226048 rss_rlim: 18446744073709551615
CPU usage: start_time: 1200786524 rtime: 43 utime: 33 stime: 10 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-volume-control'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00002ae7b755dad5 in waitpid () from /lib/libpthread.so.0

+ Trace 185952

#0 waitpid
from /lib/libpthread.so.0
#1 ??
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 ??
from /usr/lib/libgobject-2.0.so.0
#4 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#5 ??
from /usr/lib/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#7 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#8 gtk_widget_unparent
from /usr/lib/libgtk-x11-2.0.so.0
#9 ??
from /usr/lib/libgtk-x11-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgobject-2.0.so.0
#16 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#17 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#22 ??
from /usr/lib/libgobject-2.0.so.0
#23 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#24 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#25 ??
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#27 ??
from /usr/lib/libgtk-x11-2.0.so.0
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 ??
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#32 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#33 ??
from /usr/lib/libgtk-x11-2.0.so.0
#34 g_object_unref
from /usr/lib/libgobject-2.0.so.0
#35 g_value_unset
from /usr/lib/libgobject-2.0.so.0
#36 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#37 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#38 gnome_volume_control_element_change
#39 ??
#40 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#41 ??
from /usr/lib/libgtk-x11-2.0.so.0
#42 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#43 ??
from /usr/lib/libgobject-2.0.so.0
#44 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#45 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#46 ??
from /usr/lib/libgtk-x11-2.0.so.0
#47 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#48 ??
from /usr/lib/libgtk-x11-2.0.so.0
#49 ??
from /usr/lib/libgtk-x11-2.0.so.0
#50 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#51 ??
from /usr/lib/libgobject-2.0.so.0
#52 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#53 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#54 ??
from /usr/lib/libgtk-x11-2.0.so.0
#55 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#56 ??
from /usr/lib/libgtk-x11-2.0.so.0
#57 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#58 ??
from /usr/lib/libgobject-2.0.so.0
#59 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#60 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#61 ??
from /usr/lib/libgtk-x11-2.0.so.0
#62 g_object_run_dispose
from /usr/lib/libgobject-2.0.so.0
#63 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#64 ??
from /usr/lib/libgdk-x11-2.0.so.0
#65 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#66 ??
from /usr/lib/libglib-2.0.so.0
#67 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#68 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#69 main



----------- .xsession-errors ---------------------
restacking: Warnning unknown next window
restacking: Warnning unknown next window
restacking: Warnning unknown next window
restacking: Warnning unknown next window
restacking: Warnning unknown next window
restacking: Warnning unknown next window
restacking: Warnning unknown next window
restacking: Warnning unknown next window
(gnome-volume-control:14531): GLib-GObject-CRITICAL **: g_object_ref: assertion `object->ref_count > 0' failed
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x1600003
restacking: Warnning unknown next window
--------------------------------------------------

Comment 1 Marc-Andre Lureau 2008-01-19 14:03:16 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 471133 ***