GNOME Bugzilla – Bug 450012
crash in Gimmie: Clicking on the 'linux' ...
Last modified: 2007-06-23 16:32:08 UTC
What were you doing when the application crashed? Clicking on the 'linux' menu so that I could open Amarok. 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 Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: OSX 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 (2229 sec old) --------------------- to Fri Jun 22 10:25:43 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:337 (alarm_msgport_replied) - 0x80d8140: Replied to GUI thread alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0 alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task alarm-notify.c:349 (alarm_msg_received) - 0x808c818: Connecting to daemon [ ###] Connecting to daemon [ ### ] Connecting to daemon [ ### ] Connecting to daemon [ ### ] ** Message: <information> You are now connected to the wireless network 'belkin54g'. sh: disown: not found ** (gnome-cups-icon:5374): WARNING **: IPP request failed with status 1280 ** Message: <information> You are now connected to the wireless network 'belkin54g'. -------------------------------------------------- Traceback (most recent call last):
+ Trace 142858
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 ***