GNOME Bugzilla – Bug 513248
crash in Volume Control: starting a new session o...
Last modified: 2008-01-30 22:06:41 UTC
What were you doing when the application crashed? starting a new session of gnome Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.23-1-686-bigmem #1 SMP Fri Dec 21 14:39:17 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: 32935936 vsize: 32935936 resident: 12435456 share: 9396224 rss: 12435456 rss_rlim: 4294967295 CPU usage: start_time: 1201723635 rtime: 12 utime: 10 stime: 2 cutime:0 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 0xb6ed06b0 (LWP 7604)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187461
Thread 1 (Thread 0xb6ed06b0 (LWP 7604))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/linusque:/tmp/.ICE-unix/7496 Window manager warning: Failed to read saved session file /home/gl/.metacity/sessions/default0.ms: Failed to open file '/home/gl/.metacity/sessions/default0.ms': No such file or directory Initializing gnome-mount extension seahorse nautilus module initialized (gnome-panel:7568): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 25 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 ***