Bug 499992 – crash in Volume Control: je testais mon microphon...

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 499992 - crash in Volume Control: je testais mon microphon...


Summary:	crash in Volume Control: je testais mon microphon...


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:	2007-11-27 15:19 UTC by ericlinux77
Modified:	2007-12-19 14:04 UTC

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

Description ericlinux77 2007-11-27 15:19:35 UTC

Version: 2.18.0

What were you doing when the application crashed?
je testais mon microphone 


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:18:33 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 273113088 vsize: 273113088 resident: 16044032 share: 11227136 rss: 16044032 rss_rlim: 18446744073709551615
CPU usage: start_time: 1196176547 rtime: 134 utime: 95 stime: 39 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912677490224 (LWP 3067)]
(no debugging symbols found)
0x00002aaaafd0e865 in waitpid () from /lib64/libpthread.so.0

+ Trace 179834

Thread 1 (Thread 46912677490224 (LWP 3067))

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



----------- .xsession-errors (60 sec old) ---------------------
localuser:linux being added to access control list
SESSION_MANAGER=local/bureau:/tmp/.ICE-unix/2867
--------------------------------------------------

Comment 1 Marc-Andre Lureau 2007-12-19 14:04:45 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 ***