GNOME Bugzilla – Bug 467905
crash in Gimmie:
Last modified: 2007-09-08 22:12:51 UTC
What were you doing when the application crashed? Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.6 2007-08-14 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-9-386 #1 Fri Aug 3 00:21:52 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 (524 sec old) --------------------- (trackerd:5773): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed PID TTY TIME CMD (trackerd:5773): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (trackerd:5773): GLib-CRITICAL **: g_hash_table_lookup: assertion `hash_table != NULL' failed (trackerd:5773): GLib-CRITICAL **: g_hash_table_size: assertion `hash_table != NULL' failed Предупреждение менеджера окон: неверный параметр WM_TRANSIENT_FOR окна 0x3c00081 указан для 0x3c01cd3 (). ERROR: execution of prepared query CreateService failed due to columns Path, Name are not unique with return code 1 ERROR: CreateService uri is /usr/share//applications/restricted-manager.desktop ERROR: could not get file id for /usr/share//applications/restricted-manager.desktop - unable to continue indexing this file (trackerd:5773): GLib-CRITICAL **: g_hash_table_size: assertion `hash_table != NULL' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 156101
self.scroll.connect("size-request", lambda w, req: self._scroll_get_best_size(w, req))
upper = min(upper, int(self.get_screen().get_height() * 0.7))
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 417988 ***