GNOME Bugzilla – Bug 477428
crash in Gimmie: Open a PDF via AcroRead ...
Last modified: 2007-09-16 09:53:22 UTC
What were you doing when the application crashed? Open a PDF via AcroRead 8 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-generic #2 SMP Fri Aug 31 00:55:27 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaGilouche Icon Theme: tangogenerator-20070729-1316 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 (110 sec old) --------------------- ** (gnome-session:5115): WARNING **: Couldn't connect to PowerManager Method invoked for Hibernate returned FALSE but did not set error ** Message: <information> You are now connected to the wireless network 'KhoaiLang'. checking for valid crashreport now /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) /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) -------------------------------------------------- Traceback (most recent call last):
+ Trace 163281
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 ***