GNOME Bugzilla – Bug 490244
crash in Gimmie: checking it out for the ...
Last modified: 2007-10-25 23:20:19 UTC
What were you doing when the application crashed? checking it out for the first time 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 (428 sec old) --------------------- ERROR: CreateService uri is /usr/share//applications/screensavers/ubuntu_theme.desktop ERROR: could not get file id for /usr/share//applications/screensavers/ubuntu_theme.desktop - unable to continue indexing this file ERROR: execution of prepared query CreateService failed due to constraint failed with return code 19 ERROR: CreateService uri is /usr/share//applications/gnome-screensaver-preferences.desktop ERROR: could not get file id for /usr/share//applications/gnome-screensaver-preferences.desktop - unable to continue indexing this file ** (gnome-about-me:7360): WARNING **: FIXME: wait for completion unimplemented Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3f specified for 0x3400002 (Opera). checking for valid crashreport now checking for valid crashreport now checking for valid crashreport now Window manager warning: last_focus_time (3631238591) is greater than comparison timestamp (3631238456). This most likely represents a buggy client sending inaccurate timestamps in messages such as _N checking for valid crashreport now checking for valid crashreport now Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3f specified for 0x3400002 (Welcome to). -------------------------------------------------- Gimmie Version: 0.2.7 Traceback (most recent call last):
+ Trace 172841
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 ***