RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1691197 - 'Error setting up rfkill: Could not open RFKILL control device, please verify your installation' output in message.
Summary: 'Error setting up rfkill: Could not open RFKILL control device, please verify...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-settings-daemon
Version: 7.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: pre-dev-freeze
: 7.8
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1689420 1719882 1727111 1754591
TreeView+ depends on / blocked
 
Reported: 2019-03-21 06:11 UTC by xiaochun lee
Modified: 2023-03-24 14:38 UTC (History)
10 users (show)

Fixed In Version: gnome-settings-daemon-3.28.1-6.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 19:39:00 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
System journal from reproducing the bug under RHEL 7.7 x86_64 Server (284.98 KB, text/plain)
2019-09-17 13:27 UTC, Pavlin Georgiev 		no flags Details
System journal from reproducing the bug under RHEL-7.8-20190912.3 Server x86_64 (295.08 KB, text/plain)
2019-09-19 06:32 UTC, Pavlin Georgiev 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:1021 0 None None None 2020-03-31 19:39:39 UTC

Description xiaochun lee 2019-03-21 06:11:31 UTC 
Description of problem:
RHEL-7.5&7.6-GA Message log show "Error setting up rfkill: Could not open RFKILL control device, please verify your installation"
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.Install RHEL 7.6 GA or 7.5 GA
2.Boot into OS
3.Check log file (/var/log/message) information

Actual results:
Message log have error log with  "Error setting up rfkill: Could not open RFKILL control device, please verify your installation" 

Expected results:
No this error in system log

Additional info:
1. I have investigated it deeply, the symptom is reproduced when you login OS from remote after fresh installation, But once you login in OS from the GUI and then reboot OS the error message will disappear.
Comment 2 xiaochun lee 2019-03-21 06:18:24 UTC 
The root cause describe as below:
After fresh installation, when you login in OS from remote, the program" /usr/libexec/gsd-rfkill"  will run with the account named gnome-i+, But after you login in OS via GUI and then reboot OS,  the program" /usr/libexec/gsd-rfkill"  will run with the account named gdm.  However that program will judge the login account， if it not gdm，it will look for the device file /dev/rfkill, but if the modules of rfkill.so can not be loaded before, it will show the error messages that we have saw.
So,  if we don't want to the error messages come out，after we fresh install the OS, we should login in OS via GUI.

The community of gnome-settings-daemon have fixed the issue a few months ago,But OS have not merge to the master branch.
Please refer the below link:
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/42
If the rfkill.ko kernel model isn't loaded when gsd-rfkill is started, gsd-rfkill will attempt to open /dev/rfkill, fail, and then never notice when the rfkill.ko module gets loaded later.

