GNOME Bugzilla – Bug 430430
crash in Gimmie: I left-clicked on the Li...
Last modified: 2007-05-26 01:40:04 UTC
What were you doing when the application crashed? I left-clicked on the Linux section of the gimmie widget. The application crashed after that. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Dirty-Ice Icon Theme: Buuf 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 (2186 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) <memory>:1: Invalid color constant '' CI: {44cc2b80-ac35-4428-9dd1-13c1cf2dfc87} <memory>:1: Invalid color constant '' error : xmlEncodeEntitiesReentrant : input not UTF-8 encoding error : output conversion failed due to conv error, bytes 0xCE 0x30 0xB0 0x31 I/O error : encoder error (Gecko:11145): Gtk-WARNING **: Unable to locate theme engine in module_path: "cleanice", Fontconfig warning: "~/.fonts.conf", line 17: invalid constant used : /usr/bin/compiz.real: pixmap 0x100a2cb can't be bound to texture -------------------------------------------------- Traceback (most recent call last):
+ Trace 128324
for mi in self.topic.get_context_menu_items():
btn.set_submenu(self._make_settings_menu())
img.set_from_pixbuf(item.get_icon(gtk.ICON_SIZE_LARGE_TOOLBAR))
return icon_factory.load_icon(self.menu_entry.get_icon(), icon_size)
assert icon_value, "No icon to load!"
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 419239 ***