GNOME Bugzilla – Bug 525111
crash in Deskbar: Installing the updates
Last modified: 2008-03-30 14:30:15 UTC
What were you doing when the application crashed? Installing the updates Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.0 2008-03-28 (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 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 (12 sec old) --------------------- (gnome-panel:24323): GLib-CRITICAL **: g_array_free: assertion `array' failed (gnome-panel:24323): GLib-CRITICAL **: g_array_free: assertion `array' failed (gnome-panel:24323): GLib-CRITICAL **: g_array_free: assertion `array' failed (gnome-panel:24323): GLib-CRITICAL **: g_array_free: assertion `array' failed (gnome-panel:24323): GLib-CRITICAL **: g_array_free: assertion `array' failed WARNING: modinfo for module nvidia_new failed: modinfo: could not open /lib/modules/2.6.24-11-generic/volatile/nvidia_new.ko: No such file or directory WARNING: modinfo for module nvidia failed: modinfo: could not open /lib/modules/2.6.24-11-generic/volatile/nvidia.ko: No such file or directory WARNING: modinfo for module nvidia_legacy failed: modinfo: could not open /lib/modules/2.6.24-11-generic/volatile/nvidia_legacy.ko: No such file or directory -------------------------------------------------- Traceback (most recent call last):
+ Trace 193675
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 ***