GNOME Bugzilla – Bug 573966
crash in Deskbar: fechei a aplicação
Last modified: 2009-03-10 14:08:32 UTC
What were you doing when the application crashed? fechei a aplicação Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.1 2008-04-15 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 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 (376 sec old) --------------------- WARNING: modinfo for module nvidia failed: modinfo: could not find module nvidia WARNING: modinfo for module nvidia_legacy failed: modinfo: could not find module nvidia_legacy WARNING: modinfo for module fglrx failed: modinfo: could not find module fglrx (gnome-panel:5626): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 (gnome-panel:5626): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/eth1' ** Message: <info> Forcing device '/org/freedesktop/NetworkManager/Devices/eth1' -------------------------------------------------- Traceback (most recent call last):
+ Trace 213122
self._client.notify_add(self.GCONF_PROXY_PORT_KEY, lambda x, y, z, a: self.emit("proxy-port-changed", z.value.get_string()))
*** Bug 573972 has been marked as a duplicate of this bug. ***
*** Bug 573967 has been marked as a duplicate of this bug. ***
Same traceback and same version of bug 557570 (which is fixed in upstream), may be a duplicate?
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 557570 ***