GNOME Bugzilla – Bug 514990
crash in Volume Control: volvi a instalar gnome p...
Last modified: 2008-02-07 23:41:19 UTC
What were you doing when the application crashed? volvi a instalar gnome pero en la la version mas reciente 2.20.3 Distribution: Debian 4.0 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: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 25554944 vsize: 25554944 resident: 13062144 share: 9764864 rss: 13062144 rss_rlim: 4294967295 CPU usage: start_time: 1202378897 rtime: 15 utime: 14 stime: 1 cutime:17 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 -1226262864 (LWP 4841)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 188420
Thread 1 (Thread -1226262864 (LWP 4841))
----------- .xsession-errors --------------------- /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/debian:/tmp/.ICE-unix/4675 Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/migdalis/.metacity/sessions/default0.ms: Failed to open file '/home/migdalis/.metacity/sessions/defau Initializing gnome-mount extension seahorse nautilus module initialized 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 ***