Bug 513006 – crash in Volume Control: At User login,loading De...

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 513006 - crash in Volume Control: At User login,loading De...


Summary:	crash in Volume Control: At User login,loading De...


Status:	RESOLVED DUPLICATE of bug 512924

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 05:42 UTC by akiokada
Modified:	2008-01-30 10:51 UTC

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

Description akiokada 2008-01-30 05:42:55 UTC

What were you doing when the application crashed?
At User login,loading Desktop loading gnome.


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

System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 36745216 vsize: 36745216 resident: 12804096 share: 9883648 rss: 12804096 rss_rlim: 4294967295
CPU usage: start_time: 1201671548 rtime: 77 utime: 67 stime: 10 cutime:48 cstime: 20 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 0xb6ef56b0 (LWP 3064)]
(no debugging symbols found)
0xb7850321 in waitpid () from /lib/libpthread.so.0

+ Trace 187316

Thread 1 (Thread 0xb6ef56b0 (LWP 3064))

#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 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??
#37 ??
#38 ??
#39 ??
#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 (7 sec old) ---------------------
/etc/gdm/Xsession: Beginning session setup...
Setting IM through im-switch for locale=ja_JP.
Start IM through /etc/X11/xinit/xinput.d/ja_JP linked to /etc/X11/xinit/xinput.d/uim-toolbar.
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords
SESSION_MANAGER=local/debian:/tmp/.ICE-unix/2923
ウィンドウ・マネージャの警告: 保存されたセッションファイル /home/aokada/.metacity/sessions/default0.ms の読み込みに失敗しました: ファイル '/home/aokada/.met
Initializing gnome-mount extension
seahorse nautilus module initialized
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
--------------------------------------------------

Comment 1 Gianluca Borello 2008-01-30 10:51:04 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 512924 ***