GNOME Bugzilla – Bug 447012
crash in Gimmie:
Last modified: 2007-06-23 17: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-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: Human 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 (1055 sec old) --------------------- Trying Plugin: NoteOfTheDay.dll ... NoteOfTheDayPlugin. [DEBUG]: Done. Trying Plugin: PrintNotes.dll ... PrintPlugin. [DEBUG]: Done. Trying Plugin: StickyNoteImport.dll ... StickyNoteImporter. [DEBUG]: Done. (gnome-panel:5841): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24 [DEBUG]: StickyNoteImporter: Sticky Notes XML file does not exist or is invalid! [DEBUG]: Tomboy remote control active. [DEBUG]: EnableDisable Called: enabling... True [DEBUG]: Binding key '<Alt>F12' for '/apps/tomboy/global_keybindings/show_note_menu' [DEBUG]: Binding key '<Alt>F11' for '/apps/tomboy/global_keybindings/open_start_here' [DEBUG]: Binding key '<Control><Alt>N' for '/apps/tomboy/global_keybindings/create_new_note' [DEBUG]: Quitting Tomboy. Ciao! [DEBUG]: Saving unsaved notes... ** Message: <information> Sie sind nun mit dem drahtlosen Netzwerk 'wl-plug-inn' verbunden. -------------------------------------------------- Traceback (most recent call last):
+ Trace 140558
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 ***