SDDM + TTY autologin

82 views
Skip to first unread message

Mihai Dobrescu

unread,
Aug 26, 2021, 1:53:36 AM8/26/21
to sddm-devel

Hello,

I test a new distro, which is in alpha, MocaccinoOS, KDE+SDDM based among others, that can be downloaded here: https://get.mocaccino.org/minio/mocaccino-iso/.

Those are live images that have initially a root account, then, during startup, a default user,  "mocaccino" (UID 1000), is created in the group "root" and the tty's (getty) are configured (at that step too) to autologin as root user (UID 0), then those commands are run:

        systemctl daemon-reload
        systemctl restart getty@tty1

For GDM and LightDM this works.
SDDM is also set at the same step, to autologin as "mocaccino" user  and Plasma session and no relogin (Relogin=false).

Now, trouble starts:
1. Black screen, seemingly because the default SDDM service config has the following set:

Conflicts=ge...@tty1.service

Could this be related to systemctl restart getty@tty1 command above?
If the conflicts entry is set to nothing, "Conflicts=", the outcome is:

2. SDDM allows Plasma session, but it's misconfigured. It would be a "mocaccino" user session, apparently under root tty1, so no user service tree is created, meaning the following are not loaded:

  • un-user-1000.mount (to be mounted /run/user/1000)
  • session-5.scope (for running Session 5 of User mocaccino)
  • systemd-hostnamed.service (for running Hostname Service)
  • user-run...@1000.service(for User Runtime Directory /run/user/1000)
  • us...@1000.service (for running User Manager for UID 1000)
  • user-1000.slice (for User Slice of UID 1000)

That's because SDDM runs under root (UID 0).

A logout would bring the greeter where "mocaccino" user can login again, that seems to run SDDM under "sddm" user and the following are created this time:

  • un-user-1000.mount loaded active mounted /run/user/1000
  • session-5.scope loaded active running Session 5 of User mocaccino
  • systemd-hostnamed.service loaded active running Hostname Service
  • user-run...@1000.service loaded active exited User Runtime Directory /run/user/1000
  • us...@1000.service loaded active running User Manager for UID 1000
  • user-1000.slice loaded active active User Slice of UID 1000

This has been done in old SDDM setups successfully.

Is there a way to fix this? Can be SDDM configured and started at that point to have a correct user setup as "mocaccino"?

Thank you,
Mike
Reply all
Reply to author
Forward
0 new messages