GNOME Bugzilla – Bug 487483
crash in Gimmie: Clicked on Recently used...
Last modified: 2007-10-22 22:38:32 UTC
What were you doing when the application crashed? Clicked on Recently used tab Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 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 (475 sec old) --------------------- b7f3e000-b7f40000 rw-p 00019000 08:05 2147 /lib/ld-2.6.1.so bfbe9000-bfbfe000 rw-p bfbe9000 00:00 0 [stack] ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso] (synaptic:6481): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS (synaptic:6481): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:6481): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:6481): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:6481): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:6481): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 170832
printer.connect("attributes_changed", lambda p: self.emit("reload"))
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 475020 ***