GNOME Bugzilla – Bug 473983
crash in Gimmie: Clicking on the Programs...
Last modified: 2007-09-06 09:22:18 UTC
What were you doing when the application crashed? Clicking on the Programs button. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Mirage 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 (10444 sec old) --------------------- (gksu:6240): Gtk-WARNING **: Unable to locate theme engine in module_path: "mirage", Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed /usr/lib/python2.5/site-packages/UpdateManager/Common/SimpleGladeApp.py:335: GtkWarning: Unable to locate theme engine in module_path: "mirage", return gtk.glade.XML(self.glade_path, root, domain) Fontconfig error: "~/.fonts.conf", line 1: XML declaration not well-formed (gksu:6390): Gtk-WARNING **: Unable to locate theme engine in module_path: "mirage", (gksu:6390): Gtk-WARNING **: Unable to locate theme engine in module_path: "mirage", (gksu:6390): Gtk-WARNING **: Unable to locate theme engine in module_path: "mirage", (gksu:6390): Gtk-WARNING **: Unable to locate theme engine in module_path: "mirage", (gksu:6390): Gtk-WARNING **: Unable to locate theme engine in module_path: "mirage", -------------------------------------------------- Traceback (most recent call last):
+ Trace 160690
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
gtk.VBox.__init__(self, False, 4)
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 416060 ***