GNOME Bugzilla – Bug 524026
crash in Deskbar: Was updating with update...
Last modified: 2008-03-24 10:58:21 UTC
What were you doing when the application crashed? Was updating with update / package manager. Also just activated the full visual effects and it downloaded some updates for that. 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 (209 sec old) --------------------- evolution-alarm-notify-Message: Mon Mar 24 07:31:03 2008 ** (nautilus:6066): WARNING **: Unable to add monitor: Not supported Starting gtk-window-decorator /usr/bin/compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format /usr/bin/compiz.real (core) - Error: no 'scale' plugin with ABI version '20080222' loaded /usr/bin/compiz.real (scaleaddon) - Error: InitObject failed /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'scaleaddon' /usr/bin/compiz.real (core) - Error: no 'scale' plugin with ABI version '20080222' loaded /usr/bin/compiz.real (scalefilter) - Error: InitObject failed /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'scalefilter' I/O warning : failed to load external entity "/home/reterg/.compiz/session/default0" -------------------------------------------------- Traceback (most recent call last):
+ Trace 193159
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 ***