https://bugs.kde.org/show_bug.cgi?id=483163
--- Comment #25 from Nicole Schoebel <schoebel220...@nschoebel.de> --- Earlier today I went into "System Settings / Display & Monitor" and DISabled "Compositing / Enable on startup". I then rebooted. After I logged back into KDE, I could then activate the lock screen and it would show properly. I tested this multiple times, and it worked fine every time. I then re-enabled the compositor, and then the lock screen would show up black again except for the mouse cursor. So the bug only seems to appear when the compositor is enabled, which makes me wonder if the compositor is getting confused about which window should be displayed on top? If I understand the design of the lock screen correctly (as described in the sources in kscreenlocker/DESIGN), then a fullscreen (empty - all black) window is put on top of all other windows, and then the actual lock screen is put on top of that. If the compositor for some reason would think that that fullscreen window belongs on top of the lock screen... we would see exactly this bug. So, could this actually be a compositor bug? -- You are receiving this mail because: You are watching all bug changes.
