GNOME Bugzilla – Bug 463715
crash in Gimmie: nothing just opened my l...
Last modified: 2007-08-28 15:19:41 UTC
What were you doing when the application crashed? nothing just opened my laptop lid Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000000 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 (2277 sec old) --------------------- (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed (avant-window-navigator:6961): Wnck-CRITICAL **: wnck_application_get_name: assertion `WNCK_IS_APPLICATION (app)' failed -------------------------------------------------- Traceback (most recent call last):
+ Trace 153004
signal = self.event_mapping[event]
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 417686 ***