GNOME Bugzilla – Bug 513368
crash in Volume Control: I just started computer
Last modified: 2008-01-31 11:34:57 UTC
What were you doing when the application crashed? I just started computer Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: NoiaWarm Memory status: size: 35340288 vsize: 35340288 resident: 14012416 share: 9617408 rss: 14012416 rss_rlim: 4294967295 CPU usage: start_time: 1201767021 rtime: 29 utime: 23 stime: 6 cutime:1 cstime: 4 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 0xb6e336b0 (LWP 3205)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 187542
Thread 1 (Thread 0xb6e336b0 (LWP 3205))
----------- .xsession-errors (13 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/alef:/tmp/.ICE-unix/3046 Ostrzeżenie menedżera okien: Nie można odczytać zapisanego pliku sesji "/home/debian/pawel/.metacity/sessions/default0.ms": Nie można otworzyć pliku "/home/debian/pawel/.metacity/sessions/defaul 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 Initializing gnome-mount extension seahorse nautilus module initialized --------------------------------------------------
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 ***