Maximized windows placed incorrectly (metacity and compiz)

[Nikola Kasabov]

When window is maximized on the left end of the screen there is left one pixel column with the window border. This prevents for example opening of the Firefox sidebar. The mouse must be moved one pixel away from the left end of the screen to open the sidebar.

There is screenshot attached. The language is bulgarian, but this is the same menu shown when it is right clicked on the window titlebar. The menu is shown with right click on the left end of the screen. This means that on the left side of the screen there remains window border despite it is maximized.

This is the case with all windows when the window border is "Human" no matter with metacity or compiz.

[Kenneth Wimer (kwwii)]

The one pixel left border issue was a work around for a compiz bug. I am not sure how this is negatively affecting your firefox window. I can open and close the sidebar via the menu entry and nothing seems strange. Are you using the default firefox settings or have you changed something yourself?

[Nikola Kasabov (nikaas)]

I have an add-on (all-in-one sidebar). To open this sidebar I need to go to the left border of the screen.

This happened after the last update (2-3 days ago). I don't know why is this done and it's not fatal but I think it's not how it must be.

[TenLeftFingers (tenleftfingers)]

Confirming this bug given that Kenneth is also aware of the 'one pixel' issue.

[Dave Rolsky (autarch)]

I'm pretty sure this is also causing a problem I just noticed with Hardy.

I usually have Firefox opened full screen. Typically, I'll move the cursor all the way to the left to get it out of the way and then use the scroll wheel. However, recently the scroll wheel events stopped being picked up by Firefox. I tried tweaking the theme and changing the window border to "simple", and it picked up the scroll wheel events, so I'm guessing this is the same issue.

[Dave Rolsky (autarch)]

This is definitely the same problem. I made a tweaked theme and changed left_width for fullscreen windows back to 0, and my problem is solved.

[TenLeftFingers (tenleftfingers)]

If you notice any side affects to your adjustment, posting them here would be really helpful. I'm unassigning myself from this bug so the developers know it needs attention, but I'm still on the mailing list.

[Dave Rolsky (autarch)]

I should point out that I'm _not_ running compiz, so I don't see the placement bug that the change to left_width (from 0 to 1) was intended to solve.

[Kenneth Wimer (kwwii)]

This real compiz bug apparently only effects people with specific graphics cards. For those effected it randomly draws the window decoration totally incorrect on maximized windows.

[Thomas Doggette (tdoggette)]

I've got this problem on Hardy using the restricted drivers for my Nvidia 8800GT. Changing the "Window Border" to anything else in the Appearance settings fixes it, but I'd really rather have the human theme.

[notnot (notnot)]

I'm seeing the white column at the left side of a maximized window too, and
would like to get rid of it, and keep using the Human theme. I'm new on Ubuntu, can someone please explain me where to find the theme files?

[notnot (notnot)]

Never mind my previous question, I found the answer myself. I managed to edit the Human theme metacity-1.xml and set left_width="0" for maximized windows. This makes a maximized window take up all available screen width, which is what is expected. I have (so far) not experienced the 'compiz bug'.

[Tor Klingberg (tor-klingberg)]

I can confirm this, and it keeps me from scrolling with the mouse wheel when the cursor is on the left edge. Am I right that the netbook remix does not use Compiz? In that case, could we set the left_width="0" in UNR, since it maximizes all windows?

[Joshua Wiegand (bmoresbest55)]

I am having this issue in unity 5.10 and ubuntu 12.04 beta 2. It is fully updated as of 4/15/12. The pixel column is off by 1 with the window maxed out and shows the background. It does this with all windows that are maximized.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[N1ck 7h0m4d4k15 (nicktux)]

As part of the bug clean up ahead of 16.04 LTS I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 LTS development cycle.