GNOME Bugzilla – Bug 524076
crash in Deskbar: automatic installing wit...
Last modified: 2008-03-24 10:59:19 UTC
What were you doing when the application crashed? automatic installing with synaptic Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.0 2008-03-17 (Ubuntu) BugBuddy Version: 2.21.90 System: Linux 2.6.24-10-generic #1 SMP Fri Feb 22 19:08:18 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 --------------------- /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'scaleaddon' /usr/bin/compiz.real (core) - Error: no 'core' plugin with ABI version '20071103' loaded /usr/bin/compiz.real (scalefilter) - Error: InitObject failed /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'scalefilter' /usr/bin/compiz.real (core) - Error: no 'core' plugin with ABI version '20071103' loaded /usr/bin/compiz.real (shift) - Error: InitObject failed /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'shift' ** (nm-applet:5450): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ ** (nm-applet:5450): WARNING **: <WARN> nma_dbus_init(): could not acquire its service. dbus_bus_acquire_service() says: 'Connection ":1.29" is not allowed to own the service "org.freedesktop.Networ -------------------------------------------------- Traceback (most recent call last):
+ Trace 193184
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 ***