GNOME Bugzilla – Bug 517343
crash in Gimmie: I clicked on "Recently U...
Last modified: 2008-02-24 13:35:37 UTC
What were you doing when the application crashed? I clicked on "Recently Used" button. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-custom1 #1 SMP PREEMPT Tue Feb 12 20:28:58 BRST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human 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 (201 sec old) --------------------- alarm-notify.c:337 (alarm_msgport_replied) - 0x80e79d8: Replied to GUI thread alarm-notify.c:337 (alarm_msgport_repli PID TTY TIME CMD Unable to open desktop file /home/bravo/Desktop/nf7s.desktop for panel launcher: No such file or directory GCJ PLUGIN: thread 0x805e568: NP_GetMIMEDescription GCJ PLUGIN: thread 0x805e568: NP_GetMIMEDescription return GCJ PLUGIN: thread 0x805e568: NP_GetValue GCJ PLUGIN: thread 0x805e568: NP_GetValue: returning plugin name. GCJ PLUGIN: thread 0x805e568: NP_GetValue return GCJ PLUGIN: thread 0x805e568: NP_GetValue GCJ PLUGIN: thread 0x805e568: NP_GetValue: returning plugin description. GCJ PLUGIN: thread 0x805e568: NP_GetValue return (gecko:6802): Gtk-WARNING **: Attempting to read the recently used resources file at `/home/bravo/.recently-used.xbel', but the parser failed: Error reading file '/home/bravo/.recently-used.xbel': Is (gecko:6802): GLib-CRITICAL **: g_bookmark_file_get_size: assertion `bookmark != NULL' failed -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 189671
printer.connect("attributes_changed", lambda p: self.emit("reload"))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 475020 ***