4 ms·

> If the screensaver crashes, it gets restarted, or, if that fails, you get in a lovely TTY font "open a tty, login as your user, and type loginctl session-unlo

> If the screensaver crashes, it gets restarted, or, if that fails, you get in a lovely TTY font "open a tty, login as your user, and type loginctl session-unlock". This is really offtopic, but you seem to confuse KDE with systemd. There is a bit of KDE that tells you to use loginctl to tell KDE's display manager to unlock the session if KDE's screensaver doesn't work properly.

kuschku 9y ago
Sure, KDE implements that bit, but the important part is that logind makes it possible to implement that bit in the first place. Before logind, the alternative was custom handling and detection of screensavers in your session, or simply it crashing back to the session.
- slgeorge 9y ago
  I find both your comments confusing. In your first comment you said that screensavers were just normal windows and would crash back to an unlocked screen - that never happened. Here you're conflating KDE (started ~1997) needing logind (started in what 2010?) which it didn't. Even your comment about a 'session' makes no sense since at the X runlevel X itself is the 'session'. In my opinion a lot of the problem has been a lack of clarity of what the actual user benefit will be, and the crazy borg-like scope expanion. I'm going to avoid commenting on the implementation of logind and brethren.
  - kuschku 9y ago
    I'm not conflating anything — lockscreens on X11 were always just normal windows. If they crash, they unlock. I suggest you read JWZ's On Toolkits page: (archive link due to referer shenanigans): http://archive.is/BjMfp http://archive.is/BjMfp
    - makomk 9y ago
      Yes you are. The trick that KDE uses is that the screen locking is done by the KDE session manager, and because that is the main process in the X session if it crashes the session terminates so it's not possible to bypass the screen locker that way. None of that requires systemd; it makes use of something that's been true under X11 pretty much forever. The only thing that changed with logind is that instead of trying to restart the password prompt if it crashes, KDE now pops up a message asking you to drop to a console and use logind to disable the screen locker. (Annoyingly, it does this even on systems that don't use logind, in which case the instructions don't actually work.)
      - kuschku 9y ago
        I was aware that KDE handled it that way, but as far as I know to handle it properly like this across X11, Wayland, and other sessions, logind is pretty much required. Gräßlin wrote a bit about that in his blog. But you might be right, I’ve not worked on either of these projects, so my knowledge is mostly from hearsay.

kuschku 9y ago

Sure, KDE implements that bit, but the important part is that logind makes it possible to implement that bit in the first place. Before logind, the alternative was custom handling and detection of screensavers in your session, or simply it crashing back to the session.

slgeorge 9y ago
I find both your comments confusing. In your first comment you said that screensavers were just normal windows and would crash back to an unlocked screen - that never happened. Here you're conflating KDE (started ~1997) needing logind (started in what 2010?) which it didn't. Even your comment about a 'session' makes no sense since at the X runlevel X itself is the 'session'. In my opinion a lot of the problem has been a lack of clarity of what the actual user benefit will be, and the crazy borg-like scope expanion. I'm going to avoid commenting on the implementation of logind and brethren.
- kuschku 9y ago
  I'm not conflating anything — lockscreens on X11 were always just normal windows. If they crash, they unlock. I suggest you read JWZ's On Toolkits page: (archive link due to referer shenanigans): http://archive.is/BjMfp http://archive.is/BjMfp
  - makomk 9y ago
    Yes you are. The trick that KDE uses is that the screen locking is done by the KDE session manager, and because that is the main process in the X session if it crashes the session terminates so it's not possible to bypass the screen locker that way. None of that requires systemd; it makes use of something that's been true under X11 pretty much forever. The only thing that changed with logind is that instead of trying to restart the password prompt if it crashes, KDE now pops up a message asking you to drop to a console and use logind to disable the screen locker. (Annoyingly, it does this even on systems that don't use logind, in which case the instructions don't actually work.)
    - kuschku 9y ago
      I was aware that KDE handled it that way, but as far as I know to handle it properly like this across X11, Wayland, and other sessions, logind is pretty much required. Gräßlin wrote a bit about that in his blog. But you might be right, I’ve not worked on either of these projects, so my knowledge is mostly from hearsay.