GNOME Bugzilla – Bug 523970
crash in Deskbar: Actualizando El sistema ...
Last modified: 2008-03-24 10:58:10 UTC
What were you doing when the application crashed? Actualizando El sistema Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.0 2008-03-17 (Ubuntu) BugBuddy Version: 2.21.90 System: Linux 2.6.24-11-generic #1 SMP Fri Feb 29 22:08:31 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human-Murrine Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (10 sec old) --------------------- Checking for Xgl: not present. No whitelisted driver found aborting and using fallback: /usr/bin/metacity Advertencia del gestor de ventanas: 0 almacenado en la clave GConf /desktop/gnome/peripherals/mouse/cursor_size no es un tamaño razonable para «cursor_size»; debe estar entre 1..128 Advertencia del gestor de ventanas: Ocurrió un error al leer el archivo de sesión guardado /home/montero61/.metacity/sessions/default0.ms: Ha ocurrido un error al abrir el archivo «/home/montero61/ No se ha asignado valor a «/desktop/gnome/applications/at/visual/exec» ERROR: trackerd already running on your session dbus - exiting... seahorse nautilus module initialized evolution-alarm-notify-Message: Setting timeout for 41561 1206316800 1206275239 evolution-alarm-notify-Message: Sun Mar 23 21:00:00 2008 evolution-alarm-notify-Message: Sun Mar 23 09:27:19 2008 ** (nautilus:5691): WARNING **: Unable to add monitor: No soportado -------------------------------------------------- Traceback (most recent call last):
+ Trace 193129
self.load (f)
modules = self.import_module (filename)
if not getattr(module, "has_requirements" )():
if is_preferred_browser("epiphany"):
if http_handler.find(test) != -1:
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 518941 ***