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


Summary:	crash in Volume Control:


Status:	RESOLVED DUPLICATE of bug 513018

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:	2008-01-30 15:50 UTC by thijsstegeman
Modified:	2008-01-30 18:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description thijsstegeman 2008-01-30 15:50:11 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.23-1-amd64 #1 SMP Fri Dec 21 12:00:17 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: Wasp

Memory status: size: 216768512 vsize: 216768512 resident: 17178624 share: 11046912 rss: 17178624 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201708204 rtime: 16 utime: 12 stime: 4 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/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 0x2afd22b2c1c0 (LWP 4284)]
(no debugging symbols found)
0x00002afd1bacc34f in waitpid () from /lib/libpthread.so.0

+ Trace 187407

Thread 1 (Thread 0x2afd22b2c1c0 (LWP 4284))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#6 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#7 ??
from /usr/lib/libgstaudio-0.10.so.0
#8 gst_audio_default_registry_mixer_filter
from /usr/lib/libgstaudio-0.10.so.0
#9 ??
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgdk-x11-2.0.so.0
#18 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#19 ??
from /usr/lib/libglib-2.0.so.0
#20 g_main_loop_run
from /usr/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 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#24 ??
#25 __libc_start_main
from /lib/libc.so.6
#26 ??
#27 ??
#28 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
/etc/gdm/Xsession: Beginning session setup...
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords
SESSION_MANAGER=local/note-lsn220.few.vu.nl:/tmp/.ICE-unix/4062
xrdb:  "*Label.background" on line 220 overrides entry on line 150
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
seahorse nautilus module initialized
(gnome-panel:4150): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 33
Initializing gnome-mount extension
** Message: failed to load session from /home/lsn220/.nautilus/saved-session-2K1R4T
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2400059 (Buddy List)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------

Comment 1 Gianluca Borello 2008-01-30 18:12:22 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 513018 ***