GNOME Bugzilla – Bug 436315
crash in Gimmie: opened pdf file
Last modified: 2007-05-23 22:31:52 UTC
What were you doing when the application crashed? opened pdf file Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 06:17:24 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Orange-look 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 --------------------- Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Document has not the mandatory ending %EOF Error: Kid object (page 79) is wrong type (null) Error: Kid object (page 79) is wrong type (null) Error: Page count in top-level pages object is incorrect /home/ibrkanac/.themes/Orange-look/gtk-2.0/gtkrc:43: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /home/ibrkanac/.themes/Orange-look/gtk-2.0/gtkrc:44: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /home/ibrkanac/.themes/Orange-look/gtk-2.0/gtkrc:45: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. -------------------------------------------------- Traceback (most recent call last):
+ Trace 132692
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. *** This bug has been marked as a duplicate of 417988 ***