GNOME Bugzilla – Bug 510604
crash in Gimmie: Uh oh. This time, I was ...
Last modified: 2008-03-10 13:15:32 UTC
What were you doing when the application crashed? Uh oh. This time, I was looking through my recently updated gimmie. I had updated with gimmie not on the panel, then put it on the panel. When I started flicking though things (looking though Linux>Recently Used) it crashed. Sad day. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Groove Icon Theme: area-blue 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 (50 sec old) --------------------- alarm-queue.c:537 (load_alarms) - Disconnecting old queries alarm-queue.c:547 (load_alarms) - Setting Call backs alarm-queue.c:238 (midnight_refresh_async) - Reschedule the midnight update alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Sun Jan 20 00:00:00 2008 alarm-notify.c:337 (alarm_msgport_replied) - 0x80e0d80: Replied to GUI thread alarm-queue.c:1832 (check_midnight_refresh) alarm-qu/usr/lib/python2.5/site-packages/UpdateManager/Common/SimpleGladeApp.py:335: GtkWarning: Unable to locate theme engine in module_path: "rezlooks", return gtk.glade.XML(self.glade_path, root, domain) /usr/lib/python2.5/site-packages/UpdateManager/Common/SimpleGladeApp.py:335: GtkWarning: Unable to locate theme engine in module_path: "rezlooks", return gtk.glade.XML(self.glade_path, root, domain) (gksu:23596): Gtk-WARNING **: Unable to locate theme engine in module_path: "rezlooks", (gksu:24326): Gtk-WARNING **: Unable to locate theme engine in module_path: "rezlooks", -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 185954
printer.connect("attributes_changed", lambda p: 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 ***