Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

How to reproduce in Awesome WM v3.5.2:

  1. Install OpenJDK or Oracle Java 7. This bug has been observed with both.
  2. Start a new Awesome WM session with the default configuration.
  3. Start either jEdit or PyCharm. This bug has been observed with both.
    • Move the mouse pointer around, and observe how it changes based on whether you are hovering over code, project files or menus. This should work normally.
    • Click and release on the File menu, enter one of the sub-menu, and observe how the item directly under the mouse pointer is focused all the time.
  4. Press Mod4+Space repeatedly until the floating layout is activated (the application will be almost full screen).

At this point, I would expect the mouse to behave like it does with "normal" applications. Instead I observe the following:

  • When clicking and navigating menus with the mouse, the mouse pointer and the focused menu item will be vertically offset from each other, seemingly at the same amount of pixels as the height of the status bar.
  • When hovering over miscellaneous items as before, the cursor icon will be set as if the mouse pointer was higher up on the screen. For example, hovering over the top line of text you will not see a text cursor.

It's as if something doesn't detect that the window coordinates have changed.

A similar but much more annoying bug happens when you open another application in the same tag - the mouse behaviour is as if the window hadn't moved at all.

When you toggle another tag which already has an application open - the "virtual mouse desktop" is moved to the top left of the primary screen.

Since these bugs have been observed in both OpenJDK and Oracle Java, with different Java applications, it seems very likely that the bug is in Awesome WM.

Related question, article. I tried the _JAVA_AWT_WM_NONREPARENTING and wmname fixes, but no go.

share|improve this question
I think the latest Awesome is a reparenting WM so the NONREPARENTING option should not be needed. –  dknight Apr 1 at 7:50
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.