You are not logged in.
reztho:
$ for i in /usr/lib/tmpfiles.d/*.conf; do pacman -Qo $i ; done | cut -d ' ' -f5 | sort -u alsa-utils audit dbus dhcpcd filesystem geoclue kio-fuse libutempter man-db mkinitcpio openssh pam sddm shadow sudo systemd tpm2-tss udisks2 util-linux
(couldn't reproduce the bug yet, running paru now instead of yay)
I use paru too. It's some pacman hook, no AUR helper is going to prevent the issue from happening since all of them depend on pacman after all.
Here's the list of what we have in common:
alsa-utils
audit
dbus
dhcpcd
filesystem
geoclue
libutempter
man-db
mkinitcpio
openssh
pam
sddm
shadow
sudo
systemd
tpm2-tss
udisks2
util-linux
Interestingly, we both use sddm.
Offline
The pacman hook is "easily" explained by https://bugs.archlinux.org/task/77789 and can be fixed with
sudo touch /etc/systemd/do-not-udevadm-trigger-on-update
Generally speaking the potential side effects from not doing this are too big in regards to the benefits you get from running a full rule retrigger, that I'd personally reccommend everyone to just do that. This isn't limited to nvidia, I had session crashes because amdgpu wasn't available anymore,
Offline
Hi, do you still recall the nature of the update crash?
Did the system suddenly reboot or did it stall and you then rebooted it with the power button?
---
This is a mass-inquiry, so please excuse if your thread actually detailed that.
We're trying to get some data on the situation, so it would be very helpful if you can just briefly respond.
Thanks a lot.
Offline