https://bugs.kde.org/show_bug.cgi?id=357007

--- Comment #26 from Götz <goetzchr...@gmail.com> ---
> Comment #2 said "Just tried using KWin with compton as compositor and the 
> same problem."

I don't remember that :)
There are to many variables I forgot that one.

> Yes, but while hidden when you select XRender, it's never supposed to be 
> disabled (there's simply no code that does such) - and in your case should 
> list GLX & EGL

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.

But now, after using kwin_x11 with compton, then selecting EGL and applying,
kwin seems to be frozen. Killing it makes the GUI intractable again. I can
reproduce this and open a new bug report if you like.

> What exactly did you kill?

I will try to be more descriptive:
A timeout has passed and the screen locked. The locker was frozen or it was
kwin, but the screen did not react to keyboard input or mouse clicks, only the
cursor could be moved around. Then I entered the password and Enter; nothing
changes on screen. Then I switched to TTY 2 to kill kwin_x11, back to TTY 1 and
I see those Firefox tabs (first screenshot). So I kill kscreenlocker_greet,
which changes the screen content to my desktop, showing a window and the
kscreenlocker background in the vertical-left Plasma panel area (second
screenshot). Then I started kwin_x11, parts of the screen flickered. Killing
and restarting kwin makes everything work again. 

> So either the screenlocker are artifacts in the framebuffer or the konsole 
> window managed to raise above the screenlocker.

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.

But there is something else, today after starting the computer from suspend,
the first thing I was was my desktop wallpaper, the it changed rapidly to the
locker screen with its own wallpaper image.
I can observe such behavior very often.

> try to invoke the greeter directly instead of locking the screen:

It does work, but I will continue doing this and Ctrl+Alt+L and letting the
screen lock automatically to see what happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to