GNOME Bugzilla – Bug 529219
crash in Gimmie: updating ubuntu
Last modified: 2008-04-27 22:36:32 UTC
What were you doing when the application crashed? updating ubuntu Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Sun Sep 23 18:31:23 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: crystalsvg 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 --------------------- Window manager warning: Log level 8: g_object_unref: assertion `G_IS_OBJECT (object)' failed evolution-alarm-notify-Message: Setting timeout for 33124 1208822400 1208789276 evolution-alarm-notify-Message: Mon Apr 21 19:00:00 2008 evolution-alarm-notify-Message: Mon Apr 21 09:47:56 2008 Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e00056 (Buddy List) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. PID TTY TIME CMD ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19 ERROR: CreateService uri is /usr/share//applications/python2.5.desktop ERROR: could not get file id for /usr/share//applications/python2.5.desktop - unable to continue indexing this file -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 195779
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 ***