Bug 441904 - KWin 5.22.5 regression on NVIDIA: Black screen when putting on/taking off full screen a previously maximized window.
Summary: KWin 5.22.5 regression on NVIDIA: Black screen when putting on/taking off ful...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.22.5
Platform: Arch Linux Linux
: VHI normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: regression
: 442059 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-09-02 10:13 UTC by tonikelope
Modified: 2021-12-16 16:21 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.23


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tonikelope 2021-09-02 10:13:57 UTC
SUMMARY
Black screen when putting on/taking off full screen a previously maximized window.

STEPS TO REPRODUCE
1. Open some window.
2. Maximize it
3. Press F11

OBSERVED RESULT
Black screen

EXPECTED RESULT
Full screen window

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Linux 5.10.61-1-lts 64bits
X11
nvidia-390xx
Dual monitor
Comment 1 tonikelope 2021-09-02 10:23:49 UTC
Occurs with OpenGL 3.1 and 2.0
Comment 2 Colin J Thomson 2021-09-02 13:53:03 UTC
I can confirm this..
It works OK in wayland but not Xorg which is my default of choice. 
Downgrading kwin* to 5.22.4 resolves the issue for me.

KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.14.0-60.vanilla.1.fc34.x86_64 (64-bit)
Graphics Platform: X11
Comment 3 tonikelope 2021-09-02 16:06:52 UTC
Downgrading kwin* to 5.22.4 resolves the issue for me too, thanks.
Comment 4 Nate Graham 2021-09-02 18:49:19 UTC
Cannot reproduce on current git master with Intel HD620 iGPU. Is everyone affected using an NVIDIA GPU?

