GNOME Bugzilla – Bug 448708
crash in Gimmie:
Last modified: 2007-06-23 17:01:10 UTC
What were you doing when the application crashed? 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: Clearlooks 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 (67 sec old) --------------------- /usr/lib/python2.5/site-packages/GDebi/GDebi.py:95: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:95: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) GLib-GObject-WARNING **: gsignal.c:1715: handler `491' of instance `0x979bcd0' is not blocked at /usr/bin/gscan2pdf line 469. Error: Document has not the mandatory ending %EOF /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:95: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) warnings.warn("apt API not stable yet", FutureWarning) /usr/lib/python2.5/site-packages/GDebi/GDebi.py:95: GtkWarning: gdk_window_set_cursor: assertion `GDK_IS_WINDOW (window)' failed self.window_main.set_sensitive(False) Fenstermanager-Warnung: Ungültiges WM_TRANSIENT_FOR-Fenster 0x4400006 festgelegt für 0x4402c64 (Choose Fil). -------------------------------------------------- Traceback (most recent call last):
+ Trace 141822
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 ***