Hi All

Synopsis: When I select the Lock Widget icon on the Panel: my session gets canned, including all running applications.
System: KDE 4.9.0 (Kubuntu)

I am usually running two sessions at the same time, a work one and a private one.
When I switch sessions I use the Lock option on the Lock/Logout widget on the Panel.
However, every so often it cans the current (?) session without any warning and sends me back to the Login for KDM.
No warning with the currently open applications, etc. All the processes for the current session appear to be killed.

I have not seen this happen with the Switch User function as I have not been using it.
I have not noticed it happen with the Lock menu function but I have not tried that one often enough to notice.

Any assistance would be appreciated as its a real pain when it cans my current work session in particular!

Cheers, Thanks

Andy

The screenlocker (probably some facy opengl?) likely crashes the X11 server (sending you back to the login screen because X11 is auto-restarted by kdm)
That's usually a bug in the graphics driver (and for sure a bug in X11, not in KDE or any client process - the server must not crash even on client errors)

Try setting the screensaver to blank screen, also check "kcmshell4 kwincompositing", 3rd tab. Ensure "suspend compositing for fullscreen windows" is NOT checked.
Alternatively suspend compositing (shift+alt+f12) before locking the screen (the usual graphics driver bug emerges on two or more parallel OpenGL contexts)

Backtraces for the server crash can usually be found in /var/log/Xorg.*.log

Hi luebking

The screenlocker (probably some facy opengl?) likely crashes the X11 server (sending you back to the login screen because X11 is auto-restarted by kdm)
That's usually a bug in the graphics driver (and for sure a bug in X11, not in KDE or any client process - the server must not crash even on client errors)

Thanks for the enlightenment here. Looks like KDE got the evil eye for something in the X/opengl setup.

Try setting the screensaver to blank screen, also check "kcmshell4 kwincompositing", 3rd tab. Ensure "suspend compositing for fullscreen windows" is NOT checked.
Alternatively suspend compositing (shift+alt+f12) before locking the screen (the usual graphics driver bug emerges on two or more parallel OpenGL contexts)

I've checked but no joy there. Both settings are as mentioned above.

Backtraces for the server crash can usually be found in /var/log/Xorg.*.log

I'll keep an eye on the logs next time it berks itself. That may give me some clue on what's causing this fuss.

Cheers & thanks again.

Andy

If that's no GL screensaver, odds that this is caused by an GL context conflict dropped.
Ensure to check the Xorg log to see what crashed the server.