| 1 |
I had a similar (if not identical problem). This solution is a |
| 2 |
"difficult" solution, the reason I experienced this (if I understand) |
| 3 |
was that I was running KDE at the same time I was updating KDE. I can't |
| 4 |
remember if I simply rebooted, or if all it took was logging out, and |
| 5 |
logging back in. Even if I had rebooted, the *most* that should be |
| 6 |
required is restarting X, which if you are running XDM may require |
| 7 |
restarting XDM, or as stated, simply logging out and logging back in |
| 8 |
(but that might not be possible from KDE running in this broken mode). |
| 9 |
It should happen relatively infrequently. |
| 10 |
|
| 11 |
If you are doing unattended updates, you are likely to run into this |
| 12 |
kind of problem from time to time. I do not recommend it except for |
| 13 |
"security" updates, which I don't believe there is an automated process |
| 14 |
in Gentoo to do. Ie. I don't believe Portage flags updates as |
| 15 |
"security" updates in any way, so a single command of "emerge --update |
| 16 |
--security-only @word" (to my knowledge) isn't really a possibility. |
| 17 |
|
| 18 |
Though, also, I haven't been following recent discussions that closely, |
| 19 |
and I only recently returned to Gentoo after about 10 years away. |
| 20 |
|
| 21 |
On 09/11/2017 10:49 AM, Mick wrote: |
| 22 |
> I started a plasma session and after some period of input inactivity I noticed |
| 23 |
> the screen blanked out. Later on I moved the mouse and to my surprise I |
| 24 |
> obtained this message: |
| 25 |
> ********************* |
| 26 |
> "The screen locker is broken and unlocking is not possible anymore. |
| 27 |
> In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2), |
| 28 |
> log in and execute the command: |
| 29 |
> |
| 30 |
> loginctl unlock-sessions |
| 31 |
> |
| 32 |
> Afterwards switch back to the running session (Ctrl+Alt+F7)." |
| 33 |
> ********************* |
| 34 |
> |
| 35 |
> Given this is a non-systemd Gentoo installation and I intend to keep it this |
| 36 |
> way as long as reasonably practicable, what should I instruct the user to do |
| 37 |
> to recover their current plasma session? |
| 38 |
> |
| 39 |
> If this is a default Gentoo installation with openrc, why does a default |
| 40 |
> plasma desktop screenlocker comes up with this nonsense? |
| 41 |
> |
Archives