| Summary: | On X11 with AMD or NVIDIA GPU, lock screen wallpaper is sometimes all black after waking from sleep | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Erich Eickmeyer <eeickmeyer> |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | al.neodim, bhush94, bugs.kde, butirsky, eduardo.cruz, francogpellegrini, higors88, jchevarley, jinujohnjoseph, kalzwayed, kde-bugzilla, kde, mugokwe42x, nate, notmart, qydwhotmail, sephiroth_pk, tatsoft, xaver.hugl |
| Priority: | NOR | Keywords: | regression |
| Version: | 5.25.3 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=456122 https://bugs.kde.org/show_bug.cgi?id=463379 |
||
| Latest Commit: | Version Fixed In: | 5.26.5 | |
| Sentry Crash Report: | |||
| Attachments: |
Bugged lock screen
Normal lock screen Plasma under Wayland after returning from sleep |
||
|
Description
Erich Eickmeyer
2022-07-29 21:40:15 UTC
Do you see the interactive UI elements for the lock screen, or is the entire screen black? Can you move the cursor? (In reply to Nate Graham from comment #1) > Do you see the interactive UI elements for the lock screen, or is the entire > screen black? The UI elements are there and it is interactive. > Can you move the cursor? Cursor is active. The only issue is the background is black. Thanks. Moving to KWin since it seems like this is probably a graphics issue. Possibly even an issue with the NVIDIA drivers. Does it reproduce with both Wayland and X11? Does this happen on the desktop too, or just the lock screen? (In reply to Nate Graham from comment #3) > Thanks. Moving to KWin since it seems like this is probably a graphics > issue. Possibly even an issue with the NVIDIA drivers. > > Does it reproduce with both Wayland and X11? We are unable to even launch Wayland under 5.25.x as it immediately crashes on our Nvidia hardware. That might be a separate bug. > Does this happen on the desktop too, or just the lock screen? It's just the lock screen. Thanks. I've got the same issue, background is always black, and sometimes it aggravates a little more as the current date and time information sometimes shows up incomplete, only a few of the numbers are displayed. Only happens when directly returning from sleep. If I unlock it, then just lock the screen again without sleep, the lock screen shows up fine. It wasn't always like this. It started happening a couple months back, I don't know exactly when... Hard to tell where the bug is located down the stack, could be kernel, nvidia drivers, or kde software. I would guess it's some sort of race condition, maybe something is being requested of the graphics card while it is still not ready back from sleep. It happens on my 2 computers, both with kernel 5.18.16-zen, nvidia-dkms 515.65.01-1, kwin/plasma 5.25.4 under XOrg. I have this issue on two different computers, a desktop and a notebook, both with all-AMD hardware, so this is not exclusive to NVIDIA. On the desktop, the issue is also present with the desktop itself, not just with the lock screen. Can't reproduce. Can you still reproduce it after removing ~/.cache/kscreenlocker_greet/ ? If you can test 5.26 Beta it would be better. *** Bug 459075 has been marked as a duplicate of this bug. *** (In reply to Fushan Wen from comment #8) > Can't reproduce. Can you still reproduce it after removing > ~/.cache/kscreenlocker_greet/ ? If you can test 5.26 Beta it would be better. No effect. Cannot test on 5.26 Beta, I do not have access to binary builds at this time. Latest test on 5.25.5 resulted in same issue. Bear in mind, this is on an Nvidia discrete GPU in Performance mode, issue does not occur if in Powersave (integrated graphics) mode. Jino, are you also using an NVIDIA GPU when you reproduce the issue? (In reply to Nate Graham from comment #11) > Jino, are you also using an NVIDIA GPU when you reproduce the issue? Yes, I am also using and Nvidia GPU. Thanks. This is pointing to a graphics issue in KWin or the NVIDIA driver; moving back to KWin. Can anyone reproduce on Wayland? Created attachment 152122 [details]
Bugged lock screen
This is the lock screen I get when returning from sleep.
Date and time label only shows a "5, that's very random, sometimes more pieces of the date and time are shown, sometimes it shows complete, sometimes it is missing at all.
Background is black.
Profile picture is grey.
Created attachment 152123 [details]
Normal lock screen
This is what my lock screen should be. I get this when just locking without going to sleep.
Created attachment 152124 [details]
Plasma under Wayland after returning from sleep
Under Wayland it is even worse. The bug lives on into plasma desktop even after I unlock the lock screen after returning from sleep. As can be seen in the picture, the desktop renders completely crazy. No icons, no labels, black background, date and time on taskbar shows only "1"...
This is starting to feel like a bug in the NVIDIA driver itself. There's a long history of graphical glitches on suspend, unfortunately. (In reply to Nate Graham from comment #17) > This is starting to feel like a bug in the NVIDIA driver itself. There's a > long history of graphical glitches on suspend, unfortunately. It's possible... however In comment #7 he said he got the bug with AMD hardware. (In reply to Nate Graham from comment #17) > This is starting to feel like a bug in the NVIDIA driver itself. There's a > long history of graphical glitches on suspend, unfortunately. I can reproduce on AMD hardware, specifically my laptop with a Ryzen 2500U CPU and Vega 8 GPU. I am therefore removing the mention of NVIDIA from the title. One thing I noticed is that it often occurs after I connect or disconnect my laptop to/from the docking station. If I just leave it plugged in, the bug does not appear. *** Bug 456723 has been marked as a duplicate of this bug. *** We've made a change that we're pretty sure will fix this in Plasma 5.26! Please re-open if you find that you can still reproduce the issue in 5.26 after upgrade (and a reboot, of course!). *** Bug 437808 has been marked as a duplicate of this bug. *** (In reply to Nate Graham from comment #21) > We've made a change that we're pretty sure will fix this in Plasma 5.26! > Please re-open if you find that you can still reproduce the issue in 5.26 > after upgrade (and a reboot, of course!). Sadly, I can't 100% confirm this. I just upgraded to Plasma 5.26 beta from the Kubuntu beta PPA which might not have the latest commits and, sadly, the issue still exists there. That said, I won't reopen as I don't believe this fits the test case. The commits to fix it were just made yesterday and didn't make it into the beta. You'd have to be running the latest git version of the master branch or the plasma/5.26 branch. Hi, I just get it fixed by removing the NVIDIA driver completely and reinstall it again. sudo apt-get purge '*nvidia*' -y reboot sudo apt-get install nvidia-driver-515 reboot sudo apt-get install nvidia-modprobe reboot (In reply to Ali from comment #25) > Hi, > I just get it fixed by removing the NVIDIA driver completely and reinstall > it again. > > sudo apt-get purge '*nvidia*' -y > reboot > sudo apt-get install nvidia-driver-515 > reboot > sudo apt-get install nvidia-modprobe > reboot issue reproduced , black background I downgraded the nvidia-driver to 510 and apply this line
> sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit
open nvidia-settings and save the x server display configuration by pressing "save to x configuration file"
(In reply to Ali from comment #27) > I downgraded the nvidia-driver to 510 and apply this line > > sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit > open nvidia-settings and save the x server display configuration by pressing > "save to x configuration file" That's merely a workaround and can actually break some laptop displays. Please do not give such advice as a "bugfix". (In reply to Ali from comment #27) > I downgraded the nvidia-driver to 510 and apply this line > > sudo chmod +x /usr/share/screen-resolution-extra/nvidia-polkit > open nvidia-settings and save the x server display configuration by pressing > "save to x configuration file" Considering that, as people (me included) have pointed out multiple times, this issue is not related just to NVIDIA, I wouldn't be so quick in marking the issue as closed as you solving it by downgrading the NVIDIA driver doesn't fix the issue for people with AMD or Intel drivers. Let's leave this issue open until we are sure that it is fixed for everyone, thank you. Furthermore, as Erich points out, your workaround can cause further issues, so I would tread very carefully around this. More on topic, I was actually able to reproduce the issue without suspending my laptop, but simply plugging in an external display. The laptop's screen (oddly enough, not the external display) started exhibiting the behaviour, which also involved Plasma's desktop. The desktop was black unless it was focused (i.e. I clicked on it); after a few minutes the issue went away on its own on both the desktop and the lockscreen. There is al a related issue on that: bug 455738 Finally on Plasma 5.26.1. So far, I have not seen this bug appear, so I'm very close to marking this as fixed, but I want to do a little more testing before closing. Confirmed bug is gone as of 5.26.1. Thanks! *** Bug 455738 has been marked as a duplicate of this bug. *** This is fixed on my NVidia system (X11), but oddly enough, I am still seeing this on my AMD build (Wayland): Operating System: Arch Linux KDE Plasma Version: 5.26.2 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.7 Kernel Version: 6.0.2-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 5500 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B85 System Version: 1.0 I am still getting a black wallpaper on the screen locker on occasions when resuming from sleep/hibernate. I don't see anything particularly useful in journalctl, either. I just experienced this on my AMD system. It is the first time it happens in a while, though. KDE Plasma version: 5.26.4 KDE Frameworks version: 5.101.0 Qt version: 5.15.7 So updated to 5.26.5, and noticed there was a commit for blank lock screen wall papers. After updating, I have yet to see this bug again. So perhaps it's fixed now? Oh fabulous, maybe https://invent.kde.org/plasma/kscreenlocker/-/commit/50fc20dc940c87ffd62be0650b935324e164b59d was the fix. Can other people upgrade to Plasma 5.26.5 and see if the issue is solved for them too? *** Bug 463379 has been marked as a duplicate of this bug. *** (In reply to Nate Graham from comment #37) > Oh fabulous, maybe > https://invent.kde.org/plasma/kscreenlocker/-/commit/ > 50fc20dc940c87ffd62be0650b935324e164b59d was the fix. > > Can other people upgrade to Plasma 5.26.5 and see if the issue is solved for > them too? I'm using AMD, and the problem continues. Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-58-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.7 GiB of RAM Graphics Processor: RENOIR Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H V2 *** Bug 464445 has been marked as a duplicate of this bug. *** Well darn. Erich, any chance backporting https://invent.kde.org/plasma/kscreenlocker/-/commit/50fc20dc940c87ffd62be0650b935324e164b59d has fixed it for you? Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! Re-opening as it's clearly not fixed since we're still getting bug reports about it, unfortunately. *** Bug 475605 has been marked as a duplicate of this bug. *** (In reply to Nate Graham from comment #44) > Re-opening as it's clearly not fixed since we're still getting bug reports > about it, unfortunately. There is some confusion in this bug, 475605, and other duped bugs about the nature and symptoms of this bug. I am trying to gather more data on the specific flavor that I am running into daily on my system. Some basic questions that need to be summarized: - Does it happen when the system locks the screen? - Does it happen when the system puts the display to sleep? - Does it happen when the system suspends? - Are there more than one screen? - Are there more than one GPU? - Is it a PRIME system with muxing? If so, which GPU was driving the display? - Is the cursor visible? - Are there any GUI elements visible? - Is the broken lock screen function (e.g. blindly typing your password and hitting Enter unlocks)? - Is there a method that brings you back to a working desktop (e.g. killing kscreenlocker_greet). - Is the desktop session using X11 or Wayland? Each specific combination of these may be a different root issue. And of course there are other basic system information to answer, like kernel version, kernel cmdline, display modes, GPU driver version, etc. I'm also unclear how to gather more information. The journal log is really unhelpful when it happens. Are there config flags, environment variables, etc. that someone can set to get more information. Indeed, I just realized that myself and am un-duping some bug reports. As for this specific one about just the wallpaper being black after resume, we think it's fixed and have no newer reports, so I'll close it again. |