Is anyone who can reproduce the issue able to perform a git bisect, by any chance? The list of substantive changes between 5.22.4 and 5.22.5 is thankfully fairly small: https://invent.kde.org/plasma/kwin/-/commits/Plasma/5.22
Comment 5 Colin J Thomson 2021-09-02 19:32:51 UTC
Yep nVidia 470.xx here - Single Monitor. As mentioned it works OK in Wayland if that helps tracking it down.
Comment 7 alexmateescu 2021-09-02 22:16:23 UTC
It happens with Firefox (92.0b9), but only on the secondary monitor.
It doesn't happen with Chromium (93.0)
Nvidia 470.63 with 
Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-6600K CPU @ 3.50GHz
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2
Comment 8 alexmateescu 2021-09-02 22:20:28 UTC
Nevermind, it happens on the primary with Firefox as well. I forgot to hide the taskbar (allow windows to cover the taskbar, since I can't hide the taskbar because of an old bug).
Comment 9 Kirby 2021-09-02 22:49:24 UTC
I also have this issue.  Open Firefox which is maximized in my case.  Go to youtube and click full screen on any video.  This results in a black/blank screen.  This does not happen if firefox is not maximized.  I have two monitors and this bug occurs on either monitor.  I don't use the system/taskbar tray and have it replaced with Latte.

Very similar to what a number of us experience in Bug 427920 except the "fix" previously was to disable the Full Screen effect in Desktop Effects.  This no longer fixes the issue as mentioned in Bug 427920.

Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-4690K CPU @ 3.50GHz
Memory: 19.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1080/PCIe/SSE2
Comment 10 Joe 2021-09-13 05:27:46 UTC
Getting this on my dual monitor setup (only on the secondary monitor), only when Firefox is already maximed.

Might be a dupe of: https://bugs.kde.org/show_bug.cgi?id=427920 ??
Comment 11 angnysa 2021-09-14 02:56:48 UTC
I reproduce the bug with a non-maximized but full-sized window, on the primary and secondary monitors, with and without toolbars.

To reproduce on my 2560x1440 monitors (Nvidia driver):
1- resize the firefox window+decorations to the monitor resolution (2560x1440 in my case, adjust to yours). The window can be anywhere, only the size is important.
2- press F11

Expected:
Full Screen window

Actual:
Black screen


Also tested and reproduced with VLC, same procedure.


KDE Info:

Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Kernel Version: 5.13.13-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2
Comment 12 Mikael Hirki 2021-09-14 07:27:27 UTC
I'm experiencing the same bug. My test case is opening a Youtube video and making it full screen. I tried reverting each commit between 5.22.4 and 5.22.5.  Reverting this commit fixes the issue for me:

https://invent.kde.org/plasma/kwin/-/commit/f432ba7821cea2302d040c8bfc7e3cb7d9540874

--

Operating System: Gentoo Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.13.16-gentoo (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i9-9900KS CPU @ 4.00GHz
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2

Google Chrome version: 93.0.4577.63
Comment 13 Vlad Zahorodnii 2021-09-14 11:10:17 UTC
(In reply to Mikael Hirki from comment #12)
> I'm experiencing the same bug. My test case is opening a Youtube video and
> making it full screen. I tried reverting each commit between 5.22.4 and
> 5.22.5.  Reverting this commit fixes the issue for me:
> 
> https://invent.kde.org/plasma/kwin/-/commit/
> f432ba7821cea2302d040c8bfc7e3cb7d9540874
I don't think reverting that commit is right. If you disable fullscreen effect and maximize effect, is the issue still reproducible?
Comment 14 angnysa 2021-09-14 11:31:46 UTC
(In reply to Vlad Zahorodnii from comment #13)
> (In reply to Mikael Hirki from comment #12)
> > I'm experiencing the same bug. My test case is opening a Youtube video and
> > making it full screen. I tried reverting each commit between 5.22.4 and
> > 5.22.5.  Reverting this commit fixes the issue for me:
> > 
> > https://invent.kde.org/plasma/kwin/-/commit/
> > f432ba7821cea2302d040c8bfc7e3cb7d9540874
> I don't think reverting that commit is right. If you disable fullscreen
> effect and maximize effect, is the issue still reproducible?

I reproduce it with both option disabled.
Comment 15 Bug Janitor Service 2021-09-14 17:20:43 UTC
A possibly relevant merge request was started @ https://invent.kde.org/graphics/gwenview/-/merge_requests/110
Comment 16 Yaroslav Sidlovsky 2021-09-14 17:31:02 UTC
Sorry. Wrong bug :(
Comment 17 Andy Great 2021-09-18 10:05:44 UTC
*** Bug 442059 has been marked as a duplicate of this bug. ***
Comment 18 Frank Zechert 2021-09-24 20:23:40 UTC
I can also confirm this on a fresh install of Arch Linux with KDE Plasma desktop. I am using a NVIDIA GeForce GTX 970 with the proprietary nvidia driver on X11.

Disabling desktop effects (window maximize, fullscreen) or changing any compositor options did not work (this is one of the 'fixes' recommended in some forums). What worked though, was disabling the compositor with alt+shift+f12, but this is not really a nice fix :)

As recommended in this ticket, I downgraded kwin from 5.22.5 to 5.22.4, and it solved the problem.

Operating System: Arch Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.7-arch1-1 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Xeon® CPU E3-1231 v3 @ 3.40GHz
Memory: 15,6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 970/PCIe/SSE2
Comment 19 Oscar Arranz 2021-10-01 12:48:06 UTC
This is happening to me too on Kernels 5.10 / 5.13 / 5.14 (but this are the only ones I tried so I'm guessing it will happen on any kernel) with KWIN 5.22.5.

It's happening with both OpenGL 2.0 and 3.1.

I have NVIDIA proprietary drivers and own a GTX 1660.

I will try downgrading KWIN to 5.22.4 and see how it goes.
Comment 20 Oscar Arranz 2021-10-01 13:23:49 UTC
(In reply to Oscar Arranz from comment #19)
> This is happening to me too on Kernels 5.10 / 5.13 / 5.14 (but this are the
> only ones I tried so I'm guessing it will happen on any kernel) with KWIN
> 5.22.5.
> 
> It's happening with both OpenGL 2.0 and 3.1.
> 
> I have NVIDIA proprietary drivers and own a GTX 1660.
> 
> I will try downgrading KWIN to 5.22.4 and see how it goes.

Fixed it by downgrading to KWIN 5.22.4 following these steps:

1) Download downgrade from the AUR: `yay -Sa downgrade`
2) Show kwin version list: `sudo downgrade kwin`
3) Now you'll have a list with kwin versions and a number corresponding to each version, you must type the number of version 5.22.4 and hit enter
4) When asked if you want to install say `Y`
5) Reboot your system: `Reboot`

System information (I forgot to post it on the first comment):

Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5 (This is now 5.22.4 but it keeps saying 5.22.5, though it clearly is not as the bug doesn't persist)
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.14.7-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660/PCIe/SSE2
Comment 21 aCOSwt 2021-10-03 10:26:52 UTC
(In reply to Mikael Hirki from comment #12)
> I tried reverting each commit between 5.22.4 and
> 5.22.5.  Reverting this commit fixes the issue for me:
> 
> https://invent.kde.org/plasma/kwin/-/commit/
> f432ba7821cea2302d040c8bfc7e3cb7d9540874

Acted identically and came to the same conclusion.

I however acknowledge that I do not understand why the above (simple) commit would trigger such a glitch and, if we agree with Vlad's comment #13 ("reverting this commit is not the right thing to do") it would mean that the "real" problem lies elsewhere.

However, reverting it actually works. Which has IMHO a lesser cost than downgrading to 5.22.4
Comment 22 Bob 2021-10-14 00:38:13 UTC
I'm seeing this same bug on my Linux system with NVIDIA graphics. Selecting either of the OpenGL compositor backends causes a fullscreen youtube video to become a black screen. It only happens when switching from an already maximized browser window into fullscreen mode.

I also tested reverting the code from this commit as other users here have mentioned: https://invent.kde.org/plasma/kwin/-/commit/f432ba7821cea2302d040c8bfc7e3cb7d9540874

After rebuilding kwin-5.22.5, the problem is gone. I am not familiar with kwin's coding so its difficult to offer a suggestion for fixing this other than reverting that change.

Operating System: Slackware Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.3
Kernel Version:  5.14.11
Graphics Platform: X11
Processors: 8 x Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
Memory: 16GB
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER
Comment 23 Bob 2021-10-15 00:40:49 UTC
(In reply to Bob from comment #22)
> I'm seeing this same bug on my Linux system with NVIDIA graphics. Selecting
> either of the OpenGL compositor backends causes a fullscreen youtube video
> to become a black screen. It only happens when switching from an already
> maximized browser window into fullscreen mode.
> 
> I also tested reverting the code from this commit as other users here have
> mentioned:
> https://invent.kde.org/plasma/kwin/-/commit/
> f432ba7821cea2302d040c8bfc7e3cb7d9540874
> 
> After rebuilding kwin-5.22.5, the problem is gone. I am not familiar with
> kwin's coding so its difficult to offer a suggestion for fixing this other
> than reverting that change.
> 
> Operating System: Slackware Linux
> KDE Plasma Version: 5.22.5
> KDE Frameworks Version: 5.87.0
> Qt Version: 5.15.3
> Kernel Version:  5.14.11
> Graphics Platform: X11
> Processors: 8 x Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz
> Memory: 16GB
> Graphics Processor: NVIDIA GeForce GTX 1660 SUPER

I just tried out the newly released plasma version 5.23.0 and do not have this bug anymore (using OpenGL 2.0). Going to be sticking to that version now.

Thanks.
Comment 24 aCOSwt 2021-10-15 09:43:42 UTC
(In reply to Bob from comment #23)
> I just tried out the newly released plasma version 5.23.0 and do not have
> this bug anymore (using OpenGL 2.0). Going to be sticking to that version
> now.

So would https://invent.kde.org/plasma/kwin/-/commit/52c9dbb487f4ac98017b83a1deee912546cbff5f appear to be the "right" fix ?
Comment 25 Colin J Thomson 2021-10-15 16:58:49 UTC
Does indeed seem to be fixed in 5.23.0 with the commit mentioned in #442936

Thanks!
Comment 26 Nate Graham 2021-10-15 17:04:56 UTC
Nice.