GNOME Bugzilla – Bug 487808
crash in Gimmie: Clicked 'hide all' in un...
Last modified: 2007-10-22 22:29:52 UTC
What were you doing when the application crashed? Clicked 'hide all' in under programs (which minimized my terminal then clicked library, running stand alone. 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-386 #2 Sun Sep 23 19:47:10 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Ubuntulooks-cool Icon Theme: dlg-etiquette 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 (243 sec old) --------------------- alarm-queue.c:560 (load_alarms_for_today) - From Thu Oct 18 00:00:00 2007 to Thu Oct 18 00:00:00 2007 alarm-queue.c:497 (load_alarms) alarm-queue.c:516 (load_alarms) - Disconnecting old queries alarm-queue.c:526 (load_alarms) - Setting Call backs alarm-queue.c:256 (midnight_refresh_async) - Reschedule the midnight update alarm-queue.c:218 (queue_midnight_refresh) - Refresh at Fri Oct 19 00:00:00 2007 alarm-notify.c:337 (alarm_msgport_replied) - 0x80dae50: Replied to GUI thread alarm-queue.c:1837 (check_midnight_refresh) alarm-queue.c:183Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6000051 (Untitled1 ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1a00019 (tilda) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. -------------------------------------------------- Traceback (most recent call last):
+ Trace 171075
for mi in self.topic.get_context_menu_items():
self._add_templates(menu)
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 413620 ***