GNOME Bugzilla – Bug 728385
Portions of some windows (XTerm, VLC) do not show when maximized
Last modified: 2021-07-05 13:48:38 UTC
At first, when you maximize certain windows in gnome-shell 3.12.0, portions of them do not render. Steps to reproduce in gnome-shell: 1. Open xterm. It should not be maximized. 2. Maximize xterm by dragging the window to the top of the screen. Do not pause at the top of the screen long enough for the blue rectangle animation to appear. 3. At this point, the xterm window is fully maximized, but only a portion of the window and its titlebar are shown properly. The portion of the window correctly displayed happens to be the same size as the original window. (screenshot1.png) 4. Partial redraws of the window contents can cause some portions of the window to show up. (screenshot2.png) 5. Triggering a full redraw (switching workspaces, etc) makes the remainder of the window display properly. (screenshot3.png) This happens with xterm and vlc (With vlc, only the window borders have this issue, not the main application.) I cannot reproduce the issue with gedit or firefox. I filed this against mutter because it seems like a compositor issue. This is new in Gnome 3.12. Versions: * Gnome shell 3.12.0 * Mutter 3.12.0 * Mesa 10.1.0, using the open source drivers on an AMD/ATI Radeon HD 6770
Created attachment 274552 [details] screenshot1: XTerm first maximized, but not rendered correctly
Created attachment 274553 [details] screenshot2: partial redraw of screen
Created attachment 274554 [details] screenshot3: full redraw of screen
I can confirm this bug under Arch Linux, GNOME 3.12.2. Only GTK2 and Qt applications seem affected, GTK3 works fine.
https://bbs.archlinux.org/viewtopic.php?pid=1452542#p1452542
Can you reproduce it on other graphics cards or other drivers? I can't reproduce this with xterm here.
I can also reproduce this on the intel mesa driver (mesa 10.2.6).
I can also confirm this bug using gnome shell 3.12.2 and the open source radeon driver. Exporting CLUTTER_PAINT=disable-clipped-redraws:disable-culling makes the issue disappear for me, but apparently not for other users (i posted my temporary fix also on the linked Arch Forum thread from comment 5).
We were seeing this under Intel / SNA somewhat, but that was a driver bug: https://bugs.freedesktop.org/show_bug.cgi?id=81551 https://bugzilla.gnome.org/show_bug.cgi?id=733397 Perhaps Radeon needs something similar? I'm not sure myself. I'd like to hear if anybody who has Intel / NVIDIA can reproduce after those patches have been applied.
I can confirm that, as in comment 8, the issue disappears when I set CLUTTER_PAINT=disable-clipped-redraws:disable-culling
(In reply to comment #9) > We were seeing this under Intel / SNA somewhat, but that was a driver bug: > > https://bugs.freedesktop.org/show_bug.cgi?id=81551 > https://bugzilla.gnome.org/show_bug.cgi?id=733397 > > Perhaps Radeon needs something similar? I'm not sure myself. I'd like to hear > if anybody who has Intel / NVIDIA can reproduce after those patches have been > applied. This bug only applies for DRI3 on intel, isn't it? I thought, the radeon driver does not implement this on DDX side yet?
I've tried to: - enable dri3 in xf86-video-intel (disabled by default in Arch Linux), and apply the patch from https://bugs.freedesktop.org/show_bug.cgi?id=81551#c7 - change from SNA to UXA and Glamor - use my Radeon HD 6450 with xf86-video-ati And I could confirm the issue in each case. However, exporting CLUTTER_PAINT=disable-clipped-redraws:disable-culling -before- gnome-session starts solved the problem for me.
Following up here. I've spent some more time trying to reproduce this, and still couldn't. It sounds like damage rectangles aren't being sent or processed correctly. Do you still see this, on Intel and Radeon?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help.