408493 2019-06-09 17:23:08 +0000 Desktop briefly visible before lock screen appears 2021-06-21 21:20:28 +0000 1 1 10 Unmaintained kscreenlocker general unspecified Other Linux RESOLVED DUPLICATE 316734 NOR normal --- 0 jgc.novo plasma-bugs-null bshah bugseforuns kde kingspammernerd koshka nate null psychonaut 0 oldest_to_newest 1861700 0 jgc.novo 2019-06-09 17:23:08 +0000 SUMMARY I have the energy saving settings to suspend the session, after the suspend when i come to the computer i see first the desktop and then it loads the lock screen. STEPS TO REPRODUCE 1. Let the system suspend with power management. 2. Try to log in. OBSERVED RESULT The desktop comes first and then it loads the lock screen. EXPECTED RESULT The lock screen should be loaded already, or the desktop should not be visible while loading the lock screen. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.15 KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-51-generic OS Type: 64-bit 1867802 1 mgraesslin 2019-07-08 19:59:20 +0000 Most likely a graphics driver failure. The infrastructure ensures to lock prior to suspend. 1965022 2 bugseforuns 2020-10-14 21:03:41 +0000 *** Bug 415362 has been marked as a duplicate of this bug. *** 1965024 3 bugseforuns 2020-10-14 21:03:47 +0000 *** Bug 414414 has been marked as a duplicate of this bug. *** 1965391 4 psychonaut 2020-10-16 10:10:27 +0000 (In reply to Martin Flöser from comment #1) > Most likely a graphics driver failure. The infrastructure ensures to lock > prior to suspend. I agree -- I recently changed from the ancient X.Org xf86-video-intel driver to the standard modesetting driver, per Bug 395583 Comment 20, and now I am no longer experiencing this issue. Anyone who is still experiencing this issue, please check if you are using the xf86-video-intel driver, and if so, try switching to the modesetting driver instead. (Or conversely, if you are using the modesetting driver on a very old Intel graphics controller, try changing to xf86-video-intel.) 1965407 5 nate 2020-10-16 11:21:12 +0000 Can anyone else confirm the same behavior? 1967427 6 psychonaut 2020-10-23 12:29:09 +0000 (In reply to Tristan Miller from comment #4) > I recently changed from the ancient X.Org xf86-video-intel driver > to the standard modesetting driver, per Bug 395583 Comment 20, and now I am > no longer experiencing this issue. Scratch that; I'm now continuing to see the behaviour again, even with the modesetting driver. Maybe it happens less often, but it still does happen occasionally. 1972436 7 bug-janitor 2020-11-07 04:33:41 +0000 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! 1972792 8 psychonaut 2020-11-08 09:52:20 +0000 Clearing the needinfo flag as I assume this was due to my mistaken comment. 2007807 9 kde 2021-03-02 07:21:49 +0000 (In reply to Nate Graham from comment #5) > Can anyone else confirm the same behavior? It happens on amdgpu with kernel parameter "amdgpu.dc=0" set. The default "amdgpu.dc=1" doesn't have the issue (but other problems). Operating System: openSUSE Tumbleweed 20210223 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.10.16-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: Radeon RX 570 Series 2042815 10 nate 2021-06-21 21:20:28 +0000 *** This bug has been marked as a duplicate of bug 316734 ***