GNOME Bugzilla – Bug 513077
crash in Volume Control: Nenion. Mi jxus startig...
Last modified: 2008-01-30 18:06:32 UTC
What were you doing when the application crashed? Nenion. Mi jxus startigis la sistemon. 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: Wasp Icon Theme: Wasp Memory status: size: 35336192 vsize: 35336192 resident: 14245888 share: 10022912 rss: 14245888 rss_rlim: 4294967295 CPU usage: start_time: 1201692537 rtime: 25 utime: 20 stime: 5 cutime:0 cstime: 2 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 0xb6ea06b0 (LWP 3049)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187369
Thread 1 (Thread 0xb6ea06b0 (LWP 3049))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/asturlando:/tmp/.ICE-unix/2887 Window manager warning: Failed to read saved session file /home/carleos/.metacity/sessions/default0.ms: Failed to open file '/home/carleos/.metacity/sessions/default0.ms': No such file or directory seahorse nautilus module initialized Initializing gnome-mount extension 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 ***