FS#65842 - [systemd] Add support for properly disabling systemd-homed
Attached to Project:
Arch Linux
Opened by helle vaanzinn (glitsj16) - Sunday, 15 March 2020, 09:33 GMT
Last edited by Christian Hesse (eworm) - Thursday, 02 April 2020, 11:35 GMT
Opened by helle vaanzinn (glitsj16) - Sunday, 15 March 2020, 09:33 GMT
Last edited by Christian Hesse (eworm) - Thursday, 02 April 2020, 11:35 GMT
|
Details
Description:
The introduction of homed in systemd 245 is not quite ready yet IMHO. For now a user who wants to disable it has to mask systemd-homed.service, which is sub-optimal. Upstream already has a fix that enables users to properly disable the service like any other: https://github.com/keszybz/systemd/commit/54b25e4910d409eead8161091b949f6988000db8. Please consider including that patch asap. Additional info: * package version(s) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: |
This task depends upon
Closed by Christian Hesse (eworm)
Thursday, 02 April 2020, 11:35 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 245.4-2
Thursday, 02 April 2020, 11:35 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 245.4-2
I do hope that will never change. My apologies for not being fully clear on this. I happen to use autologin with GDM and that is now fully broken with systemd 245-{1,2,3}:
$ pacman -Q gdm systemd
gdm 3.34.1-2
systemd 245-3
$ cat /etc/gdm/custom.conf
# GDM configuration storage
[daemon]
# Uncomment the line below to force the login screen to use Xorg
#WaylandEnable=false
AutomaticLogin=glitsj16
AutomaticLoginEnable=true
TimedLoginEnable=false
[security]
# If true, then always append -nolisten tcp to the command line
# when starting attached Xservers, thus disallowing TCP connection.
# This is a more secure configuration if you are not using remote connections.
DisallowTCP=true
[xdmcp]
Enable=false
[chooser]
[debug]
# Uncomment the line below to turn on debugging
#Enable=true
$ journalctl --no-hostname -u systemd-logind
-- Logs begin at Fri 2020-03-13 05:26:54 CET, end at Fri 2020-03-13 05:32:19 CET. --
Mar 13 05:26:56 systemd[1]: Starting Login Service...
Mar 13 05:26:58 systemd-logind[813]: New seat seat0.
Mar 13 05:26:58 systemd[1]: Started Login Service.
Mar 13 05:27:01 systemd-logind[813]: New session 1 of user glitsj16.
Mar 13 05:27:47 systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: systemd-logind.service: Succeeded.
Mar 13 05:27:47 systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1.
Mar 13 05:27:47 systemd[1]: Stopped Login Service.
Mar 13 05:27:47 systemd[1]: Starting Login Service...
Mar 13 05:27:49 systemd-logind[1077]: New seat seat0.
Mar 13 05:27:49 systemd-logind[1077]: Failed to add user by file name 1001, ignoring: Invalid argument
Mar 13 05:27:49 systemd-logind[1077]: User enumeration failed: Invalid argument
Mar 13 05:27:49 systemd-logind[1077]: User of session 1 not known.
Mar 13 05:27:49 systemd-logind[1077]: Session enumeration failed: No such file or directory
Mar 13 05:27:49 systemd[1]: Started Login Service.
Mar 13 05:27:49 systemd-logind[1077]: New session 3 of user glitsj16.
$ journalctl --no-hostname -u systemd-homed
-- Logs begin at Fri 2020-03-13 05:26:54 CET, end at Fri 2020-03-13 05:33:29 CET. --
Mar 13 05:26:56 systemd[1]: Starting Home Manager...
Mar 13 05:26:58 systemd[1]: Started Home Manager.
Mar 13 05:27:47 systemd[1]: systemd-homed.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: systemd-homed.service: Succeeded.
$ journalctl --no-hostname | grep Unexpected
Mar 13 05:27:47 systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: rtkit-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: ead.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: iwd.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: upower.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: systemd-logind.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: systemd-homed.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: polkit.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: accounts-daemon.service: Unexpected error response from GetNameOwner(): Connection terminated
Mar 13 05:27:47 systemd[1]: NetworkManager-dispatcher.service: Unexpected error response from GetNameOwner(): Connection terminated
I can live with the urgency-level being lowered. But when reading through
https://bugs.archlinux.org/task/65825
https://bugs.archlinux.org/task/65819
https://bugs.archlinux.org/task/65791
https://bugs.archlinux.org/task/65777
I do think this wasn't a very well-tested nor well-thought-through introduction of homed in the first place.