If I boot to 9.5 I have no WiFi services. 9.4 is working perfectly. Not sure where to even start with trouble shooting this.
Second issue… after messing about with KDE the machine no longer boots to Plymouth. I’ve been starting it with Cont Alt F2.
This is all getting tiresome. Especially when combined with a keyboard with fn duel purpose F keys. 
Not sure why the Plymouth issue is hard to resolve. I’ve spent hours on help files and trying options, including reinstall.
What wireless card is there? Is there any chance that installing some iwlxxx-firmware (or other wireless driver) will help? (You’ve probably already investigated that one, but every once in awhile it turns out to be the obvious thing that we overlooked, or assumed was already in place)
It’s a USB thing, bit no name brand. It’s worked for 9.4 and maybe 9.3.
I might not have done that fix. I tried a few things, I did get KDE to report correctly on the transfer rates.
I didn’t want to touch this until I’d had a chat. Starting with has anyone experienced this?
I don’t have a good understanding of what changes between 9.4 > 9.5, versioning in general. I’m guessing that changes beyond the kernel are minimal.
This is the log after removing and reinseting on 9.4 (works)
I’ll reboot and collect the 9.5 (not works)`14/12/24 1:15 PM systemd NetworkManager-dispatcher.service: Deactivated successfully.
14/12/24 1:15 PM ModemManager [base-manager] couldn’t check support for device ‘/sys/devices/pci0000:20/0000:20:03.2/0000:25:00.0/usb7/7-1/7-1.3’: not supported by any plugin
14/12/24 1:15 PM NetworkManager [1734146125.2176] policy: auto-activating connection ‘Yani’ (60b226e8-bf38-478a-ab34-40db05f264fe)
14/12/24 1:15 PM NetworkManager [1734146125.2182] device (wlp37s0u1u3i2): Activation: starting connection ‘Yani’ (60b226e8-bf38-478a-ab34-40db05f264fe)
14/12/24 1:15 PM NetworkManager [1734146125.2183] device (wlp37s0u1u3i2): state change: disconnected → prepare (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146125.2186] manager: NetworkManager state is now CONNECTING
14/12/24 1:15 PM NetworkManager [1734146125.2354] device (wlp37s0u1u3i2): set-hw-addr: reset MAC address to 90:DE:80:16:4F:77 (preserve)
14/12/24 1:15 PM NetworkManager [1734146125.7523] device (wlp37s0u1u3i2): state change: prepare → config (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146125.7526] device (wlp37s0u1u3i2): Activation: (wifi) access point ‘Yani’ has security, but secrets are required.
14/12/24 1:15 PM NetworkManager [1734146125.7526] device (wlp37s0u1u3i2): state change: config → need-auth (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146125.7531] device (wlp37s0u1u3i2): supplicant interface state: disconnected → interface_disabled
14/12/24 1:15 PM NetworkManager [1734146125.7543] device (wlp37s0u1u3i2): state change: need-auth → prepare (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146125.7547] device (wlp37s0u1u3i2): state change: prepare → config (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM kdeconnectd “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM NetworkManager [1734146125.7550] device (wlp37s0u1u3i2): Activation: (wifi) connection ‘Yani’ has security, and secrets exist. No new secrets needed.
14/12/24 1:15 PM NetworkManager [1734146125.7552] Config: added ‘ssid’ value ‘Yani’
14/12/24 1:15 PM NetworkManager [1734146125.7552] Config: added ‘scan_ssid’ value ‘1’
14/12/24 1:15 PM NetworkManager [1734146125.7552] Config: added ‘bgscan’ value ‘simple:30:-65:300’
14/12/24 1:15 PM NetworkManager [1734146125.7553] Config: added ‘key_mgmt’ value ‘WPA-PSK WPA-PSK-SHA256 SAE’
14/12/24 1:15 PM NetworkManager [1734146125.7553] Config: added ‘psk’ value ‘’
14/12/24 1:15 PM kgpg “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM kded5 “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM akonadi_sendlater_agent “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM DiscoverNotifier “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM akonadi_followupreminder_agent “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM akonadi_maildispatcher_agent “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM akonadi_mailmerge_agent “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM maliit-keyboard “Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2””
14/12/24 1:15 PM NetworkManager [1734146125.7571] device (wlp37s0u1u3i2): supplicant interface state: interface_disabled → inactive
14/12/24 1:15 PM kded5 kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property “VersionId”
14/12/24 1:15 PM plasmashell kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property “VersionId”
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: SME: Trying to authenticate with 46:64:7a:b5:22:ae (SSID=‘Yani’ freq=2412 MHz)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 80 MHz not supported, disabling VHT
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticate with 46:64:7a:b5:22:ae (local address=90:de:80:16:4f:77)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: send auth to 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM NetworkManager [1734146126.4534] device (wlp37s0u1u3i2): supplicant interface state: inactive → authenticating
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: Trying to associate with 46:64:7a:b5:22:ae (SSID=‘Yani’ freq=2412 MHz)
14/12/24 1:15 PM NetworkManager [1734146126.4575] device (wlp37s0u1u3i2): supplicant interface state: authenticating → associating
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticated
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: RX AssocResp from 46:64:7a:b5:22:ae (capab=0x431 status=30 aid=1)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 46:64:7a:b5:22:ae rejected association temporarily; comeback duration 1464 TU (1499 ms)
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@9.service: Deactivated successfully.
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@9.service: Consumed 1.063s CPU time.
14/12/24 1:15 PM systemd systemd-rfkill.service: Deactivated successfully.
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 2/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: RX AssocResp from 46:64:7a:b5:22:ae (capab=0x431 status=30 aid=1)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 46:64:7a:b5:22:ae rejected association temporarily; comeback duration 1464 TU (1499 ms)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 3/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: deauthenticated from 46:64:7a:b5:22:ae while associating (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-DISCONNECTED bssid=46:64:7a:b5:22:ae reason=6
14/12/24 1:15 PM NetworkManager [1734146129.5357] device (wlp37s0u1u3i2): supplicant interface state: associating → disconnected
14/12/24 1:15 PM NetworkManager [1734146130.1422] device (wlp37s0u1u3i2): supplicant interface state: disconnected → scanning
14/12/24 1:15 PM systemd setroubleshootd.service: Deactivated successfully.
14/12/24 1:15 PM systemd setroubleshootd.service: Consumed 4.120s CPU time.
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: SME: Trying to authenticate with 46:64:7a:b5:22:ae (SSID=‘Yani’ freq=2412 MHz)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 80 MHz not supported, disabling VHT
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticate with 46:64:7a:b5:22:ae (local address=90:de:80:16:4f:77)
14/12/24 1:15 PM NetworkManager [1734146131.7566] device (wlp37s0u1u3i2): supplicant interface state: scanning → authenticating
14/12/24 1:15 PM kernel wlp37s0u1u3i2: send auth to 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: Trying to associate with 46:64:7a:b5:22:ae (SSID=‘Yani’ freq=2412 MHz)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticated
14/12/24 1:15 PM NetworkManager [1734146131.7589] device (wlp37s0u1u3i2): supplicant interface state: authenticating → associating
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: RX AssocResp from 46:64:7a:b5:22:ae (capab=0x431 status=0 aid=1)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associated
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: Associated with 46:64:7a:b5:22:ae
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
14/12/24 1:15 PM NetworkManager [1734146131.7774] device (wlp37s0u1u3i2): supplicant interface state: associating → associated
14/12/24 1:15 PM kernel wlp37s0u1u3i2: Limiting TX power to 0 (-128 - 0) dBm as advertised by 46:64:7a:b5:22:ae
14/12/24 1:15 PM NetworkManager [1734146131.7991] device (wlp37s0u1u3i2): supplicant interface state: associated → 4way_handshake
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: WPA: Key negotiation completed with 46:64:7a:b5:22:ae [PTK=CCMP GTK=CCMP]
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-CONNECTED - Connection to 46:64:7a:b5:22:ae completed [id=0 id_str=]
14/12/24 1:15 PM kernel IPv6: ADDRCONF(NETDEV_CHANGE): wlp37s0u1u3i2: link becomes ready
14/12/24 1:15 PM NetworkManager [1734146131.8400] device (wlp37s0u1u3i2): supplicant interface state: 4way_handshake → completed
14/12/24 1:15 PM NetworkManager [1734146131.8401] device (wlp37s0u1u3i2): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network “Yani”
14/12/24 1:15 PM NetworkManager [1734146131.8429] device (wlp37s0u1u3i2): state change: config → ip-config (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146131.8436] dhcp4 (wlp37s0u1u3i2): activation: beginning transaction (timeout in 45 seconds)
14/12/24 1:15 PM avahi-daemon Joining mDNS multicast group on interface wlp37s0u1u3i2.IPv6 with address fe80::adca:889:e682:9900.
14/12/24 1:15 PM avahi-daemon New relevant interface wlp37s0u1u3i2.IPv6 for mDNS.
14/12/24 1:15 PM avahi-daemon Registering new address record for fe80::adca:889:e682:9900 on wlp37s0u1u3i2..
14/12/24 1:15 PM NetworkManager [1734146131.8644] dhcp4 (wlp37s0u1u3i2): state changed new lease, address=192.168.72.202
14/12/24 1:15 PM NetworkManager [1734146131.8647] policy: set ‘Yani’ (wlp37s0u1u3i2) as default for IPv4 routing and DNS
14/12/24 1:15 PM NetworkManager [1734146131.8794] dns-mgr: could not commit DNS changes: Failed to rename file “/etc/resolv.conf.W6CBY2” to “/etc/resolv.conf”: g_rename() failed: Permission denied
14/12/24 1:15 PM avahi-daemon Joining mDNS multicast group on interface wlp37s0u1u3i2.IPv4 with address 192.168.72.202.
14/12/24 1:15 PM avahi-daemon New relevant interface wlp37s0u1u3i2.IPv4 for mDNS.
14/12/24 1:15 PM avahi-daemon Registering new address record for 192.168.72.202 on wlp37s0u1u3i2.IPv4.
14/12/24 1:15 PM NetworkManager [1734146131.8919] device (wlp37s0u1u3i2): state change: ip-config → ip-check (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM systemd Starting SETroubleshoot daemon for processing new SELinux denial logs…
14/12/24 1:15 PM systemd Starting Network Manager Script Dispatcher Service…
14/12/24 1:15 PM systemd Started Network Manager Script Dispatcher Service.
14/12/24 1:15 PM NetworkManager [1734146131.9131] device (wlp37s0u1u3i2): state change: ip-check → secondaries (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146131.9134] device (wlp37s0u1u3i2): state change: secondaries → activated (reason ‘none’, sys-iface-state: ‘managed’)
14/12/24 1:15 PM NetworkManager [1734146131.9138] manager: NetworkManager state is now CONNECTED_SITE
14/12/24 1:15 PM NetworkManager [1734146131.9143] device (wlp37s0u1u3i2): Activation: successful, device activated.
14/12/24 1:15 PM NetworkManager [1734146131.9150] manager: NetworkManager state is now CONNECTED_GLOBAL
14/12/24 1:15 PM chronyd Source 162.159.200.1 online
14/12/24 1:15 PM chronyd Source 13.55.50.68 online
14/12/24 1:15 PM chronyd Source 194.195.249.28 online
14/12/24 1:15 PM chronyd Source 162.159.200.123 online
14/12/24 1:15 PM plasmashell Could not find the Plasmoid for Plasma::FrameSvgItem(0x7f6e1c030680) QQmlContext(0x55fc130f22f0) QUrl(“file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml”)
14/12/24 1:15 PM plasmashell Could not find the Plasmoid for Plasma::FrameSvgItem(0x7f6e1c030680) QQmlContext(0x55fc130f22f0) QUrl(“file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml”)
14/12/24 1:15 PM systemd Reloading Login and scanning of iSCSI devices…
14/12/24 1:15 PM iscsiadm iscsiadm: No records found
14/12/24 1:15 PM systemd Reloaded Login and scanning of iSCSI devices.
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=6500
14/12/24 1:15 PM systemd Started SETroubleshoot daemon for processing new SELinux denial logs.
14/12/24 1:15 PM chronyd Selected source 162.159.200.1 (2.rocky.pool.ntp.org)
14/12/24 1:15 PM setroubleshoot failed to retrieve rpm info for path ‘/etc/resolv.conf’:
14/12/24 1:15 PM systemd Started dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@10.service.
14/12/24 1:15 PM NetworkManager [1734146133.4669] policy: set ‘Yani’ (wlp37s0u1u3i2) as default for IPv6 routing and DNS
14/12/24 1:15 PM NetworkManager [1734146133.4739] dns-mgr: could not commit DNS changes: Failed to rename file “/etc/resolv.conf.LHHPY2” to “/etc/resolv.conf”: g_rename() failed: Permission denied
14/12/24 1:15 PM avahi-daemon Leaving mDNS multicast group on interface wlp37s0u1u3i2.IPv6 with address fe80::adca:889:e682:9900.
14/12/24 1:15 PM avahi-daemon Joining mDNS multicast group on interface wlp37s0u1u3i2.IPv6 with address 2001:8004:2768:164a:2214:569a:1375:3cbc.
14/12/24 1:15 PM avahi-daemon Registering new address record for 2001:8004:2768:164a:2214:569a:1375:3cbc on wlp37s0u1u3i2..
14/12/24 1:15 PM avahi-daemon Withdrawing address record for fe80::adca:889:e682:9900 on wlp37s0u1u3i2.
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf. For complete SELinux messages run: sealert -l 4cc3ab13-3fb6-429c-9acd-903880f9a41f
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf.
***** Plugin restorecon (94.8 confidence) suggests ************************
If you want to fix the label.
/etc/resolv.conf default label should be net_conf_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
Do
***** Plugin catchall_labels (5.21 confidence) suggests *******************
If you want to allow NetworkManager to have unlink access on the resolv.conf file
Then you need to change the label on /etc/resolv.conf
Do
where FILE_TYPE is one of the following: NetworkManager_etc_rw_t, NetworkManager_tmp_t, NetworkManager_var_lib_t, NetworkManager_var_run_t, dhcpc_state_t, dhcpc_var_run_t, dnsmasq_var_run_t, hostname_etc_t, krb5_host_rcache_t, named_cache_t, net_conf_t, pppd_var_run_t, ssh_home_t, systemd_passwd_var_run_t.
Then execute:
restorecon -v ‘/etc/resolv.conf’
***** Plugin catchall (1.44 confidence) suggests **************************
If you believe that NetworkManager should be allowed unlink access on the resolv.conf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf. For complete SELinux messages run: sealert -l 4cc3ab13-3fb6-429c-9acd-903880f9a41f
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf.
***** Plugin restorecon (94.8 confidence) suggests ************************
If you want to fix the label.
/etc/resolv.conf default label should be net_conf_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
Do
***** Plugin catchall_labels (5.21 confidence) suggests *******************
If you want to allow NetworkManager to have unlink access on the resolv.conf file
Then you need to change the label on /etc/resolv.conf
Do
where FILE_TYPE is one of the following: NetworkManager_etc_rw_t, NetworkManager_tmp_t, NetworkManager_var_lib_t, NetworkManager_var_run_t, dhcpc_state_t, dhcpc_var_run_t, dnsmasq_var_run_t, hostname_etc_t, krb5_host_rcache_t, named_cache_t, net_conf_t, pppd_var_run_t, ssh_home_t, systemd_passwd_var_run_t.
Then execute:
restorecon -v ‘/etc/resolv.conf’
***** Plugin catchall (1.44 confidence) suggests **************************
If you believe that NetworkManager should be allowed unlink access on the resolv.conf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
14/12/24 1:15 PM systemd NetworkManager-dispatcher.service: Deactivated successfully.
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@10.service: Deactivated successfully.
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@10.service: Consumed 1.120s CPU time.
14/12/24 1:15 PM systemd setroubleshootd.service: Deactivated successfully.
14/12/24 1:15 PM systemd setroubleshootd.service: Consumed 6.643s CPU time.
`
9.5 the failing version
| 14/12/24 1:22 PM | systemd | Finished KSplash ready Stage. |
|---|---|---|
| 14/12/24 1:22 PM | plasma_waitforname | org.kde.knotifications: WaitForName: Service was not registered within timeout |
| 14/12/24 1:22 PM | systemd | dbus-:1.2-org.kde.KSplash@0.service: Main process exited, code=exited, status=1/FAILURE |
| 14/12/24 1:22 PM | systemd | dbus-:1.2-org.kde.KSplash@0.service: Failed with result ‘exit-code’. |
| 14/12/24 1:22 PM | systemd | virtqemud.service: Deactivated successfully. |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: USB disconnect, device number 4 |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/ldac |
| 14/12/24 1:23 PM | systemd | Starting Load/Save RF Kill Switch Status… |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSink/aac |
| 14/12/24 1:23 PM | systemd | Stopped target Bluetooth Support. |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/aac |
| 14/12/24 1:23 PM | systemd | Started Load/Save RF Kill Switch Status. |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSink/sbc |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/sbc |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSink/sbc_xq |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/sbc_xq |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/faststream |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/faststream_duplex |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSink/opus_05 |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/opus_05 |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSink/opus_05_duplex |
| 14/12/24 1:23 PM | bluetoothd | Endpoint unregistered: sender=:1.63 path=/MediaEndpoint/A2DPSource/opus_05_duplex |
| 14/12/24 1:23 PM | bluetoothd | Battery Provider Manager destroyed |
| 14/12/24 1:23 PM | systemd | fprintd.service: Deactivated successfully. |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: new high-speed USB device number 5 using xhci_hcd |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: New USB device found, idVendor=0bda, idProduct=d723, bcdDevice= 2.00 |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: Product: 802.11n WLAN Adapter |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: Manufacturer: Realtek |
| 14/12/24 1:23 PM | kernel | usb 7-1.3: SerialNumber: 00e04c000001 |
| 14/12/24 1:23 PM | systemd | systemd-rfkill.service: Deactivated successfully. |
| 14/12/24 1:23 PM | kernel | Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000d lmp_ver=08 lmp_subver=8723 |
| 14/12/24 1:23 PM | kernel | Bluetooth: hci0: RTL: rom_version status=0 version=2 |
| 14/12/24 1:23 PM | kernel | Bluetooth: hci0: RTL: loading rtl_bt/rtl8723d_fw.bin |
| 14/12/24 1:23 PM | mtp-probe | checking bus 7, device 5: /sys/devices/pci0000:20/0000:20:03.2/0000:25:00.0/usb7/7-1/7-1.3 |
| 14/12/24 1:23 PM | kernel | Bluetooth: hci0: RTL: loading rtl_bt/rtl8723d_config.bin |
| 14/12/24 1:23 PM | kernel | Bluetooth: hci0: RTL: cfg_sz 10, total sz 33266 |
| 14/12/24 1:23 PM | systemd | Starting Load/Save RF Kill Switch Status… |
| 14/12/24 1:23 PM | mtp-probe | bus: 7, device: 5 was not an MTP device |
| 14/12/24 1:23 PM | upower.service | treating change event as add on /sys/devices/pci0000:20/0000:20:03.2/0000:25:00.0/usb7/7-1/7-1.3 |
| 14/12/24 1:23 PM | systemd | Reached target Bluetooth. |
| 14/12/24 1:23 PM | systemd | Started Load/Save RF Kill Switch Status. |
| 14/12/24 1:23 PM | systemd | Reached target Bluetooth Support. |
| 14/12/24 1:23 PM | mtp-probe | checking bus 7, device 5: /sys/devices/pci0000:20/0000:20:03.2/0000:25:00.0/usb7/7-1/7-1.3 |
| 14/12/24 1:23 PM | mtp-probe | bus: 7, device: 5 was not an MTP device |
| 14/12/24 1:23 PM | kernel | Bluetooth: hci0: RTL: fw version 0x828a96f1 |
| 14/12/24 1:23 PM | kernel | Bluetooth: MGMT ver 1.22 |
| 14/12/24 1:23 PM | bluetoothd | Battery Provider Manager created |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/ldac |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSink/aac |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/aac |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSink/sbc |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/sbc |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSink/sbc_xq |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/sbc_xq |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/faststream |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/faststream_duplex |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSink/opus_05 |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/opus_05 |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSink/opus_05_duplex |
| 14/12/24 1:23 PM | bluetoothd | Endpoint registered: sender=:1.63 path=/MediaEndpoint/A2DPSource/opus_05_duplex |
| 14/12/24 1:23 PM | bluetoothd | src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down |
| 14/12/24 1:23 PM | systemd | systemd-rfkill.service: Deactivated successfully. |
Damned if I know how I fluked that formatting.
Working version 9.4
14/12/24 1:15 PM systemd NetworkManager-dispatcher.service: Deactivated successfully.
14/12/24 1:15 PM ModemManager <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:20/0000:20:03.2/0000:25:00.0/usb7/7-1/7-1.3': not supported by any plugin
14/12/24 1:15 PM NetworkManager <info> [1734146125.2176] policy: auto-activating connection 'Yani' (60b226e8-bf38-478a-ab34-40db05f264fe)
14/12/24 1:15 PM NetworkManager <info> [1734146125.2182] device (wlp37s0u1u3i2): Activation: starting connection 'Yani' (60b226e8-bf38-478a-ab34-40db05f264fe)
14/12/24 1:15 PM NetworkManager <info> [1734146125.2183] device (wlp37s0u1u3i2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146125.2186] manager: NetworkManager state is now CONNECTING
14/12/24 1:15 PM NetworkManager <info> [1734146125.2354] device (wlp37s0u1u3i2): set-hw-addr: reset MAC address to 90:DE:80:16:4F:77 (preserve)
14/12/24 1:15 PM NetworkManager <info> [1734146125.7523] device (wlp37s0u1u3i2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146125.7526] device (wlp37s0u1u3i2): Activation: (wifi) access point 'Yani' has security, but secrets are required.
14/12/24 1:15 PM NetworkManager <info> [1734146125.7526] device (wlp37s0u1u3i2): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146125.7531] device (wlp37s0u1u3i2): supplicant interface state: disconnected -> interface_disabled
14/12/24 1:15 PM NetworkManager <info> [1734146125.7543] device (wlp37s0u1u3i2): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146125.7547] device (wlp37s0u1u3i2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM kdeconnectd "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM NetworkManager <info> [1734146125.7550] device (wlp37s0u1u3i2): Activation: (wifi) connection 'Yani' has security, and secrets exist. No new secrets needed.
14/12/24 1:15 PM NetworkManager <info> [1734146125.7552] Config: added 'ssid' value 'Yani'
14/12/24 1:15 PM NetworkManager <info> [1734146125.7552] Config: added 'scan_ssid' value '1'
14/12/24 1:15 PM NetworkManager <info> [1734146125.7552] Config: added 'bgscan' value 'simple:30:-65:300'
14/12/24 1:15 PM NetworkManager <info> [1734146125.7553] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 SAE'
14/12/24 1:15 PM NetworkManager <info> [1734146125.7553] Config: added 'psk' value '<hidden>'
14/12/24 1:15 PM kgpg "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM kded5 "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM akonadi_sendlater_agent "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM DiscoverNotifier "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM akonadi_followupreminder_agent "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM akonadi_maildispatcher_agent "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM akonadi_mailmerge_agent "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM maliit-keyboard "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/2”"
14/12/24 1:15 PM NetworkManager <info> [1734146125.7571] device (wlp37s0u1u3i2): supplicant interface state: interface_disabled -> inactive
14/12/24 1:15 PM kded5 kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
14/12/24 1:15 PM plasmashell kf.networkmanagerqt: void NetworkManager::ConnectionPrivate::onPropertiesChanged(const QVariantMap&) Unhandled property "VersionId"
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: SME: Trying to authenticate with 46:64:7a:b5:22:ae (SSID='Yani' freq=2412 MHz)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 80 MHz not supported, disabling VHT
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticate with 46:64:7a:b5:22:ae (local address=90:de:80:16:4f:77)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: send auth to 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM NetworkManager <info> [1734146126.4534] device (wlp37s0u1u3i2): supplicant interface state: inactive -> authenticating
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: Trying to associate with 46:64:7a:b5:22:ae (SSID='Yani' freq=2412 MHz)
14/12/24 1:15 PM NetworkManager <info> [1734146126.4575] device (wlp37s0u1u3i2): supplicant interface state: authenticating -> associating
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticated
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: RX AssocResp from 46:64:7a:b5:22:ae (capab=0x431 status=30 aid=1)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 46:64:7a:b5:22:ae rejected association temporarily; comeback duration 1464 TU (1499 ms)
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@9.service: Deactivated successfully.
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@9.service: Consumed 1.063s CPU time.
14/12/24 1:15 PM systemd systemd-rfkill.service: Deactivated successfully.
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 2/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: RX AssocResp from 46:64:7a:b5:22:ae (capab=0x431 status=30 aid=1)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 46:64:7a:b5:22:ae rejected association temporarily; comeback duration 1464 TU (1499 ms)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 3/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: deauthenticated from 46:64:7a:b5:22:ae while associating (Reason: 6=CLASS2_FRAME_FROM_NONAUTH_STA)
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-DISCONNECTED bssid=46:64:7a:b5:22:ae reason=6
14/12/24 1:15 PM NetworkManager <info> [1734146129.5357] device (wlp37s0u1u3i2): supplicant interface state: associating -> disconnected
14/12/24 1:15 PM NetworkManager <info> [1734146130.1422] device (wlp37s0u1u3i2): supplicant interface state: disconnected -> scanning
14/12/24 1:15 PM systemd setroubleshootd.service: Deactivated successfully.
14/12/24 1:15 PM systemd setroubleshootd.service: Consumed 4.120s CPU time.
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: SME: Trying to authenticate with 46:64:7a:b5:22:ae (SSID='Yani' freq=2412 MHz)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: 80 MHz not supported, disabling VHT
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticate with 46:64:7a:b5:22:ae (local address=90:de:80:16:4f:77)
14/12/24 1:15 PM NetworkManager <info> [1734146131.7566] device (wlp37s0u1u3i2): supplicant interface state: scanning -> authenticating
14/12/24 1:15 PM kernel wlp37s0u1u3i2: send auth to 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: Trying to associate with 46:64:7a:b5:22:ae (SSID='Yani' freq=2412 MHz)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: authenticated
14/12/24 1:15 PM NetworkManager <info> [1734146131.7589] device (wlp37s0u1u3i2): supplicant interface state: authenticating -> associating
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associate with 46:64:7a:b5:22:ae (try 1/3)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: RX AssocResp from 46:64:7a:b5:22:ae (capab=0x431 status=0 aid=1)
14/12/24 1:15 PM kernel wlp37s0u1u3i2: associated
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: Associated with 46:64:7a:b5:22:ae
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
14/12/24 1:15 PM NetworkManager <info> [1734146131.7774] device (wlp37s0u1u3i2): supplicant interface state: associating -> associated
14/12/24 1:15 PM kernel wlp37s0u1u3i2: Limiting TX power to 0 (-128 - 0) dBm as advertised by 46:64:7a:b5:22:ae
14/12/24 1:15 PM NetworkManager <info> [1734146131.7991] device (wlp37s0u1u3i2): supplicant interface state: associated -> 4way_handshake
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: WPA: Key negotiation completed with 46:64:7a:b5:22:ae [PTK=CCMP GTK=CCMP]
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-CONNECTED - Connection to 46:64:7a:b5:22:ae completed [id=0 id_str=]
14/12/24 1:15 PM kernel IPv6: ADDRCONF(NETDEV_CHANGE): wlp37s0u1u3i2: link becomes ready
14/12/24 1:15 PM NetworkManager <info> [1734146131.8400] device (wlp37s0u1u3i2): supplicant interface state: 4way_handshake -> completed
14/12/24 1:15 PM NetworkManager <info> [1734146131.8401] device (wlp37s0u1u3i2): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Yani"
14/12/24 1:15 PM NetworkManager <info> [1734146131.8429] device (wlp37s0u1u3i2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146131.8436] dhcp4 (wlp37s0u1u3i2): activation: beginning transaction (timeout in 45 seconds)
14/12/24 1:15 PM avahi-daemon Joining mDNS multicast group on interface wlp37s0u1u3i2.IPv6 with address fe80::adca:889:e682:9900.
14/12/24 1:15 PM avahi-daemon New relevant interface wlp37s0u1u3i2.IPv6 for mDNS.
14/12/24 1:15 PM avahi-daemon Registering new address record for fe80::adca:889:e682:9900 on wlp37s0u1u3i2.*.
14/12/24 1:15 PM NetworkManager <info> [1734146131.8644] dhcp4 (wlp37s0u1u3i2): state changed new lease, address=192.168.72.202
14/12/24 1:15 PM NetworkManager <info> [1734146131.8647] policy: set 'Yani' (wlp37s0u1u3i2) as default for IPv4 routing and DNS
14/12/24 1:15 PM NetworkManager <warn> [1734146131.8794] dns-mgr: could not commit DNS changes: Failed to rename file “/etc/resolv.conf.W6CBY2” to “/etc/resolv.conf”: g_rename() failed: Permission denied
14/12/24 1:15 PM avahi-daemon Joining mDNS multicast group on interface wlp37s0u1u3i2.IPv4 with address 192.168.72.202.
14/12/24 1:15 PM avahi-daemon New relevant interface wlp37s0u1u3i2.IPv4 for mDNS.
14/12/24 1:15 PM avahi-daemon Registering new address record for 192.168.72.202 on wlp37s0u1u3i2.IPv4.
14/12/24 1:15 PM NetworkManager <info> [1734146131.8919] device (wlp37s0u1u3i2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM systemd Starting SETroubleshoot daemon for processing new SELinux denial logs...
14/12/24 1:15 PM systemd Starting Network Manager Script Dispatcher Service...
14/12/24 1:15 PM systemd Started Network Manager Script Dispatcher Service.
14/12/24 1:15 PM NetworkManager <info> [1734146131.9131] device (wlp37s0u1u3i2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146131.9134] device (wlp37s0u1u3i2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
14/12/24 1:15 PM NetworkManager <info> [1734146131.9138] manager: NetworkManager state is now CONNECTED_SITE
14/12/24 1:15 PM NetworkManager <info> [1734146131.9143] device (wlp37s0u1u3i2): Activation: successful, device activated.
14/12/24 1:15 PM NetworkManager <info> [1734146131.9150] manager: NetworkManager state is now CONNECTED_GLOBAL
14/12/24 1:15 PM chronyd Source 162.159.200.1 online
14/12/24 1:15 PM chronyd Source 13.55.50.68 online
14/12/24 1:15 PM chronyd Source 194.195.249.28 online
14/12/24 1:15 PM chronyd Source 162.159.200.123 online
14/12/24 1:15 PM plasmashell Could not find the Plasmoid for Plasma::FrameSvgItem(0x7f6e1c030680) QQmlContext(0x55fc130f22f0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
14/12/24 1:15 PM plasmashell Could not find the Plasmoid for Plasma::FrameSvgItem(0x7f6e1c030680) QQmlContext(0x55fc130f22f0) QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml")
14/12/24 1:15 PM systemd Reloading Login and scanning of iSCSI devices...
14/12/24 1:15 PM iscsiadm iscsiadm: No records found
14/12/24 1:15 PM systemd Reloaded Login and scanning of iSCSI devices.
14/12/24 1:15 PM wpa_supplicant wlp37s0u1u3i2: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=6500
14/12/24 1:15 PM systemd Started SETroubleshoot daemon for processing new SELinux denial logs.
14/12/24 1:15 PM chronyd Selected source 162.159.200.1 (2.rocky.pool.ntp.org)
14/12/24 1:15 PM setroubleshoot failed to retrieve rpm info for path '/etc/resolv.conf':
14/12/24 1:15 PM systemd Started dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@10.service.
14/12/24 1:15 PM NetworkManager <info> [1734146133.4669] policy: set 'Yani' (wlp37s0u1u3i2) as default for IPv6 routing and DNS
14/12/24 1:15 PM NetworkManager <warn> [1734146133.4739] dns-mgr: could not commit DNS changes: Failed to rename file “/etc/resolv.conf.LHHPY2” to “/etc/resolv.conf”: g_rename() failed: Permission denied
14/12/24 1:15 PM avahi-daemon Leaving mDNS multicast group on interface wlp37s0u1u3i2.IPv6 with address fe80::adca:889:e682:9900.
14/12/24 1:15 PM avahi-daemon Joining mDNS multicast group on interface wlp37s0u1u3i2.IPv6 with address 2001:8004:2768:164a:2214:569a:1375:3cbc.
14/12/24 1:15 PM avahi-daemon Registering new address record for 2001:8004:2768:164a:2214:569a:1375:3cbc on wlp37s0u1u3i2.*.
14/12/24 1:15 PM avahi-daemon Withdrawing address record for fe80::adca:889:e682:9900 on wlp37s0u1u3i2.
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf. For complete SELinux messages run: sealert -l 4cc3ab13-3fb6-429c-9acd-903880f9a41f
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf.
***** Plugin restorecon (94.8 confidence) suggests ************************
If you want to fix the label.
/etc/resolv.conf default label should be net_conf_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
Do
# /sbin/restorecon -v /etc/resolv.conf
***** Plugin catchall_labels (5.21 confidence) suggests *******************
If you want to allow NetworkManager to have unlink access on the resolv.conf file
Then you need to change the label on /etc/resolv.conf
Do
# semanage fcontext -a -t FILE_TYPE '/etc/resolv.conf'
where FILE_TYPE is one of the following: NetworkManager_etc_rw_t, NetworkManager_tmp_t, NetworkManager_var_lib_t, NetworkManager_var_run_t, dhcpc_state_t, dhcpc_var_run_t, dnsmasq_var_run_t, hostname_etc_t, krb5_host_rcache_t, named_cache_t, net_conf_t, pppd_var_run_t, ssh_home_t, systemd_passwd_var_run_t.
Then execute:
restorecon -v '/etc/resolv.conf'
***** Plugin catchall (1.44 confidence) suggests **************************
If you believe that NetworkManager should be allowed unlink access on the resolv.conf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'NetworkManager' --raw | audit2allow -M my-NetworkManager
# semodule -X 300 -i my-NetworkManager.pp
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf. For complete SELinux messages run: sealert -l 4cc3ab13-3fb6-429c-9acd-903880f9a41f
14/12/24 1:15 PM setroubleshoot SELinux is preventing /usr/sbin/NetworkManager from unlink access on the file /etc/resolv.conf.
***** Plugin restorecon (94.8 confidence) suggests ************************
If you want to fix the label.
/etc/resolv.conf default label should be net_conf_t.
Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly.
Do
# /sbin/restorecon -v /etc/resolv.conf
***** Plugin catchall_labels (5.21 confidence) suggests *******************
If you want to allow NetworkManager to have unlink access on the resolv.conf file
Then you need to change the label on /etc/resolv.conf
Do
# semanage fcontext -a -t FILE_TYPE '/etc/resolv.conf'
where FILE_TYPE is one of the following: NetworkManager_etc_rw_t, NetworkManager_tmp_t, NetworkManager_var_lib_t, NetworkManager_var_run_t, dhcpc_state_t, dhcpc_var_run_t, dnsmasq_var_run_t, hostname_etc_t, krb5_host_rcache_t, named_cache_t, net_conf_t, pppd_var_run_t, ssh_home_t, systemd_passwd_var_run_t.
Then execute:
restorecon -v '/etc/resolv.conf'
***** Plugin catchall (1.44 confidence) suggests **************************
If you believe that NetworkManager should be allowed unlink access on the resolv.conf file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'NetworkManager' --raw | audit2allow -M my-NetworkManager
# semodule -X 300 -i my-NetworkManager.pp
14/12/24 1:15 PM systemd NetworkManager-dispatcher.service: Deactivated successfully.
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@10.service: Deactivated successfully.
14/12/24 1:15 PM systemd dbus-:1.1-org.fedoraproject.SetroubleshootPrivileged@10.service: Consumed 1.120s CPU time.
14/12/24 1:15 PM systemd setroubleshootd.service: Deactivated successfully.
14/12/24 1:15 PM systemd setroubleshootd.service: Consumed 6.643s CPU time.
You can try lspci |grep -i network and see if it shows a network controller like intel or Realtek something. (A lot of those cheap USB things are Realtek). If it shows something, that might give you an idea of what to search for. Or, put the result into a web search like rocky driver for and see if there’s an rpm for it. As is probably obvious, I’m no expert, but the few times my wireless hasn’t worked, this is the sort of thing I’d do to find what I needed.
Or, if possible, try another cheap adapter and see if it’s recognized. Hopefully, someone with more knowledge will step in.
For an experiment, I primed ChatGPTi and then fed it the logs.
We might see some advantages from code that is Open Source that aren’t possible in the closed door world?
GPT
It looks like you’re dealing with logs from your system that include information about:
KSplash Error:
org.kde.knotifications: WaitForName: Service was not registered within timeout
Failure with dbus-:1.2-org.kde.KSplash@0.service.
This suggests an issue with KDE Plasma's splash screen system. It might be related to a misconfiguration in Plasma or a timing issue with DBus services starting up.
Bluetooth Device Management:
A series of events indicate that Bluetooth endpoints and services were unregistered and then re-registered.
This suggests a Bluetooth reset, possibly due to the device being reconnected or a driver reset.
Specific logs about loading firmware for a Realtek chip (rtl8723d) suggest your Bluetooth is tied to this hardware.
USB WLAN Adapter:
A Realtek 802.11n WLAN Adapter was detected and initialized.
If this reinitialization was unintended, it could indicate intermittent USB power cycling or driver behavior.
System Services:
fprintd.service and systemd-rfkill.service deactivations are normal unless you rely on these for functionality (e.g., fingerprint authentication or RF Kill switch state preservation).
Suggestions:
KSplash Issue:
Check if the system is trying to start an unneeded or misconfigured KSplash theme.
Use journalctl -u plasmashell or similar to investigate further.
If issues persist, try resetting Plasma's cache:
rm -rf ~/.cache/*
Bluetooth:
Ensure the firmware files for the Realtek chip (rtl8723d) are correctly installed. These are often part of the linux-firmware package.
Monitor power management settings for the adapter; aggressive power-saving might cause resets.
USB Stability:
Check USB power settings:
cat /sys/module/usbcore/parameters/autosuspend
If it’s causing issues, disable autosuspend:
echo -1 | sudo tee /sys/module/usbcore/parameters/autosuspend
General:
Use journalctl or KDE’s systemsettings5 logs section to dig deeper into any persistent misconfigurations.
If running multiple VMs, check whether device passthrough might be affecting Bluetooth or USB behaviors.
Let me know if you’d like detailed commands or further steps!