GNOME Bugzilla – Bug 513452
crash in Volume Control: reiniciar el sistema
Last modified: 2008-01-31 18:58:22 UTC
What were you doing when the application crashed? reiniciar el sistema Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.18-5-amd64 #1 SMP Sat Dec 22 20:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 210014208 vsize: 210014208 resident: 16203776 share: 11153408 rss: 16203776 rss_rlim: 18446744073709551615 CPU usage: start_time: 1201785794 rtime: 17 utime: 11 stime: 6 cutime:1 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b9befd64180 (LWP 5269)] [New Thread 0x40800950 (LWP 5272)] 0x00002b9be8d0434f in waitpid () from /lib/libpthread.so.0
+ Trace 187592
Thread 1 (Thread 0x2b9befd64180 (LWP 5269))
----------- .xsession-errors (1384 sec old) --------------------- /etc/gdm/Xsession: Beginning session setup... can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords SESSION_MANAGER=local/debian:/tmp/.ICE-unix/4052 Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/jmvazquezes/.metacity/sessions/default0.ms: Falló al abrir el archivo «/home/jmvazquezes/.metacity/ 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 ***