https://bugs.kde.org/show_bug.cgi?id=357007
--- Comment #31 from Thomas Lübking <thomas.luebk...@gmail.com> --- (In reply to Götz from comment #26) > This is also strange. The combobox was empty while OpenGL 2.0 or 3 where > selected. Now I see the options (now sure what changed) and I have selected > EGL. It queries KWin for some basic information (notably the compiled in backends) - feature, not bug. > But now, after using kwin_x11 with compton, then selecting EGL and applying That should have zero or bad impact - you cannot use two compositors at once and I've no idea how compton reacts if you try to claim the compositor selection (resp. whether it claims it) Just don't do that. > I will try to be more descriptive: > A timeout has passed and the screen locked. The locker was frozen or it was Can you try to kill just kscreenlocker_greet instead? (see jmux's input) FYI, the cursor is drawn directly into the scanout buffer by the HW, it's different from everything else by nature. > I think it where the artifacts, and that the locker was working but kwin did > not work correctly. So the screen unlocked after entering the password, but > kwin didn't update the screen content. In such case, suspending the compositor (SHIFT+Alt+F12) *after* the assumed unlock should present you the uncomposited, but correct desktop. > But there is something else, today after starting the computer from suspend, Is this btw. part of the broken process? At least the nvidia blob is known to cause trouble when transferring VBOs between GPU and system RAM (between ugly artifacts and segfaults) - and this would likely affect both, kwin *and* the screenlocker (the brief wallpaper might point towards this - you should still only see a black window when the greeter crash-restarts, but the driver might expose an older frame instead) -- You are receiving this mail because: You are watching all bug changes.
