Bug 575156 – 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 575156 - crash in Volume Control:


Summary:	crash in Volume Control:


Status:	RESOLVED DUPLICATE of bug 574950

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:	2009-03-12 23:51 UTC by Wouter Bolsterlee (uws)
Modified:	2009-03-13 12:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Description Wouter Bolsterlee (uws) 2009-03-12 23:51:40 UTC

What were you doing when the application crashed?



Distribution: Debian squeeze/sid
Gnome Release: 2.24.2 2009-01-04 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.28-1-686 #1 SMP Mon Feb 23 03:13:24 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Shiki-Brave
Icon Theme: Tango

Memory status: size: 58806272 vsize: 58806272 resident: 20992000 share: 14221312 rss: 20992000 rss_rlim: 18446744073709551615
CPU usage: start_time: 1236893622 rtime: 223 utime: 184 stime: 39 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6d2e970 (LWP 4525)]
0xb80c9424 in __kernel_vsyscall ()

+ Trace 213439

Thread 1 (Thread 0xb6d2e970 (LWP 4525))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /build/buildd/glib2.0-2.19.10/glib/gspawn.c line 382
#3 IA__g_spawn_command_line_sync
at /build/buildd/glib2.0-2.19.10/glib/gspawn.c line 694
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 IA__g_datalist_id_set_data_full
at /build/buildd/glib2.0-2.19.10/glib/gdataset.c line 216
#8 g_object_real_dispose
at /build/buildd/glib2.0-2.19.10/gobject/gobject.c line 740
#9 gtk_object_dispose
at /tmp/buildd/gtk+2.0-2.15.5/gtk/gtkobject.c line 426
#10 gtk_widget_dispose
at /tmp/buildd/gtk+2.0-2.15.5/gtk/gtkwidget.c line 7906
#11 gtk_window_dispose
at /tmp/buildd/gtk+2.0-2.15.5/gtk/gtkwindow.c line 2147
#12 IA__g_object_unref
at /build/buildd/glib2.0-2.19.10/gobject/gobject.c line 2393
#13 gnome_volume_applet_dispose
at applet.c line 507
#14 IA__g_object_run_dispose
at /build/buildd/glib2.0-2.19.10/gobject/gobject.c line 789
#15 IA__gtk_object_destroy
at /tmp/buildd/gtk+2.0-2.15.5/gtk/gtkobject.c line 406
#16 ??
from /usr/lib/libbonoboui-2.so.0
#17 ??
#18 ??
#19 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
Windowmanager waarschuwing:CurrentTime used to choose focus window; focus window may not be correct.
Windowmanager waarschuwing:Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
seahorse nautilus module shutdown
Shutting down nautilus-open-terminal extension
--- Hash table keys for warning below:
--> x-nautilus-desktop:///
--> file:///home/uws
--> file:///home/uws/Incoming/Photos
--> file:///home/uws/Desktop
--> file:///home/uws/Incoming
(nautilus:4469): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 5 elements at quit time (keys above)
(nautilus:4469): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 5 elements at quit time
--------------------------------------------------

Comment 1 Fabio Durán Verdugo 2009-03-13 12:21:23 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 574950 ***