Those are systemd-235-5 packages which I already have installed on my hardware test systems. I did install the systemd-235-6 packages in main-testing and still have the same problem with install. During install computer screen starts rapidly flashing. In journalctl this sequence repeats many times:
Nov 17 18:40:16 ben79-pc acpid[3582]: 1 client rule loaded
Nov 17 18:40:16 ben79-pc sddm[4045]: /usr/bin/xauth: (stdin):1: bad "remove" command line
Nov 17 18:40:16 ben79-pc sddm[4045]: /usr/bin/xauth: (stdin):2: bad "add" command line
Nov 17 18:40:16 ben79-pc sddm[4045]: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
Nov 17 18:40:16 ben79-pc acpid[3582]: client 12103[0:0] has disconnected
Nov 17 18:40:16 ben79-pc acpid[3582]: client connected from 12118[0:0]
Nov 17 18:40:16 ben79-pc acpid[3582]: 1 client rule loaded
Nov 17 18:40:17 ben79-pc sddm[4045]: /usr/bin/xauth: (stdin):1: bad "remove" command line
Nov 17 18:40:17 ben79-pc sddm[4045]: /usr/bin/xauth: (stdin):2: bad "add" command line
Nov 17 18:40:17 ben79-pc sddm[4045]: QProcess: Destroyed while process ("/usr/libexec/sddm-helper") is still running.
Nov 17 18:40:17 ben79-pc acpid[3582]: client 12118[0:0] has disconnected
Nov 17 18:40:17 ben79-pc acpid[3582]: client connected from 12133[0:0]
Hoping this is helpful.
Edit: Even though screen is flashing I was able to type reboot and system did reboot and systemd-235-6 from that point seems to work OK.
Note to anyone testing these systemd packages. Check and remember/write down the time you are doing actual install so if there is a problem you can easily find journalctl logs.
Edit: Also anyone testing these packages it is a good idea first update everything else and reboot and then to download all packages first with:
I updated to systemd vs. 235 - 6 this evening and saw the same behaviour as ben79. While dbus was at 1.12.2, I didnât update sddm to 0.16.0-4 until after updating systemd.
Looking fruther at the logs right after âurpmi -v --auto-updateâ I see:
Nov 17 18:39:16 ben79-pc systemd[1]: Reexecuting.
Nov 17 18:39:16 ben79-pc systemd[1]: systemd 235 running in system mode. (+PAM +AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +>
Nov 17 18:39:16 ben79-pc systemd[1]: Detected architecture x86-64.
Nov 17 18:39:16 ben79-pc systemd[1]: File /lib/systemd/system/systemd-journald.service:33 configures an IP firewall (IPAddressDeny=any), but the local system>
Nov 17 18:39:16 ben79-pc systemd[1]: Proceeding WITHOUT firewalling in effect!
Nov 17 18:39:16 ben79-pc systemd[1]: File /lib/systemd/system/systemd-udevd.service:32 configures an IP firewall (IPAddressDeny=any), but the local system do>
Nov 17 18:39:16 ben79-pc systemd[1]: Proceeding WITHOUT firewalling in effect!
Nov 17 18:39:16 ben79-pc systemd[1]: File /lib/systemd/system/systemd-logind.service:34 configures an IP firewall (IPAddressDeny=any), but the local system d>
Nov 17 18:39:16 ben79-pc systemd[1]: Proceeding WITHOUT firewalling in effect!
Nov 17 18:39:16 ben79-pc systemd[1]: File /lib/systemd/system/systemd-coredump@.service:37 configures an IP firewall (IPAddressDeny=any), but the local syste>
Nov 17 18:39:16 ben79-pc systemd[1]: Proceeding WITHOUT firewalling in effect!
Nov 17 18:39:16 ben79-pc polkitd[3632]: Reloading rules
Nov 17 18:39:16 ben79-pc polkitd[3632]: Collecting garbage unconditionally...
Nov 17 18:39:16 ben79-pc polkitd[3632]: Loading rules from directory /etc/polkit-1/rules.d
Nov 17 18:39:16 ben79-pc polkitd[3632]: Loading rules from directory /usr/share/polkit-1/rules.d
Nov 17 18:39:16 ben79-pc polkitd[3632]: Finished loading, compiling and executing 5 rules
Nov 17 18:39:16 ben79-pc polkitd[3632]: Reloading rules
Nov 17 18:39:16 ben79-pc polkitd[3632]: Collecting garbage unconditionally...
Nov 17 18:39:16 ben79-pc polkitd[3632]: Loading rules from directory /etc/polkit-1/rules.d
Nov 17 18:39:16 ben79-pc polkitd[3632]: Loading rules from directory /usr/share/polkit-1/rules.d
Nov 17 18:39:16 ben79-pc polkitd[3632]: Finished loading, compiling and executing 5 rules
Nov 17 18:39:16 ben79-pc systemd[1]: Listening on udev Kernel Socket.
Nov 17 18:39:16 ben79-pc systemd[1]: Listening on udev Control Socket.
Nov 17 18:39:16 ben79-pc systemd[1]: Starting udev Kernel Device Manager...
Nov 17 18:39:16 ben79-pc systemd[1]: Started udev Kernel Device Manager.
Nov 17 18:39:17 ben79-pc kernel: FINAL_REJECT: IN=enp3s0 OUT= MAC=ff:ff:ff:ff:ff:ff:64:66:b3:dd:f8:c4:08:00 SRC=192.168.0.1 DST=255.255.255.255 LEN=201 TOS=0>
Nov 17 18:39:17 ben79-pc systemd[1]: Stopping Login Service...
Nov 17 18:39:17 ben79-pc systemd[1]: Stopped Login Service.
Nov 17 18:39:17 ben79-pc systemd[1]: Starting Login Service...
Nov 17 18:39:17 ben79-pc systemd[1]: Started Login Service.
Nov 17 18:39:17 ben79-pc systemd-logind[5229]: New seat seat0.
Nov 17 18:39:17 ben79-pc systemd-logind[5229]: Watching system buttons on /dev/input/event1 (Power Button)
Not sure if this is relevant but the line with âReexecutingâ make me wonder if something is triggering systemd to run again during the package install as if it were starting the machine?
Edit: Then stopping login service and then starting login service. I believe that would be the sddm misbehaving you asked us to look for?
@TPG hereâs the entire journalctl log from the boot where I installed the systemd-235-6 packages. What I did was first put systemd in skip.list and update everything else and reboot. Then remove systemd from skip.list and install the systemd packages.