gnome-do crashes when Inkscape has more than 1 dialog open

Bug #345092 reported by Bruno Santos
2
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
Confirmed
Undecided
Jason Smith

Bug Description

Binary package hint: gnome-do

If Inkscape is running with more than 1 dialog window open, using the Inkscape icon on the docky to change to Inkscape crashes gnome-do.

I tried with GIMP which has various windows and it doesn't happen, so the crash may have something to do with how Inkscape manages multiple windows?

I have advanced indicators on, I only have one indicator under Inkscape, and if I use the right button menu to choose the Inkscape window, it doesn't crash, only if I use the icon. Also, if I use the menu to choose the window, it doesn't crash the next time I use the icon. If I restart gnome-do and Inkscape isn't requiring attention (blue indicator) before I restart gnome-do, it'll crash again. If the indicator was blue before I restarted gnome-do, it doesn't crash. Does my explanation make sense?

gnome-do exits with the following error:

Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception.
System.InvalidOperationException: Operation is not valid due to the current state of the object
  at System.Linq.Enumerable.First[Window] (IEnumerable`1 source) [0x00000]
  at Docky.Utilities.WindowControl+<FocusWindows>c__AnonStorey22.<>m__85 () [0x00000]
  at GLib.Timeout+TimeoutProxy.Handler () [0x00000]
   at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal)
   at GLib.Timeout+TimeoutProxy.Handler()
   at GLib.Timeout+TimeoutProxy.Handler()
   at Gtk.Application.gtk_main()
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Do.Do.Main(System.String[] args)

I'm on Ubuntu 8.10 running gnome-do 0.8.1-0~intrepid~ppa1 from the do-core ppa.

Revision history for this message
Jason Smith (jassmith) wrote :

Cant confirm but will work on it.

Changed in gnome-do (Ubuntu):
assignee: nobody → jassmith
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.