gimp's detached menus are unmovable

Bug #398011 reported by Mark Chernev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Musca
In Progress
Medium
Sean Pringle

Bug Description

If you detach a menu in Gimp, the menu can not be moved (even if the group it's in is in stacking mode). It also can't be raised to the front by cycling through the windows.

Revision history for this message
Sean Pringle (sean-pringle) wrote :

I do remember the menus you mean, but my version of Gimp seems to lack them. We may be handling a _NET_WM_WINDOW_STATE incorrectly. Please collect the output from "xprop" for one of the menu windows, and attach it to this bug report.

Changed in musca:
assignee: nobody → Sean Pringle (sean-pringle)
importance: Undecided → Medium
Revision history for this message
Mark Chernev (mchernev) wrote :

Every version of gimp has them. All you have to do to detach a menu is right click on an image (or on the main gimp window, in the newer versions of gimp) and then click on the dotted line at the top of the menu. In the following screenshot, I have circled the dotted line I'm talking about:

http://img141.imageshack.us/img141/3201/gimpmenus.png

Here is the output of xwininfo when I click on the detached menu:

http://paste.pocoo.org/show/129181

However, the title of the window that xwininfo gives me (in this case "Image Window") varies, depending on which menu I've detached. For example, if I've detached the Layers menu, the title of the window that xwininfo gives me will be "Layers".

Revision history for this message
Mark Chernev (mchernev) wrote :

Ooops. I just noticed that you asked for the output of xprop, not of xwininfo. Here it is:

http://paste.pocoo.org/show/129183

Revision history for this message
Sean Pringle (sean-pringle) wrote :

Thanks for that. Musca was handling _NET_WM_WINDOW_TYPE_MENU incorrectly. Revision 261 of the development tree has a patch, if you're interested to test it. https://code.launchpad.net/musca

Changed in musca:
status: New → In Progress
Revision history for this message
Mark Chernev (mchernev) wrote :

Thanks. Looks like 261 fixed the bug.

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.