You are not logged in.
I have a relatively fresh install (about a month), and after some time, I noticed reboot and poweroff are missing from sddm login screen.
I use default theme. And when i change theme to something else that has those buttons on different locations buttons are there, but they simply don't work.
journalctl output:
Feb 12 18:28:01 excalibur sddm-helper[362]: [PAM] Starting...
Feb 12 18:28:01 excalibur sddm-helper[362]: [PAM] Authenticating...
Feb 12 18:28:01 excalibur sddm-helper[362]: [PAM] returning.
Feb 12 18:28:01 excalibur sddm-helper[362]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0)
Feb 12 18:28:01 excalibur sddm[347]: Greeter session started successfully
Feb 12 18:28:01 excalibur sddm[347]: Message received from greeter: Connect
Feb 12 18:28:03 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:04 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:04 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:04 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:04 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:04 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:05 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:05 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:05 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:05 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:06 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:06 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:06 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:06 excalibur sddm[347]: Message received from greeter: PowerOff
Feb 12 18:28:06 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:07 excalibur sddm[347]: Message received from greeter: Reboot
Feb 12 18:28:12 excalibur sddm[347]: Message received from greeter: Login
Feb 12 18:28:12 excalibur sddm[347]: Reading from "/usr/share/xsessions/i3.desktop"
Feb 12 18:28:12 excalibur sddm[347]: Reading from "/usr/share/xsessions/i3.desktop"
Feb 12 18:28:12 excalibur sddm[347]: Session "/usr/share/xsessions/i3.desktop" selected, command: "i3"Edit:
If i restart sddm service, buttons start to work. I found this issue, but I can't see how is that connected with arch.
Edit 2:
Did a clean reinstall, the issue is still there.
Last edited by ivokosir (2018-02-12 22:38:48)
Offline
I have the same problem on a fresh installation. Seems there is a problem with loading/starting systemd-logind.
buttons not working on bootup
Feb 13 10:03:46 ideapad sddm[312]: Initializing...
Feb 13 10:03:46 ideapad sddm[312]: No session manager found
Feb 13 10:03:46 ideapad sddm[312]: Adding new display on vt 1 ...buttons working after restarting sddm service
Feb 13 10:04:39 ideapad sddm[720]: Initializing...
Feb 13 10:04:39 ideapad sddm[720]: Logind interface found
Feb 13 10:04:39 ideapad sddm[720]: Starting...
Feb 13 10:04:39 ideapad sddm[720]: Adding new display on vt 1 ...I was not able to figure out what's excatcly the problem, any ideas?
Offline
Thanks, your input really helped me!
Ok, so i noticed that string "No session manager found" is printed in this file.
This means that there is no "org.freedesktop.login1", which is systemd-logind.
When i look at sddm.service, it doesn't have to be run after systemd-logind, as my dependency suggests. I would say this is a bug, but I'm not sure who is to blame here.
I added "systemd-logind.service" to "After" line in my "/usr/lib/systemd/system/sddm.service", so line like this now:
After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service systemd-logind.serviceI don't know who is to blame here, maybe there was some change in systemd or arch, I would appreciate any help or recommandation where should i file this bug.
Currently i created issue in sddm github repo.
Edit:
The older install i have does not expirience the same issue. For some reason, systemd-user-sessions.service (wich sddm.service dpends on) does wait for systemd-logind.service even if they are not dependant on eachother. I'm not systemd guru, so i don't know what is happening.
Last edited by ivokosir (2018-02-14 00:07:41)
Offline
Thanks for the workaround.
The older install i have does not expirience the same issue. ...
Same here, on an older installation it works without changing sddm.service file.
Offline
I have this issue only on 1 of 3 ArchLinux systems, the newest and fastest one.
Therfore my assumption is, without dependency on logind, sddm is started too early on fast systems.
On slower machines logind is done starting when sddm needs it.
The mentioned experiences above seem to fit in this picture.
Offline
Therfore my assumption is, without dependency on logind, sddm is started too early on fast systems.
I cannot confirm this. My machine with the older install is faster than the one I get the issue on.
Also the issue did not occur on the same machine with an older install. (I reinstalled Arch after temporarily using another distro.. )
Offline