GNOME Bugzilla – Bug 505780
crash in Deskbar: pressing down with nothi...
Last modified: 2007-12-29 11:55:37 UTC
What were you doing when the application crashed? pressing down with nothing selected in prefrences dialogue. Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.1 2007-10-19 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 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 --------------------- <gtk.gdk.Pixbuf object at 0xa785a0 (GdkPixbuf at 0xc23990)> <gtk.gdk.Pixbuf object at 0xa785a0 (GdkPixbuf at 0xb85230)> <gtk.gdk.Pixbuf object at 0xa785a0 (GdkPixbuf at 0xb851e0)> <gtk.gdk.Pixbuf object at 0xa785a0 (GdkPixbuf at 0xc23990)> <gtk.gdk.Pixbuf object at 0xa785a0 (GdkPixbuf at 0xc3cc50)> <gtk.gdk (PySwitcher.py:30233): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed (PySwitcher.py:30233): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed (PySwitcher.py:30233): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed (PySwitcher.py:30233): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed (PySwitcher.py:30233): Wnck-CRITICAL **: update_client_list: assertion `reentrancy_guard == 0' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 183135
self.module_list.move_module_down(iter)
iter_next = self.iter_next(iter)
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 490981 ***