GNOME Bugzilla – Bug 481175
crash in Gimmie: Just opened a text file ...
Last modified: 2007-09-28 11:20:40 UTC
What were you doing when the application crashed? Just opened a text file in gedit 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: Glossy Icon Theme: Tango 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 (23 sec old) --------------------- ** Message: GetValue variable 2 (2) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3e00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** Message: GetValue variable 1 (1) ** 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) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (thunar:9845): Gtk-WARNING **: Error loading theme icon for stock: Icon 'Terminal' not present in theme (thunar:9845): Gtk-WARNING **: Error loading theme icon for stock: Icon 'Terminal' not present in theme -------------------------------------------------- Traceback (most recent call last):
+ Trace 166093
self.recent_items[recent_item.get_uri()] = recent_item
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. Or you can also try the latest SVN (443) which should contain a patch for this crasher. Feel free to reopen this if you think it is not solved. *** This bug has been marked as a duplicate of 417988 ***