GNOME Bugzilla – Bug 542577
crash in Gimmie: the search tool in the s...
Last modified: 2008-07-13 21:12:11 UTC
What were you doing when the application crashed? the search tool in the settings window, it was acting weird (highlighting the icon 2 above my mouse location) and then this bug tool popped up! I love this program, thank you!!! Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.2 2008-06-03 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: HighContrastInverse 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 (230 sec old) --------------------- ** (gnome-system-monitor:7696): WARNING **: SELinux was found but is not enabled. Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered GConf backend: There is an unsupported value at path /apps/compiz/plugins/scale/allscreens/options/initiate_edge. Settings from this path won't be read. Try to remove that value so that operation can (gnome-settings-daemon:6200): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (gnome-settings-daemon:6200): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gnome-settings-daemon:6200): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (gnome-settings-daemon:6200): GLib-GObject-CRITICAL **: g_signal_handlers_destroy: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed -------------------------------------------------- Gimmie Version: 0.2.8 Traceback (most recent call last):
+ Trace 202589
printer.connect("attributes_changed", lambda *args: self.emit("reload"))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 475020 ***