GNOME Bugzilla – Bug 488334
crash in Gimmie:
Last modified: 2007-10-21 21:51:00 UTC
What were you doing when the application crashed? 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 Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: T-ish-Brushed Icon Theme: StillLifeBrushed 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 --------------------- /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:55: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:56: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:57: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. Traceback (most recent call last):
+ Trace 171464
for mi in self.topic.get_context_menu_items():
self._add_templates(menu)
/usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:2: Unable to find include file: "iconrc" /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:54: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored. /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:55: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:56: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/T-ish-Brushed/gtk-2.0/gtkrc:57: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. -------------------------------------------------- Traceback (most recent call last):
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 413620 ***