GNOME Bugzilla – Bug 432513
crash in Gimmie: I just opend a 'Linux' a...
Last modified: 2007-05-03 03:15:11 UTC
What were you doing when the application crashed? I just opend a 'Linux' and a 'Applications' window. But before and afterwards I recognized a freezing of gimmie, so I could not use that. Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-386 #2 Sun Apr 15 07:34:00 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Outdoors Icon Theme: Tangerine 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 (1773 sec old) --------------------- (search:5525): Gtk-CRITICAL **: gtk_widget_get_display: assertion `GTK_IS_WIDGET (widget)' failed Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at Search.Tray.NotificationArea.UpdateManagerWindow (bool) <0x00020> at Search.Tray.NotificationArea.ManagerFilter (intptr,Gdk.Event) <0x000f3> at (wrapper delegate-invoke) System.MulticastDelegate.invoke_FilterReturn_intptr_Event (intptr,Gdk.Event) <0x0003e> at GdkSharp.FilterFuncWrapper.NativeCallback (intptr,intptr,intptr) <0x00030> at (wrapper native-to-managed) GdkSharp.FilterFuncWrapper.NativeCallback (intptr,intptr,intptr) <0x0003f> in (unmanaged) 0xb650c960 at (wrapper managed-to-native) Gtk.Application.gtk_main () <0x00004> at Gtk.Application.Run () <0x00007> at Gnome.Program.Run () <0x00007> at Search.MainWindow.Main (string[]) <0x000f8> -------------------------------------------------- Traceback (most recent call last):
+ Trace 129940
self.window.property_delete("_NET_WM_STRUT")
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 ***