GNOME Bugzilla – Bug 513503
crash in Volume Control: I've only start the sist...
Last modified: 2008-01-31 18:57:50 UTC
What were you doing when the application crashed? I've only start the sistem. 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: Clearlooks Icon Theme: gnome Memory status: size: 34902016 vsize: 34902016 resident: 13901824 share: 9838592 rss: 13901824 rss_rlim: 4294967295 CPU usage: start_time: 1201806746 rtime: 15 utime: 11 stime: 4 cutime:1 cstime: 0 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 0xb6e8d6b0 (LWP 3510)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187629
Thread 1 (Thread 0xb6e8d6b0 (LWP 3510))
----------- .xsession-errors (12 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=it_IT. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/debian:/tmp/.ICE-unix/3352 Avviso del window manager: Lettura del file della sessione /home/questor/.metacity/sessions/default0.ms fallita: Failed to open file '/home/questor/.metacity/sessions/default0.ms': No such file or dir 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 seahorse nautilus module initialized Initializing gnome-mount extension --------------------------------------------------
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 ***