| 1 |
On Monday, 11 September 2017 19:27:02 BST Jigme Datse Yli-RAsku wrote: |
| 2 |
> I had a similar (if not identical problem). This solution is a |
| 3 |
> "difficult" solution, the reason I experienced this (if I understand) |
| 4 |
> was that I was running KDE at the same time I was updating KDE. |
| 5 |
|
| 6 |
No the user started a Plasma session after booting up the PC and while no |
| 7 |
updates were being performed. |
| 8 |
|
| 9 |
|
| 10 |
> I can't |
| 11 |
> remember if I simply rebooted, or if all it took was logging out, and |
| 12 |
> logging back in. Even if I had rebooted, the *most* that should be |
| 13 |
> required is restarting X, which if you are running XDM may require |
| 14 |
> restarting XDM, or as stated, simply logging out and logging back in |
| 15 |
> (but that might not be possible from KDE running in this broken mode). |
| 16 |
> It should happen relatively infrequently. |
| 17 |
|
| 18 |
I can login and restart xdm, but I fear the user may lose some the work being |
| 19 |
performed at the time. I may end up doing this, but not if there is a way to |
| 20 |
recover the session. Strangely, I can't see any relevant screenlock process I |
| 21 |
could stop from the console. :-( |
| 22 |
-- |
| 23 |
Regards, |
| 24 |
Mick |
Archives