GNOME Bugzilla – Bug 513331
crash in Volume Control: just started the compute...
Last modified: 2008-01-31 11:31:17 UTC
What were you doing when the application crashed? just started the computer right after safe-upgrade Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Forwardlooks Icon Theme: Neu Memory status: size: 34045952 vsize: 34045952 resident: 13303808 share: 9859072 rss: 13303808 rss_rlim: 4294967295 CPU usage: start_time: 1201747275 rtime: 17 utime: 13 stime: 4 cutime:2 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e5e6b0 (LWP 3497)] [New Thread 0xb6964b90 (LWP 3503)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187514
Thread 1 (Thread 0xb6e5e6b0 (LWP 3497))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/salmonella:/tmp/.ICE-unix/3349 Window manager warning: Failed to read saved session file /home/daniel/.metacity/sessions/default0.ms: Failed to open file '/home/daniel/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension (gnome-panel:3419): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 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 --------------------------------------------------
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 ***