https://bugs.kde.org/show_bug.cgi?id=495765
--- Comment #26 from jkotran <[email protected]> --- Maybe this can help the developers craft a fix. Google Gemini provided this information. It seems rational to me: The redundant kscreenlocker_greet process is likely spawned because of a race condition between the GPU driver initializing the display and kwin_wayland trying to paint the lock screen upon wake. On Wayland, the screen locker is tightly integrated with the compositor (KWin). If the GPU context isn't fully restored when the locker tries to grab input, the locker binary (kscreenlocker_greet) can hang or spawn a second instance to try to recover, leading to two processes fighting for focus. (In reply to jkotran from comment #25) > > Can someone let me know what precisely starts the kscreenlocker_greet > process? For me the problem is there's a redundant kscreenlocker_greet > process after PC sleep. If I kill the redundant process, I can successfully > login. > -- You are receiving this mail because: You are watching all bug changes.
