Bug 2186090

Summary:	udev rules use obsolete 'plugdev' group
Product:	[Fedora] Fedora	Reporter:	Michael Tatarinov <kukabu>
Component:	rtl-sdr	Assignee:	Jaroslav Škarvada <jskarvad>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	jskarvad
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rtl-sdr-0.6.0^20230403git142325a9-2.fc39 rtl-sdr-0.6.0^20230403git142325a9-2.fc38 rtl-sdr-0.6.0^20230403git142325a9-2.fc37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-04-13 14:14:54 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Tatarinov 2023-04-12 05:16:03 UTC

Description of problem:
The rtl-sdr uses the obsolete group mechanism in udev rules. The correct action is to use tags the devices as 'uaccess'.

Version-Release number of selected component (if applicable):
0.6.0^20230403git142325a9

Steps to Reproduce:
1.grep plugdev /usr/lib/udev/rules.d/10-rtl-sdr.rules 

Actual results: see rules using plugdev

Expected results: no plugdev use

Comment 1 Jaroslav Škarvada 2023-04-13 13:53:57 UTC

It has ENV{ID_SOFTWARE_RADIO}="1" which is processed and tagged by uaccess rule, thus it works correctly on desktop.

What's wrong with the plugdev? It's for server usage and workaround for cases where there is no logind / logged user.

Comment 2 Jaroslav Škarvada 2023-04-13 13:56:24 UTC

But on Fedora it should be rtlsdr group, not plugdev. I will fix it.

Comment 3 Fedora Update System 2023-04-13 14:13:28 UTC

FEDORA-2023-ab4fac3625 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ab4fac3625

Comment 4 Fedora Update System 2023-04-13 14:14:54 UTC

FEDORA-2023-ab4fac3625 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2023-04-13 16:14:21 UTC

FEDORA-2023-3e1b6ee468 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-3e1b6ee468

Comment 6 Fedora Update System 2023-04-13 16:14:54 UTC

FEDORA-2023-62e02edee1 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-62e02edee1

Comment 7 Fedora Update System 2023-04-14 02:41:59 UTC

FEDORA-2023-3e1b6ee468 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3e1b6ee468

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

Comment 8 Fedora Update System 2023-04-14 02:46:39 UTC

FEDORA-2023-62e02edee1 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-62e02edee1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-62e02edee1

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

Comment 9 Michael Tatarinov 2023-04-14 03:12:21 UTC

Thanks.

Comment 10 Fedora Update System 2023-04-22 00:47:32 UTC

FEDORA-2023-3e1b6ee468 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2023-04-22 00:54:54 UTC

FEDORA-2023-62e02edee1 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.