GNOME Bugzilla – Bug 432496
crash in Gimmie:
Last modified: 2007-05-26 01:13:18 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-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina-GreenMod Icon Theme: nuoveXT-1.6 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 (65 sec old) --------------------- alarm-queue.c:2008 (alarm_queue_add_async) - 0x80c4630 alarm-notify.c:337 (alarm_msgport_replied) - 0x80c4d00: Replied to GUI thread alarm-queue.c:560 (load_alarms_for_today) - From Mon Apr 23 08:10:39 2007 to Mon Apr 23 08:10:39 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-notify.c:349 (alarm_msg_received) - 0x80caa88: Received at thread b452ab90 alarm-queue.c:2008 (alarm_queue_add_async) - 0x80 (gnome-panel:6582): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -13 and height 26 Desktop-Datei file:///home/peter/Desktop/synaptic.desktop konnte nicht für Panel-Starter : geöffnet werdenNo such file or directory ** (gnome-cups-icon:6624): WARNING **: Das Systembenachrichtigungssymbol für Drucker konnte nicht gestartet werden, da der CUPS-Server nicht kontaktiert werden konnte. (mail-notification:6613): mail-notification-WARNING **: m00d6bcd@mail.peterkroener.de: Die SASL-Authentifizierung konnte nicht gestartet werden: SASL(-4): no mechanism available: No worthy mechs found -------------------------------------------------- Traceback (most recent call last):
+ Trace 129924
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 ***