GNOME Bugzilla – Bug 522680
crash in Deskbar:
Last modified: 2008-03-16 09:33:38 UTC
What were you doing when the application crashed? Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.0 2008-03-10 (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 (22 sec old) --------------------- Checking for Xgl: not present. No whitelisted driver found aborting and using fallback: /usr/bin/metacity Avertissement du gestionnaire de fenêtres : 0 enregistrée dans la clé GConf /desktop/gnome/peripherals/mouse/cursor_size n'est pas une valeur cursor_size raisonnable; elle doit se trouver dans l'i Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/bidule1/.metacity/sessions/default0.ms a échoué : L'ouverture du fichier « /home/bidule1/.metacity Aucune valeur définie pour « /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 8515 1205625600 1205617085 evolution-alarm-notify-Message: Sun Mar 16 01:00:00 2008 evolution-alarm-notify-Message: Sat Mar 15 22:38:05 2008 ** (nautilus:5645): WARNING **: Unable to add monitor: Non pris en charge -------------------------------------------------- Traceback (most recent call last):
+ Trace 192535
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 ***