This is the commit id?
https://gitlab.gnome.org/GNOME/gnome-settings-daemon
commit id:e4bc5b81dea5c0bfbfb42a929ea273fe19e72d7c
Comment 3 xiaochun lee 2019-03-21 06:20:59 UTC 
I have submit a FEAT to RHEL 8.1, Now here open the bug for 7.6, Please Notice!
The feature request link is https://bugzilla.redhat.com/show_bug.cgi?id=1665352
Comment 4 xiaochun lee 2019-05-10 08:17:45 UTC 
I have check the RHEL 7.7 Alpha-1, the gnome-settings-daemon just updated to gnome-settings-daemon-3.28.1-3.el7, But a higher version solved the problem.And I will comment here after we test it.
Comment 5 xiaochun lee 2019-05-16 06:18:51 UTC 
We have test the RHEL7.7 Alpha-1, the problem still exists.So need to upgrade the higher version of gnome-settings-daemon.
Comment 6 xiaochun lee 2019-06-20 03:05:20 UTC 
Is there any update for this defect？ I verified
Comment 7 xiaochun lee 2019-06-21 05:52:02 UTC 
Is there any update for this defect？ I have verified the 7.7 snapshot3， But the defect is still exist.
Comment 10 xiaochun lee 2019-07-25 09:02:41 UTC 
Hi,Tomas
I have saw you have change the target release to 7.8, that is ok!  But what about RHEL 8.1? the link is https://bugzilla.redhat.com/show_bug.cgi?id=1665352
Comment 11 Tomas Pelka 2019-07-25 11:11:42 UTC 
(In reply to xiaochun lee from comment #10)
> Hi,Tomas
> I have saw you have change the target release to 7.8, that is ok!  But what
> about RHEL 8.1? the link is
> https://bugzilla.redhat.com/show_bug.cgi?id=1665352

For 7.7 we unfortunately don't have time nor capacity to do it. Honestly also not sure whether we are going to do it in 7.8 and going forward as RHEL7 is entering maintenance phase 2 which limits us what we can rebase. Sorry for that.

For 8.1 see https://bugzilla.redhat.com/show_bug.cgi?id=1665352#c3.

-Tom
Comment 12 xiaochun lee 2019-08-02 06:22:24 UTC 
(In reply to Tomas Pelka from comment #11)
> (In reply to xiaochun lee from comment #10)
> > Hi,Tomas
> > I have saw you have change the target release to 7.8, that is ok!  But what
> > about RHEL 8.1? the link is
> > https://bugzilla.redhat.com/show_bug.cgi?id=1665352
> 
> For 7.7 we unfortunately don't have time nor capacity to do it. Honestly
> also not sure whether we are going to do it in 7.8 and going forward as
> RHEL7 is entering maintenance phase 2 which limits us what we can rebase.
> Sorry for that.
> 
> For 8.1 see https://bugzilla.redhat.com/show_bug.cgi?id=1665352#c3.
> 
> -Tom

Ok,I got it, I have verified it on 8.1 beta 1.0, the defect was fixed.The gnome-setting-daemon version is gnome-settings-daemon-3.32.0-3.el8.x86_64.rpm
Comment 16 Pavlin Georgiev 2019-09-06 10:24:14 UTC 
TEST SETUP
Hardware: PC HP Z200 Workstation
Distro: RHEL 7.5
Component version: gnome-settings-daemon-3.26.2-9.el7

Graphics card: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02)


TEST PROCEDURE
1. Install distro RHEL-7.5 from Beaker.
   https://beaker.engineering.redhat.com/jobs/3770718
2. Do not restart the testing machine.
3. Search for "rfkill" in the system journal.
4. Reboot the machine.
5. Search for "rfkill" in the system journal.


RESULT
I cannot reproduce the bug on that system.
Comment 17 Pavlin Georgiev 2019-09-06 10:25:11 UTC 
TEST SETUP 2
Hardware: PC Dell Inspiron 660s
Distro: RHEL 7.6
Component version: gnome-settings-daemon-3.28.1-2.el7

Graphics card: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09)


TEST PROCEDURE 2
1. Install distro RHEL-7.6 from Beaker.
   https://beaker.engineering.redhat.com/jobs/3770720
2. Do not restart the testing machine.
3. Search for "rfkill" in the system journal.
4. Reboot the machine.
5. Search for "rfkill" in the system journal.


RESULT 2
I cannot reproduce the bug on that system.
Comment 18 Pavlin Georgiev 2019-09-06 12:57:30 UTC 
TEST SETUP 3
Distro: RHEL 7.6
Component version: gnome-settings-daemon-3.28.1-2.el7


TEST PROCEDURE 3
1. Install distro RHEL 7.6 on a VM from ISO file:
   http://download-ipv4.eng.brq.redhat.com/released/rhel-7/RHEL-7/7.6/Workstation/x86_64/iso/RHEL-7.6-20181010.0-Workstation-x86_64-dvd1.iso
2. After clean install, do not log in via GUI.
3. Connect remotely to that VM.
4. Search for "rfkill" in the system journal.


RESULT 3
I cannot reproduce the bug on that system.
Comment 19 Pavlin Georgiev 2019-09-06 15:17:55 UTC 
TEST SETUP 4
Distro: RHEL-7.8-20190905.0
Component version: gnome-settings-daemon-devel-3.28.1-7.el7

Graphics card: 2nd Generation Core Processor Family Integrated Graphics Controller


TEST PROCEDURE 4
1. Install distro RHEL-7.8-20190905.0 from Beaker.
   https://beaker.engineering.redhat.com/jobs/3771016
2. Do not restart the testing machine.
3. Search for "rfkill" in the system journal.
4. Reboot the machine.
5. Search for "rfkill" in the system journal.


RESULT 4
I cannot reproduce the bug on that system.
Comment 21 xiaochun lee 2019-09-17 09:17:11 UTC 
The symptom is reproduced when you complete installation then reboot OS and  first log in OS via remote ssh or press F2 enter into runlevel 3 mode, But once you have logged in OS via GUI and then reboot OS the error message will disappear. It disappeared while log in via F2 or remote ssh, But if you log via GUI, the error still exist.

After fresh installation, when you login in OS via remote ssh or press F2 enter into runlevel 3 mode, the program" /usr/libexec/gsd-rfkill"  will run with the account named gnome-i+,but if the os is logged in via the gui once, then reboot OS and log in via remote ssh or runlevel3,  the program" /usr/libexec/gsd-rfkill"  will run with the account named gdm.  However rfkill program will judge the login account, if it not gdm, it will look for the device file /dev/rfkill, but if the modules of rfkill.ko can't be loaded automatic before, because the server haven't a Bluetooth device, So it will show the error messages that we have saw.

Here give a step by step description of how to reproduce the issue.
Hardware: ThinkSystem SR650
Distro: RHEL 7.7
Component version: gnome-settings-daemon-3.28.1-4.el7.x86_64

	1. Install distro RHEL-7.7-20190723.1-Server-x86_64-dvd1.iso from local CDROM
	2. Choose the installation option of the "Server with GUI" and  select all the components under Server with GUI
	3. After installation completed, click the reboot button that locate in the  lower right corner of the screen.
	4. Log in OS via by pressing the keyboard key F2 or via remote ssh.
	5. Check the message log, the following information will be displayed
	"Sep 17 03:34:11 localhost journal: Error setting up rfkill: Could not open RFKILL control device, please verify your installation"
Comment 22 Pavlin Georgiev 2019-09-17 13:27:02 UTC 
Created attachment 1615848 [details]
System journal from reproducing the bug under RHEL 7.7 x86_64 Server

TEST SETUP 5
Hardware: Dell Precision T5400
Distro: RHEL 7.7 x86_64 Server
Component version: gnome-settings-daemon-3.28.1-4.el7


TEST PROCEDURE 5
1. Download ISO file from:
   http://download.eng.brq.redhat.com/released/RHEL-7/7.7/Server/x86_64/iso/RHEL-7.7-20190723.1-Server-x86_64-dvd1.iso

2. Write the ISO to a USB drive.
3. Install RHEL 7.7 x86_64 server from USB drive.
4. After initial installation press "Reboot".
5. Finish the installation by accepting the license.
6. GDM starts. Do NOT log in.
7. Switch to TTY2 in text mode by pressing Ctrl+Alt+F2.
8. Log in as root.
9. Check the journal for the problem:
   # journalctl | grep -i rfkill
   The bug is not visible.
   
10. Return to GUI mode by pressing Ctrl+Alt+F1.
11. Log in a GNOME session as user "test".
12. Wait for the GNONE welcome splash screen to appear.
13. Switch to TTY2 in text mode by pressing Ctrl+Alt+F2.
14. Check the journal for the problem:
    # journalctl | grep -i rfkill
    The bug has appeared. I have reproduced the bug.
Comment 23 Pavlin Georgiev 2019-09-19 06:32:17 UTC 
Created attachment 1616573 [details]
System journal from reproducing the bug under RHEL-7.8-20190912.3 Server x86_64

TEST SETUP 6
Distro: RHEL-7.8-20190912.3 Server x86_64
Component version: gnome-settings-daemon-3.28.1-8.el7


TEST PROCEDURE 6
1. Download ISO file from:
   http://download.eng.rdu2.redhat.com/rel-eng/latest-RHEL-7/compose/Server/x86_64/iso/RHEL-7.8-20190912.3-Server-x86_64-dvd1.iso

2. Write the ISO to a USB drive.
3. Install RHEL 7.8 Server x86_64 from USB drive.
4. After initial installation press "Reboot".
5. Finish the installation by accepting the license.
6. GDM starts. Do NOT log in.
7. Switch to TTY2 in text mode by pressing Ctrl+Alt+F2.
8. Log in as root.
9. Check the journal for the problem:
   # journalctl | grep -i rfkill
   The bug is not visible.
   
10. Return to GUI mode by pressing Ctrl+Alt+F1.
11. Log in a GNOME session as user "test".
12. Wait for the GNONE welcome splash screen to appear.
13. Switch to TTY2 in text mode by pressing Ctrl+Alt+F2.
14. Check the journal for the problem:
    # journalctl | grep -i rfkill
    

RESULT 6
The bug does NOT appear.
Comment 24 Pavlin Georgiev 2019-09-19 06:33:38 UTC 
Upgrading component: gnome-settings-daemon
    from: 3.28.1-2.el7
      to: 3.28.1-8.el7
has fixed the bug.
Comment 29 errata-xmlrpc 2020-03-31 19:39:00 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1021
Note You need to log in before you can comment on or make changes to this bug.