GNOME Bugzilla – Bug 441468
crash in Gimmie:
Last modified: 2007-05-31 19:38:08 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 (87 sec old) --------------------- ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) File /home/ste/skype_debian-1.3.0.53-1_i386.deb has finished changing flushing all words Finished indexing. Waiting for new events... /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 136185
self._show()
self.topic_win = self.topic.get_topic_window()
self.topic_window = TopicMenu(self)
TopicView.__init__(self, topic)
self.sidebar = Sidebar(topic)
gtk.VBox.__init__(self, False, 4)
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 416060 ***