Description of problem: /usr/lib/udev/rules.d/99-graphlcd-base.rules is specifying not existing group "uucp" Version-Release number of selected component (if applicable): rpm -qf /usr/lib/udev/rules.d/99-graphlcd-base.rules graphlcd-common-2.0.2-1.fc33.x86_64 Steps to Reproduce: 1. use e.g.vdr-graphlcd 2. watch log Actual results: systemd-udevd[555]: /usr/lib/udev/rules.d/99-graphlcd-base.rules:5 Unknown group 'uucp', ignoring systemd-udevd[555]: /usr/lib/udev/rules.d/99-graphlcd-base.rules:6 Unknown group 'uucp', ignoring systemd-udevd[555]: /usr/lib/udev/rules.d/99-graphlcd-base.rules:8 Unknown group 'uucp', ignoring Expected results: no such message Additional info: serial devices have nowadays group "dialout" applied ll /dev/ttyS0 crw-rw---- 1 root dialout 4, 64 30. Jan 07:56 /dev/ttyS0
FEDORA-2021-690e377394 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-690e377394
FEDORA-2021-17a1142d5f has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-17a1142d5f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-17a1142d5f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-690e377394 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-690e377394` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-690e377394 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-690e377394 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-17a1142d5f has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.