Bug 1691197

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

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

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.

We have test the RHEL7.7 Alpha-1, the problem still exists.So need to upgrade the higher version of gnome-settings-daemon.

Is there any update for this defect？ I verified

Is there any update for this defect？ I have verified the 7.7 snapshot3， But the defect is still exist.

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

(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

(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

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.

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.

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.

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.

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"

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.

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.

Upgrading component: gnome-settings-daemon
    from: 3.28.1-2.el7
      to: 3.28.1-8.el7
has fixed the bug.

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