Bug 513698 – 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 513698 - 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-02-01 14:00 UTC by kilroydacat
Modified:	2008-02-01 18:15 UTC

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

Description kilroydacat 2008-02-01 14:00:09 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.18-4-686 #1 SMP Wed May 9 23:03:12 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: Kreski-Lines

Memory status: size: 30998528 vsize: 30998528 resident: 11984896 share: 8884224 rss: 11984896 rss_rlim: 4294967295
CPU usage: start_time: 1201855672 rtime: 100 utime: 78 stime: 22 cutime:1 cstime: 6 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 0xb6e756b0 (LWP 10487)]
(no debugging symbols found)
0xb77d0321 in waitpid () from /lib/libpthread.so.0

+ Trace 187735

Thread 1 (Thread 0xb6e756b0 (LWP 10487))

#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 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libgthread-2.0.so.0
#11 ??
#12 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#13 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#14 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#15 ??
#16 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#17 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#18 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#19 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#20 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#21 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#22 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#23 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#24 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#25 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#26 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#27 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#28 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#29 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#30 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#31 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#32 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#33 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#34 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#35 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#36 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#37 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#38 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#39 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#40 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#41 gst_structure_set_parent_refcount
from /usr/lib/libgstreamer-0.10.so.0
#42 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#43 ??
#44 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors (116502 sec old) ---------------------
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-26T00:05Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-26T00:29Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T17:40Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:05Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:07Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:08Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:04Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T17:34Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:06Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:06Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:07Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:06Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Location date: 2008-01-28T18:06Z%2C 
08-01-30 18:26:23 (WARNING): cannot parse Alternate-Loca
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Gianluca Borello 2008-02-01 18:15:04 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 ***