GNOME Bugzilla – Bug 441549
crash in Gimmie:
Last modified: 2007-05-31 19:37:58 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: Carbonite 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 (50 sec old) --------------------- (EE) xf86OpenSerial: Cannot open device /dev/wacom No such file or directory. Error opening /dev/wacom : Success (EE) xf86OpenSerial: Cannot open device /dev/wacom No such file or directory. Error opening /dev/wacom : Success Could not init font path element /usr/X11R6/lib/X11/fonts/misc, removing from list! Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/Type1, removing from list! ** (nautilus:5948): WARNING **: Invalid borders specified for theme pixmap: /home/joerg/.themes/Carbonite/gtk-2.0/Menu-Menubar/menuitem.png, borders don't fit within the image Fenstermanager-Warnung: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a0001b (tilda) Fenstermanager-Warnung: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 136249
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 ***