Created attachment 1948664 [details] Trivial patch to change RUNTIME_DIR. When updating sddm on Fedora 37 to sddm-0.19.0^git20230214.8f1e3df-1.fc37.x86_64, the warning: | /usr/lib/tmpfiles.d/sddm.conf:6: Line references path below legacy directory /var/run/, updating /var/run/sddm → /run/sddm; please update the tmpfiles.d/ drop-in file accordingly. is output. The triggering entry is: | # This contains X11 auth files passed to Xorg and the greeter | d /var/run/sddm 0711 root root It should be fixable by patching CMakeLists.txt's: | # Set constants | set(DATA_INSTALL_DIR "${CMAKE_INSTALL_FULL_DATADIR}/sddm" CACHE PATH "System application data install directory") | set(DBUS_CONFIG_DIR "${CMAKE_INSTALL_SYSCONFDIR}/dbus-1/system.d" CACHE PATH "DBus config files directory") | set(STATE_DIR "${CMAKE_INSTALL_FULL_LOCALSTATEDIR}/lib/sddm" CACHE PATH "State directory") | set(RUNTIME_DIR "${CMAKE_INSTALL_FULL_LOCALSTATEDIR}/run/sddm" CACHE PATH "Runtime data storage directory") ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | set(QML_INSTALL_DIR "${QT_IMPORTS_DIR}" CACHE PATH "QML component installation directory") but I have not tested the attached patch beyond verifying that /usr/lib/tmpfiles.d/sddm.conf then refers to /run/sddm. This was previously reported as bugs #1748321 and #1795294.
Thanks for the help! We fixed this upstream though: https://github.com/sddm/sddm/pull/1678
FEDORA-2023-719e0e1399 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-719e0e1399
FEDORA-2023-719e0e1399 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-719e0e1399` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-719e0e1399 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-719e0e1399 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.