Bottom Panel Covering Bottom Of Windows (Strut Issue?)

Bug #1397470 reported by Buford T. Justice
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
marco (Ubuntu)
Fix Released
Undecided
Unassigned
mate-panel (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I am using Ubuntu MATE 14.04.1 LTS which I just installed a couple of days ago. I didn't notice this issue until now. The bottom panel is covering the bottoms of maximized windows.

xprop -root | grep WORKAREA

_NET_WORKAREA(CARDINAL) = 0, 24, 1680, 1002, 0, 24, 1680, 1002, 0, 24, 1680, 1002, 0, 24, 1680, 1002

xprop -root | grep _NET_DESKTOP_GEOMETRY

_NET_DESKTOP_GEOMETRY(CARDINAL) = 1680, 1050

xrandr

    Screen 0: minimum 320 x 200, current 1440 x 900, maximum 16384 x 16384
    DFP1 disconnected (normal left inverted right x axis y axis)
    DFP2 disconnected (normal left inverted right x axis y axis)
    DFP3 disconnected (normal left inverted right x axis y axis)
    DFP4 disconnected (normal left inverted right x axis y axis)
    DFP5 disconnected (normal left inverted right x axis y axis)
    DFP6 connected 1440x900+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
       1680x1050 60.0 +
       1600x1200 60.0
       1400x1050 60.0
       1280x1024 60.0 75.0
       1440x900 75.0 59.9*
       1280x960 60.0
       1280x800 60.0
       1152x864 60.0 75.0
       1280x768 60.0
       1280x720 60.0
       1024x768 75.0 70.1 60.0
       800x600 72.2 75.0 60.3 56.2
       640x480 75.0 72.8 66.6 59.9
    CRT1 disconnected (normal left inverted right x axis y axis)

I am using 1440x900 screen resulution on a 16:10 monitor. Thanks!

Revision history for this message
Buford T. Justice (btjustice) wrote :
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

The problem here is that the X atoms _NET_WORKAREA and _NET_DESKTOP_GEOMETRY have wrong values. They are set to 1680x1050, which is the native resolution of the display (+), but the display is really set to 1440x900.

Checking _NET_WORKAREA we can see that there is 24 pixels reserved at the top and bottom for the panels. But because the system thinks the display is 1050 pixels tall, the reserved area at the bottom is from 1026 to 1050, which is off the bottom of the visible display area, and so does nothing.

The panel is still constrained to the display though, so it overlaps maximized windows.

This is most likely a problem with the window manager, with the second most likely trouble causer being gdk.

description: updated
Revision history for this message
Alistair Buxton (a-j-buxton) wrote :

User's login screen is running at the native resolution, but at the desktop a custom resolution is applied. So my working theory is this is a race condition between window manager and settings manager:

At login, screen is 1680x1050.

After login, window manager starts, and queries resolution from GDK, which says 1680x1050.

In another process, settings manager starts up and changes screenmode to 1440x900.

Window manager doesn't notice the screenmode changed and writes the old values into the _NET atom.

Changed in ubuntu-mate:
importance: Undecided → Low
Revision history for this message
hmhmhm (hmhmhm) wrote :

Same issue here. Means I cannot use maximised windows, which makes for a user-unfriendly experience. I have to resizes windows manually to make them fit. Such a basic thing, should be a lot higher than 'low'.

Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

Can you confirm if this issue is still present in Ubuntu MATE 16.04 Alpha 2? Using the live image will be sufficient.

Changed in ubuntu-mate:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubuntu-mate because there has been no activity for 60 days.]

Changed in ubuntu-mate:
status: Incomplete → Expired
Changed in ubuntu-mate:
status: Expired → Confirmed
Victor Kareh (vkareh)
Changed in ubuntu-mate:
assignee: nobody → Victor Kareh (vkareh)
Victor Kareh (vkareh)
Changed in ubuntu-mate:
status: Confirmed → In Progress
Norbert (nrbrtx)
tags: added: trusty
Norbert (nrbrtx)
tags: added: xenial
removed: trusty
Revision history for this message
Norbert (nrbrtx) wrote :

Can you reproduce this bug with newer version of Ubuntu MATE?

Norbert (nrbrtx)
Changed in ubuntu-mate:
status: In Progress → Won't Fix
Revision history for this message
Victor Kareh (vkareh) wrote :
Revision history for this message
Norbert (nrbrtx) wrote :

Ok, I'm sorry. I did big bug-sorting last days, may be mistaken.

Reverted to Confirmed. If you want to set other status, then feel free to do so :)

Changed in ubuntu-mate:
status: Won't Fix → Confirmed
tags: added: bionic focal hirsute impish
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

This was fixed via marco 1.26.0-0ubuntu1 which was introduced in Ubuntu MATE 21.10

Changed in marco (Ubuntu):
status: New → Fix Released
Changed in mate-panel (Ubuntu):
status: New → Invalid
Changed in ubuntu-mate:
assignee: Victor Kareh (vkareh) → nobody
no longer affects: ubuntu-mate
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.