Bug 651392

Summary:	sys-apps/systemd: systemd-rfkill: Failed to open device rfkill2: No such device
Product:	Gentoo Linux	Reporter:	Pacho Ramos <pacho>
Component:	Current packages	Assignee:	Gentoo systemd Team <systemd>
Status:	RESOLVED UPSTREAM
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://github.com/systemd/systemd/issues/8586
Whiteboard:
Package list:		Runtime testing required:	---

Description Pacho Ramos gentoo-dev

2018-03-24 22:57:09 UTC

When resuming from suspend I see this message, I don't know if it's normal (because it is shown in "red" color) or maybe I have some kernel option disabled or so :/
mar 24 23:49:00 dell-2017 systemd[1]: Starting Load/Save RF Kill Switch Status...
mar 24 23:49:00 dell-2017 bluetoothd[343]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSink
mar 24 23:49:00 dell-2017 upowerd[449]: unhandled action 'unbind' on /sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.1
mar 24 23:49:00 dell-2017 bluetoothd[343]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSource
mar 24 23:49:00 dell-2017 systemd-rfkill[3774]: Failed to open device rfkill2: No such device
mar 24 23:49:00 dell-2017 bluetoothd[343]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSink

Comment 1 Pacho Ramos gentoo-dev

2018-03-25 10:14:11 UTC

At least in 237 it was being shown too.. maybe it has been there for a long time and only noticed now because I was reviewing logs more deeply due to a different issue

Comment 2 Mike Gilbert gentoo-dev

2018-03-25 14:19:05 UTC

Seems like a race between udev add/remove events and rfkill trying to open the device. I suggest seeking help upstream on this.

Comment 3 Pacho Ramos gentoo-dev

2018-03-26 21:18:53 UTC

Sure :)

Comment 4 Pacho Ramos gentoo-dev

2018-04-05 22:00:42 UTC

upstream fixed it in git... this is not a major issue, hence, I think we can simply wait for the next upstream release