! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
NVidia: Windows disappear when zooming
Status:
RESOLVED: FIXED

Comments

Description Alistair Buxton 2019-09-16 15:15:44 CEST
Some windows disappear when zooming. The most common windows to disappear are Firefox and xfce4-panel. It doesn't always happen immediately, but always happens after a couple of seconds of zooming in and out and panning around. The windows reappear after zooming all the way out back to the normal desktop view.

I have bisected it back to somewhere between these commits:

commit 11493fd453481b4c832986b1123160435b53a27a (refs/bisect/bad)
Author: Olivier Fourdan <fourdan@xfce.org>
Date:   Sun May 12 12:03:18 2019 +0200

    Revert "compositor: Draw to back buffer"
    
    This change is incompatible with NVidia closed source driver and
    causes a blank screen.
    
    Thanks-to: Philip Müller <philm@manjaro.org>
    
    This reverts commit 97c051b865623cf7133d74d0281ed6ad1cf4c3d6.


commit 97c051b865623cf7133d74d0281ed6ad1cf4c3d6 (refs/bisect/skip-97c051b865623cf7133d74d0281ed6ad1cf4c3d6)
Author: Olivier Fourdan <fourdan@xfce.org>
Date:   Tue May 7 20:25:01 2019 +0200

    compositor: Draw to back buffer
    
    Draw the texture to the back buffer instead of the front buffer and
    `glXSwapBuffers()` will take care of swapping the back to front.
    
    Signed-off-by: Olivier Fourdan <fourdan@xfce.org>

Commits between these two always produce a blank screen on NVidia. By selectively reverting I have found the following:

8a5fc3b with 97c05 reverted: good
f343d4a with 97c05 reverted: blank screen
3eecc5e with f343d4a reverted and then 97c05 reverted: good

So I think the bug is either between 11493fd and 3eecc5e or it is caused by f343d4a.
Comment 1 Olivier Fourdan editbugs 2019-09-16 15:17:47 CEST
The bug is just that zooming defeats the fence...
Comment 2 Alistair Buxton 2019-09-17 21:48:52 CEST
Okay, can I assume from this that you know how to fix it and don't need me to keep investigating?
Comment 3 Alistair Buxton 2019-09-21 20:37:36 CEST
e5462de37a4b0a18 today seems to have fixed this, or at least made it a lot harder to reproduce.

Bug #15967

Reported by:
Alistair Buxton
Reported on: 2019-09-16
Last modified on: 2020-05-21

People

Assignee:
Olivier Fourdan
CC List:
1 user

Version

Version:
unspecified

Attachments

Additional information