Bug 513242 – crash in Volume Control: Logging into Gnome

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 513242 - crash in Volume Control: Logging into Gnome


Summary:	crash in Volume Control: Logging into Gnome


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 19:53 UTC by stig.doermaenen
Modified:	2008-01-30 22:06 UTC

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

Description stig.doermaenen 2008-01-30 19:53:19 UTC

What were you doing when the application crashed?
Logging into Gnome


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

System: Linux 2.6.24 #1 SMP Wed Jan 30 20:29:43 CET 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 36491264 vsize: 36491264 resident: 13410304 share: 9482240 rss: 13410304 rss_rlim: 4294967295
CPU usage: start_time: 1201722758 rtime: 50 utime: 40 stime: 10 cutime:2 cstime: 5 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6df06b0 (LWP 4531)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 187456

Thread 1 (Thread 0xb6df06b0 (LWP 4531))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#7 ??
#8 ??
#9 ??
#10 ??
#11 ??
from /usr/lib/libgthread-2.0.so.0
#12 ??
#13 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#14 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#15 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#16 ??
#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 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#42 gst_structure_set_parent_refcount
from /usr/lib/libgstreamer-0.10.so.0
#43 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#44 ??
#45 ??
#46 ??
#47 ??
#48 ??
#49 ??
#50 ??
#51 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#52 ??
#53 ??
from /usr/lib/libgstaudio-0.10.so.0
#54 ??
#55 ??
from /usr/lib/gstreamer-0.10/libgstossaudio.so
#56 ??
#57 ??
from /usr/lib/libgobject-2.0.so.0
#58 ??
#59 ??
from /usr/lib/libgstinterfaces-0.10.so.0
#60 ??
#61 ??
from /usr/lib/libgstinterfaces-0.10.so.0
#62 ??
#63 gst_mixer_list_tracks
from /usr/lib/libgstinterfaces-0.10.so.0
#0 __kernel_vsyscall



----------- .xsession-errors (9 sec old) ---------------------
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
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
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: Invalid symbolic color 'tooltip_bg_color'
/usr/share/themes/Clearlooks/gtk-2.0/gtkrc:170: error: invalid identifier `tooltip_bg_color', expected valid identifier
** Message: <info>  You are now connected to the wireless network 'DI-634M'.
--------------------------------------------------

Comment 1 Gianluca Borello 2008-01-30 22:06:34 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 ***