GNOME Bugzilla – Bug 570962
crash in Deskbar: Trying to move the bar f...
Last modified: 2009-02-09 17:48:24 UTC
What were you doing when the application crashed? Trying to move the bar from the top to the bottom of the desktop. Distribution: Ubuntu 8.04 (hardy) Gnome Release: 2.22.3 2008-07-09 (Ubuntu) BugBuddy Version: 2.22.0 System: Linux 2.6.24-23-generic #1 SMP Mon Jan 26 00:13:11 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: GlassyBleu Icon Theme: GlassyBleu 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 (95 sec old) --------------------- (evolution:5901): Gdk-CRITICAL **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (gc)' failed (evolution:5901): e-table-CRITICAL **: e_table_draw_elided_string: assertion `gc != NULL' failed (evolution:5901): Gdk-CRITICAL **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (gc)' failed (evolution:5901): e-table-CRITICAL **: e_table_draw_elided_string: assertion `gc != NULL' failed (evolution:5901): Gdk-CRITICAL **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (gc)' failed (evolution:5901): e-table-CRITICAL **: e_table_draw_elided_string: assertion `gc != NULL' failed (evolution:5901): Gdk-CRITICAL **: gdk_gc_set_clip_rectangle: assertion `GDK_IS_GC (gc)' failed (evolution:5901): e-table-CRITICAL **: e_table_draw_elided_string: assertion `gc != NULL' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 212352
self.module_list.move_module_to_bottom(iter)
self.move_after(iter, self.get_iter(self._bottom_enabled_path))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 488665 ***