You're right about why docky hides when this error window pops up, but I just figured out what the "real" problem is and how to trigger it 100% of the time and not 50% of the time as I had stated earlier. Actually whether you want to call it 100% or 50% of the time has more to do with how you define the sequence of events you need to do, to reproduce this bug , which actually begins with an apparent bug in gnome-do when removing launchers from docky.
1. I notice that sometimes dragging a launcher off of docky and releasing it onto the desktop in order to remove it from docky, doesn't work the first time around. The icon reappears in docky, and the animation in which the icon vanishes in a "puff of smoke" doesn't happen. Sometimes I have to add and re-add different icons a few times in order to get this bug to happen, but it happens soon enough. 2. When step 1 does happen, it takes a second drag of the same launcher onto the desktop in order to removie it from docky in a "puff of smoke". 3 Regardless of whether you did step 2 or not, as long as step 1 has occurred, dragging any icon from the gnome menu (doesn't have to be the icon from step 1) causes this error window to appear. For me, I can only return functionality with "killall gnome-panel". Running "killall nautilus" in a terminal doesn't work. This error still happens when I turn Intellihide off (I meant Intellihide all this time, and not autohide as I had incorrectly said earlier). After recovering from this error using "killall gnome-panel", after a few minutes gnome-do crashes and closes unexpectedly with the following message in the terminal, when gnome-do was run from the terminal. The program 'Do' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 12909 error_code 9 request_code 14 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) So is this a gnome-do bug? Or should I file it elsewhere? -- Gnome hang https://bugs.launchpad.net/bugs/433817 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
