Systemd 240 update breaks graphical login

[anon27588196]

It might be a combination...

I have coredump of xfce4-session and light-locker.

Also have strange new ACPI errors:

Dec 22 09:35:53 Jammin1 kernel: ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
Dec 22 09:35:53 Jammin1 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
Dec 22 09:35:53 Jammin1 kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.RP04.PXSX, AE_NOT_FOUND (20170728/psparse-550)
Dec 22 09:35:53 Jammin1 kernel: ACPI Error: [_SB_.PCI0.RP09.PXSX] Namespace lookup failure, AE_NOT_FOUND (20170728/dswload2-191)
Dec 22 09:35:53 Jammin1 kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20170728/psobject-252)
Dec 22 09:35:53 Jammin1 kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.RP08.PXSX, AE_NOT_FOUND (20170728/psparse-550)

Something going on with mdadm:

Dec 22 09:35:53 Jammin1 [407]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sdb5 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [335]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sda5 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [367]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sdb4 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [402]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sdb3 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [378]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sdb6 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [388]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sda2 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [382]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sda6 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [351]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sda4 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [357]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sdb2 --offroot ${DEVLINKS}': Input/output error
Dec 22 09:35:53 Jammin1 [448]: Failed to wait spawned command '/usr/bin/mdadm --incremental --export /dev/sda3 --offroot ${DEVLINKS}': Input/output error

And, a couple of other random entries:

Dec 22 09:35:53 Jammin1 kernel: amdgpu 0000:01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0xffff
Dec 22 09:35:53 Jammin1 kernel: (NULL device *): hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().

I also downgraded everything (systemd and linux-firmware) and all is well again.

[Librewish]

No problem here with kde on unstable
With latest firmware and systemd 240

[viking]

I just logged in to report this as well.

