I was changing some udev rules last night and ran "udevadm trigger" (which I found on the internet to avoid a reboot).
This morning trying to watch a video, I had no sound. For some reason my sound output had been set to SPDIF rather than the HDMI I always had it set to.
Was that a "trigger" side effect, or is something more mysterious going on (I haven't installed any updates or rebooted).
A global "udevadm trigger" often has weird effects.
All of the initial setup udev rules get re-run and will re-assert those settings and override the current state.
Without digging through the udev rules it would be hard to tell, but in general a udevadm trigger re-executes the udev rules used when the devices are initially found and can reset devices settings back to the udev rule(s) want that other applications had changed/overrode.
On Tue, Jul 26, 2022 at 9:37 AM Tom Horsley horsley1953@gmail.com wrote:
I was changing some udev rules last night and ran "udevadm trigger" (which I found on the internet to avoid a reboot).
This morning trying to watch a video, I had no sound. For some reason my sound output had been set to SPDIF rather than the HDMI I always had it set to.
Was that a "trigger" side effect, or is something more mysterious going on (I haven't installed any updates or rebooted). _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure