Description of problem: Holy moly, why involve udev in this at all? Please just check the kernel command line when starting sddm. And if sddm cannot check itself, do it in ExecStartPre=. There is really no need to touch the file system on every udev add, remove, change, bind, and unbind event. Version-Release number of selected component (if applicable): sddm-0.19.0-13.fc34.x86_64
$ cat /usr/lib/udev/rules.d/61-sddm-plasmawayland.rules # disable Wayland if modesetting is disabled RUN+="/usr/bin/rm -f /etc/sddm/hide-wayland-sessions" IMPORT{cmdline}="nomodeset", RUN+="/usr/bin/touch /etc/sddm/hide-wayland-sessions"
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
"Holy moly, why involve udev in this at all?" because we were in a hurry and it was the best idea we had at the time...this was to fix https://bugzilla.redhat.com/show_bug.cgi?id=1952431 . Neal came up with the initial plan which involved a udev rule running a script that did a bunch of stuff then touched `/etc/sddm/hide-wayland-sessions`, we noted that would mean it was hidden forever and added the step of wiping the file at the start of the udev rule, then I suggested just getting rid of the script and having the udev rule create the file then remove it if nomodeset was in cmdline. I was focusing on the messiness of the script, so didn't really think about how much activity the udev rule would cause. As Jeremy points out, the change he recently made to fix https://bugzilla.redhat.com/show_bug.cgi?id=2016788 should also address this concern: https://src.fedoraproject.org/rpms/sddm/c/52dc921f03abf4524bb2ca249ef28cf78b8c0e4a?branch=rawhide so I'll mark the update as fixing this bug too.
FEDORA-2021-631306a178 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-631306a178
Thanks! That update removes the file altogether, so "should also address" → "addresses" :)
FEDORA-2021-631306a178 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.