Bug 1779855 - udev rule: Unknown group 'plugdev'
Summary: udev rule: Unknown group 'plugdev'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: android-tools
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ivan Afonichev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-04 21:04 UTC by Christian Stadelmann
Modified: 2021-06-03 12:07 UTC (History)
4 users (show)

Fixed In Version: android-tools-30.0.5p1-1.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-02 01:21:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christian Stadelmann 2019-12-04 21:04:13 UTC
Description of problem:
The example udev rules file contains a group "plugdev" which does not exist on Fedora.

Version-Release number of selected component (if applicable):
20180828gitc7815d675-4.fc31.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Install android-tools
2. create a symlink /etc/udev/rules.d/51-android.rules linking to /usr/share/doc/android-tools/51-android.rules
3. reboot
4. have a look into your logs

Actual results:
At boot, you get this error message in the syslog:
> systemd-udevd[669]: /etc/udev/rules.d/51-android.rules:8302 Unknown group 'plugdev', ignoring

Expected results:
No error message

Additional info:
This issue is also affecting many other packages.

Comment 1 Ben Cotton 2020-11-03 15:56:25 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Christian Stadelmann 2020-11-04 20:55:39 UTC
Issue still present. Error message appears on every boot.

Comment 3 Fedora Update System 2021-03-24 20:06:37 UTC
FEDORA-2021-0dda64cc5d has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-0dda64cc5d

Comment 4 Fedora Update System 2021-03-25 01:32:22 UTC
FEDORA-2021-0dda64cc5d 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-0dda64cc5d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-0dda64cc5d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-04-02 01:21:07 UTC
FEDORA-2021-0dda64cc5d has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Christian Stadelmann 2021-04-13 20:17:56 UTC
Thank you for fixing this issue!

Comment 7 Maciej Żenczykowski 2021-05-19 22:26:39 UTC
Still broken in fc34 - koji suggests package failed to build...

Comment 8 Christian Stadelmann 2021-06-03 12:07:47 UTC
(In reply to Maciej Żenczykowski from comment #7)
> Still broken in fc34 - koji suggests package failed to build...

That is tracked in bug #1923681


Note You need to log in before you can comment on or make changes to this bug.