GNOME Bugzilla – Bug 455692
crash in Gimmie: I clicked on "Favourites...
Last modified: 2007-08-30 22:13:09 UTC
What were you doing when the application crashed? I clicked on "Favourites" 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-powerpc #3 Thu Jun 7 19:32:55 UTC 2007 ppc X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (177 sec old) --------------------- (jpilot:12517): Gtk-CRITICAL **: gtk_text_buffer_insert: assertion `text != NULL' failed (jpilot:12517): Gtk-CRITICAL **: gtk_text_buffer_insert: assertion `text != NULL' failed (jpilot:12517): Gtk-CRITICAL **: gtk_text_buffer_insert: assertion `text != NULL' failed (jpilot:12517): Gtk-CRITICAL **: gtk_text_buffer_insert: assertion `text != NULL' failed (gnome-panel:6281): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x100a2048 (gnome-panel:6281): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x100a2048 (gnome-panel:6281): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x100a2048 (gnome-panel:6281): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x100a2048 -------------------------------------------------- Traceback (most recent call last):
+ Trace 147096
item.pin()
bookmarks.add_bookmark_item(self)
self.add_bookmark(item.get_uri(), item.get_mimetype(), classname)
assert uri, "Must specify URI to bookmark"
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 415898 ***