GNOME Bugzilla – Bug 481677
crash in Gimmie: this is a virtual machin...
Last modified: 2007-10-05 21:55:12 UTC
What were you doing when the application crashed? this is a virtual machine, i use it to prove software (as gimmie) 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 Sun Sep 23 19:50:39 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome 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 (20 sec old) --------------------- The program 'tilda' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAccess (attempt to access private resource denied)'. (Details: serial 11 error_code 10 request_code 33 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) (tilda:5633): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed (tilda:5633): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3601e7a (tilda) Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 166472
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 ***