You are not logged in.
Recently, about months ago, I start to get the issue with "pacman -Syu" which will cause xorg/i3wm log out while the post-isntallation hooks 'Reloading device manager configuration' in the termintal.
The issue is almost the same with this thread https://bbs.archlinux.org/viewtopic.php?id=286657
In that thread they advice to only keep '/usr/share/X11/xorg.conf.d/10-quirks.conf' and remove other '/usr/share/X11/xorg.conf.d/*.conf' which related to 'evdev'.
But, it doesn't work for me, even I removed all *.conf related to 'evdev'.
Later I found pacman reinstall the package 'pulseaudio' can 100% cause the issue, because the package post-installation will hook 'Reloading device manager configuration'.
here is the pacman log:
[2023-08-01T15:52:03+0800] [PACMAN] Running 'pacman --color auto -S extra/pulseaudio-jack'
[2023-08-01T15:52:05+0800] [ALPM] transaction started
[2023-08-01T15:52:05+0800] [ALPM] installed pulseaudio-jack (16.1-6)
[2023-08-01T15:52:05+0800] [ALPM] transaction completed
[2023-08-01T15:52:05+0800] [ALPM] running '30-systemd-update.hook'...
[2023-08-01T15:52:14+0800] [PACMAN] Running 'pacman --color auto -S extra/pulseaudio-bluetooth'
[2023-08-01T15:52:17+0800] [ALPM] transaction started
[2023-08-01T15:52:17+0800] [ALPM] installed pulseaudio-bluetooth (16.1-6)
[2023-08-01T15:52:17+0800] [ALPM] transaction completed
[2023-08-01T15:52:17+0800] [ALPM] running '30-systemd-update.hook'...
[2023-08-01T15:55:17+0800] [PACMAN] Running 'pacman --color auto -S extra/pulseaudio'
[2023-08-01T15:55:20+0800] [ALPM] transaction started
[2023-08-01T15:55:20+0800] [ALPM] reinstalled pulseaudio (16.1-6)
[2023-08-01T15:55:20+0800] [ALPM] transaction completed
[2023-08-01T15:55:20+0800] [ALPM] running '30-systemd-udev-reload.hook'...
[2023-08-01T15:55:21+0800] [ALPM] running '30-systemd-update.hook'...
[2023-08-01T15:55:21+0800] [ALPM] running 'glib-compile-schemas.hook'...How to debug this issue? please help.
Last edited by cstn (2023-08-01 08:37:08)
Offline
There are many things that suffer from this, it's triggered by a lot more then just obsolote xorg configs.
A change in /usr/share/libalpm/scripts/systemd-hook is the root cause, see https://bugs.archlinux.org/task/77789 for more info .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline