GNOME Bugzilla – Bug 425864
crash in Gimmie:
Last modified: 2007-04-03 22:17:30 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks-Marooned Icon Theme: Human_Ultra_Red2 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 --------------------- sh: mpg123: not found sh: mpg123: not found GTK Accessibility Module initialized Bonobo accessibility support initialized /home/minna/.themes/Clearlooks-Marooned/gtk-2.0/gtkrc:46: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored. /home/minna/.themes/Clearlooks-Marooned/gtk-2.0/gtkrc:47: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /home/minna/.themes/Clearlooks-Marooned/gtk-2.0/gtkrc:48: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /home/minna/.themes/Clearlooks-Marooned/gtk-2.0/gtkrc:49: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. (totem:5204): Gtk-WARNING **: Theme directory 96x96/action of theme Human_Ultra_Red2 has no size field totem-video-thumbnailer couln't thumbnail file: 'file:///media/cdrom0/jonobacon-bloodredday.ogg' Reason: Took too much time to thumbnail. GTK Accessibility Module initialized -------------------------------------------------- Traceback (most recent call last):
+ Trace 124628
self.recent_items[recent_item.get_uri()] = recent_item
globals)
for item in filters:
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 417988 ***