GNOME Bugzilla – Bug 435425
crash in Gimmie:
Last modified: 2007-05-08 19:55:26 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: Glossy Icon Theme: Tango 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 (74 sec old) --------------------- alarm-notify.c:349 (alarm_msg_received) - 0x80c7268: Received at thread b2bf9b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c6b90 alarm-notify.c:337 (alarm_msgport_replied) - 0x80c71a8: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Thu May 3 09:04:23 2007 to Thu May 3 09:04:23 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80c8fe0: Received at thread b2bf9b90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c6d80 alarm-notify.c:337 (alarm_msgport_replied) - 0x80c7268: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml ** Message: <information> U bent nu verbonden met het bedraad netwerk. -------------------------------------------------- Traceback (most recent call last):
+ Trace 132053
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 ***