GNOME Bugzilla – Bug 513129
crash in Volume Control: starting the system and ...
Last modified: 2008-01-30 18:16:37 UTC
What were you doing when the application crashed? starting the system and entering the password for the gnome keyring manager 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: Gilouche-suse-mint Icon Theme: Mist Memory status: size: 35016704 vsize: 35016704 resident: 13914112 share: 9760768 rss: 13914112 rss_rlim: 4294967295 CPU usage: start_time: 1201705425 rtime: 20 utime: 16 stime: 4 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6eaf6b0 (LWP 3718)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187390
Thread 1 (Thread 0xb6eaf6b0 (LWP 3718))
----------- .xsession-errors (11 sec old) --------------------- (gnome-settings-daemon:3563): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 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 ** (x-session-manager:3501): WARNING **: Failed to start sound. Avviso del window manager: Lettura del file della sessione /home/federico/.metacity/sessions/default0.ms fallita: Failed to open file '/home/federico/.metacity/sessions/default0.ms': No such file or d Connection failure: Connection refused Initializing gnome-mount extension seahorse nautilus module initialized (gnome-panel:3588): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 24 --------------------------------------------------
Where I was asked to reload it I answered yes and it crashes again. Here is the trace (I don't know if it's the same of the previous): 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: Gilouche-suse-mint Icon Theme: Mist Memory status: size: 35016704 vsize: 35016704 resident: 13914112 share: 9760768 rss: 13914112 rss_rlim: 4294967295 CPU usage: start_time: 1201705579 rtime: 22 utime: 18 stime: 4 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6ebf6b0 (LWP 3955)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187391
Thread 1 (Thread 0xb6ebf6b0 (LWP 3955))
----------- .xsession-errors (140 sec old) --------------------- 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 ** (x-session-manager:3501): WARNING **: Failed to start sound. Avviso del window manager: Lettura del file della sessione /home/federico/.metacity/sessions/default0.ms fallita: Failed to open file '/home/federico/.metacity/sessions/default0.ms': No such file or d Connection failure: Connection refused Initializing gnome-mount extension seahorse nautilus module initialized (gnome-panel:3588): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 24 ** Message: <info> Si è ora connessi alla rete wireless “ZyXEL_nostro”. -------------------------------------------------- I am using Debian GNU/Linux unstable (sid), Kernel 2.6.22-3-686, GNOME 2.20.3
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 ***