GNOME Bugzilla – Bug 554885
crash in Deskbar:
Last modified: 2008-10-05 10:55:23 UTC
What were you doing when the application crashed? Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome 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 --------------------- ** (nautilus:6961): WARNING **: Unable to add monitor: Not supported Could not set idle IO priority...attempting best effort 7 priority starting HAL detection for ac adaptors...found /org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_ADP1 Throttle level is 5 evolution-alarm-notify-Message: Setting timeout for 27306 1223078400 1223051094 evolution-alarm-notify-Message: Sat Oct 4 00:00:00 2008 evolution-alarm-notify-Message: Fri Oct 3 16:24:54 2008 /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format (gnome-panel:6958): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -26 and height 23 I/O warning : failed to load external entity "/home/bwyan/.compiz/session/default0" inotify_add_watch: No such file or directory Starting gtk-window-decorator -------------------------------------------------- Traceback (most recent call last):
+ Trace 207715
tray = DeskbarTray(applet)
self.__setup_mvc()
self.__core.run()
self._setup_keybinder()
self.set_keybinding( self.get_keybinding() )
self._gconf.set_keybinding(binding)
self._client.set_string(self.GCONF_KEYBINDING, binding)
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 486549 ***