GNOME Bugzilla – Bug 522683
crash in Deskbar: rechner schaltete sich s...
Last modified: 2008-03-16 09:33:51 UTC
What were you doing when the application crashed? rechner schaltete sich selbs aus 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 (28 sec old) --------------------- ** (gnome-settings-daemon:6013): WARNING **: Fehler beim Öffnen des Verzeichnisses »/etc/gnome/config«: No such file or directory Checking for Xgl: not present. Found laptop using ati driver. aborting and using fallback: /usr/bin/metacity Fenstermanager-Warnung: Gespeicherte Sitzungsdatei /home/ilo/.metacity/sessions/default0.ms konnte nicht gelesen werden: Datei »/home/ilo/.metacity/sessions/default0.ms« konnte nicht geöffnet werde »/desktop/gnome/applications/at/visual/exec« wurde kein Wert zugewiesen ERROR: trackerd already running on your session dbus - exiting... seahorse nautilus module initialized evolution-alarm-notify-Message: Setting timeout for 7223 1205625600 1205618377 evolution-alarm-notify-Message: Sun Mar 16 01:00:00 2008 evolution-alarm-notify-Message: Sat Mar 15 22:59:37 2008 ** (nautilus:6058): WARNING **: Unable to add monitor: Nicht unterstützt -------------------------------------------------- Traceback (most recent call last):
+ Trace 192538
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 ***