Updated 12 packages this morning, rebooted this afternoon and no graphical login (error something like 'can't find settings manager' - don't know exactly, I didn't write it down).
Used the fantastic 'Timeshift' to restore to yesterdays disk image, all was well.
Redid the update with the 8 updates that weren't to do with systemd, rebooted and all was well again. So proof positive that systemd is the problem (if you ever needed proof of that).

I am on Xfce4 unstable.

Holding systemd updates for now.

[CMarch]

Same as @Librewish. " No problem here with kde on unstable With latest firmware and systemd 240"

Did get a few pacman: [ALPM-SCRIPTLET] Failure to communicate with kernel device-mapper driver. etc errors. But I always reboot after getting these errors and go on my merry way with no ill effects.

[jonathon]

240.1 is in unstable now.

[viking]

240.1 is just as bad.
Incidentally the error message is:

Unable to contact settings server
Connection Refused

[nam1962]

Same for me : 240.1 breaks boot
First symptom : shutdown after update or after switch from stable to unstable takes forever (and then no boot)

[Unstable Update] 2018-12-14 - Cinnamon, Deepin, QT5, Systemd, KDE-Apps, KDE-Framework, Mesa

Broken ! I get a GUI popup : "impossible de contacter le serveur de configuration" No cursor, thus cannot clic, doesn't react to keys Tried fallback 4.19 : idem Tried tty, had to go to tty4 Tried rm -rf ~/.cache/sessions/no effect Now changing for stable [Edit] My details (back to stable) tell me if logs needed ~]$ inxi CPU: Dual Core Intel Core i3-2370M (-MT MCP-) speed/min/max: 2166/800/2400 MHz Kernel: 4.19.12-1-MANJARO x86_64 Up: 2m Mem: 1798.6/5855.9 MiB (30.7%) Storage: 698.64 Gi…

[philm]

Please test v240.1-2 and report back ...

[viking]

I will do when I see it, but not available yet (German mirrors)

Edit. 240.1-2 has just arrived I will try it now.

[viking]

240.1-2 is bad as well.
Same error.

[philm]

Hmm, I didn't had time yet to test. Maybe I'll update a fresh v18.0.1 version in VB which I'm currently uploading ...

[philm]

I just updated a fresh Gnome v18.0.1 to systemd 240.1-2 without any issues. Seems only old installations may have problems, on which I don't know why. Did systemd 239.370-1 work? See current issues reported to the Arch-Bugtracker ... You may also see the changelog of fedora, which is upstream for systemd.

[davidex]

i just changed branch to testing that contains systemd 239.370-2 and it works

[jonathon]

Might also be having issues with my X230. I'll check more tomorrow.

[Librewish]

Just updated still no problem works fine

[sueridgepipe]

No issues for me on an old KDE VM, after reading this thread I was almost expecting the system to blow up, but alas not.

I'll update my other VMs then bare metal update on my secondary laptop.

EDIT :

No issues at all for me on any of my unstable systems, all fully encrypted KDE systems, all running linux419 4.19.12-1 with systemd 240.1-2.

Is this a GTK based DE / DM related issue?

Only warning was to do with appstream metadata.

[ALPM] running 'update-appstream-cache.hook'...
[ALPM-SCRIPTLET] The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information.

[bogdancovaciu]

No issues for me on Gnome, KDE Plasma and i3 - but i get this on Cinnamon and XFCE

The login screen loads correctly, but then the login fails:

Unable to determine failsafe session name. Possible causes: xfconfd isn't running (D-Bus setup problem); environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"), or xfce4-session is installed incorrectly.

• On Budgie the login just goes in a loop with no error display.

I can reach the desktop on all of them from TTY2 with the startx command and logged with my user.

No time to check journactl and/or fixes for this. Probably i will be able later this evening.

[Erwan]

tested this morning, still broken...

déc. 23 08:46:14 manjaro systemd-udevd[242]: Failed to wait spawned command '/usr/bin/alsactl restore 1': Input/output error
déc. 23 08:46:17 manjaro systemd-udevd[242]: Failed to wait spawned command '/usr/bin/alsactl restore 0': Input/output error
déc. 23 08:45:44 manjaro kernel: traps: light-locker[679] trap int3 ip:7fe19f317c36 sp:7ffc9121cc50 error:0
déc. 23 09:01:58 manjaro pulseaudio[734]: ICE default IO error handler doing an exit(), pid = 734, errno = 11

[anon35400795]

could this be related to dbus-x11 vs dbus?

No issues on *gnome unstable w/ wayland; upgrade via gnome-software.

except...

-- Logs begin at Sat 2018-09-22 11:33:23 CEST, end at Sun 2018-12-23 11:54:31 CET. --
Dez 23 11:53:46 balder systemd-udevd[433]: Failed to wait spawned command '/usr/bin/set-wireless-regdom': Input/output error
Dez 23 11:53:46 balder systemd-udevd[428]: Failed to wait spawned command '/usr/bin/alsactl restore 1': Input/output error
Dez 23 11:53:46 balder systemd-udevd[474]: Failed to wait spawned command '/usr/bin/alsactl restore 2': Input/output error
Dez 23 11:53:46 balder systemd-udevd[558]: Failed to wait spawned command '/usr/bin/alsactl restore 0': Input/output error
Dez 23 11:53:51 balder colord-sane[767]: io/hpmud/pp.c 627: unable to read device-id ret=-1
Dez 23 11:53:58 balder bluetoothd[667]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Dez 23 11:53:58 balder bluetoothd[667]: RFCOMM server failed for :1.221/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb: rfcomm_bind: Address already in use (98)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:03 balder bluetoothd[667]: bt_uhid_send: Invalid argument (22)
Dez 23 11:54:07 balder gnome-session-binary[3357]: Unrecoverable failure in required component org.gnome.Shell.desktop

That bluetooth thing is just normal for my system. Everything else is not. But no issues at the graphicsl session or boot at all.

[viking]

My investigations this morning don't lead me very far, just 2 things found.

1] It is only the 'systemd' package itself that causes the problem, I have updated the other 3 (lib32-systemd, libsystemd and systemd-sysvcompat with no ill effects).

2] Unlike bogdancovaciu in his post above I am unable to reach a graphical login from a TTY.
Running 'startx' just drops me back to the non-graphical login, and running 'startxfce4' generates the following error message:

[ 341.513] _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
[ 341.513] _XSERVTransMakeAllCOTSServerListeners: server already running
[ 341.513] (EE)
Fatal server error:
[ 341.513] (EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
[ 341.513] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 341.513] (EE) Please also check the log file at "/home/manjaro/.local/share/xorg/Xorg.0.log" for additional information.
[ 341.513] (EE)
[ 341.513] (EE) Server terminated with error (1). Closing log file.