Did you install any other packages that “improved” your security then? Because this is definitely a hardware address change:
and that doesn’t happen all by itself.
So dig down in your computer settings what you installed and remove that piece of … erm… software!
This started happening after the big update on 31st Dec. My GPU configuration got screwed, and this happened. While the GPU thing was resolved, this is still there. And I’m not sure why it’s happening, or even where to start looking.
I’m sad to tell you that from this point forward I’ll be utterly and totally useless to you…
My apologies!
P.S. I’ve added the wifi tag to your question to get smarter people then me involved…
I can only point you in the right direction. If what you say about this fault occurring after an update is true then boot into the live USB (install to RAM) and verify it. If it works, then you can proceed to compare the two environments to see what differs in terms of configuration and also operational behaviour (logs).
Device-2: Intel Wireless 7265 driver: iwlwifi
See arch wiki wifi troubleshooting guide:
https://wiki.archlinux.org/index.php/Network_configuration/Wireless#Observing_logs
https://wiki.archlinux.org/index.php/Network_configuration/Wireless#iwlwifi
See arch wiki power saving guide:
https://wiki.archlinux.org/index.php/Power_saving#Network_interfaces
Thanks. I’ll try it out. It also struck me that the update installed 5.10 kernel for the first time. I always thought that this was some rogue config file doing its thing but I’ll still go back to 5.4 and check.
For totally disabling MAC Address Randomization, I have done the following, since I encountered a similar issue (very low reconnection on resume)
Made the config file /etc/NetworkManager/conf.d/90-disable-randomization.conf
With the following content:
[device-mac-randomization]
wifi.scan-rand-mac-address=no
[connection-mac-randomization]
## FOR ETHERNET, OPTIONAL IF YOU USE ONLY WLAN
#ethernet.cloned-mac-address=permanent
wifi.cloned-mac-address=permanent
Then restart NetworkManager.service:
systemctl restart NetworkManager.service
I had to reboot, but it worked. Thanks!
You’re welcome! I’m glad for you🙂
It’s happening again. But this time only every other boot (no idea how that’s even possible). Here’s output from journalctl around Lid open:
Feb 24 15:17:19 sintan-pc kernel: wlo1: deauthenticating from 10:be:f5:fe:1e:ee by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Interface wlo1.IPv6 no longer relevant for mDNS.
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::783a:5845:4bbe:83e8.
Feb 24 15:17:19 sintan-pc dhcpcd[475]: wlo1: carrier lost
Feb 24 15:17:19 sintan-pc wpa_supplicant[582]: wlo1: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Interface wlo1.IPv4 no longer relevant for mDNS.
Feb 24 15:17:19 sintan-pc wpa_supplicant[582]: wlo1: CTRL-EVENT-DISCONNECTED bssid=10:be:f5:fe:1e:ee reason=3 locally_generated=1
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.0.2.
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Withdrawing address record for fe80::a60f:1d73:17d0:3a98 on wlo1.
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Withdrawing address record for fe80::783a:5845:4bbe:83e8 on wlo1.
Feb 24 15:17:19 sintan-pc avahi-daemon[462]: Withdrawing address record for 192.168.0.2 on wlo1.
Feb 24 15:17:19 sintan-pc wpa_supplicant[582]: rfkill: WLAN soft blocked
Feb 24 15:17:19 sintan-pc wpa_supplicant[582]: rfkill: WLAN soft blocked
Feb 24 15:17:20 sintan-pc NetworkManager[467]: <info> [1614160040.0000] manager: rfkill: Wi-Fi now disabled by radio killswitch
Feb 24 15:17:20 sintan-pc NetworkManager[467]: <info> [1614160040.0004] device (wlo1): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Feb 24 15:17:20 sintan-pc NetworkManager[467]: <info> [1614160040.0120] dhcp4 (wlo1): canceled DHCP transaction
Feb 24 15:17:20 sintan-pc NetworkManager[467]: <info> [1614160040.0121] dhcp4 (wlo1): state changed bound -> done
Feb 24 15:17:20 sintan-pc NetworkManager[467]: <info> [1614160040.0201] manager: NetworkManager state is now DISCONNECTED
Feb 24 15:17:20 sintan-pc NetworkManager[467]: <info> [1614160040.0278] device (p2p-dev-wlo1): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
Feb 24 15:17:20 sintan-pc dhcpcd[475]: wlo1: deleting address fe80::a60f:1d73:17d0:3a98
Feb 24 15:17:20 sintan-pc dhcpcd[475]: wlo1: deleting route to 192.168.0.0/24
Feb 24 15:17:20 sintan-pc dhcpcd[475]: wlo1: deleting default route via 192.168.0.1
Feb 24 15:17:20 sintan-pc wpa_supplicant[582]: nl80211: deinit ifname=p2p-dev-wlo1 disabled_11b_rates=0
Feb 24 15:17:20 sintan-pc dbus-daemon[466]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=467 comm="/usr/bin/NetworkManager --no-daemon ")
Feb 24 15:17:20 sintan-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit NetworkManager-dispatcher.service has begun execution.
░░
░░ The job identifier is 2370.
Feb 24 15:17:20 sintan-pc syncthingtray[1129]: QNetworkReplyImplPrivate::error: Internal problem, this method must only be called once.
Feb 24 15:17:20 sintan-pc dbus-daemon[466]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Feb 24 15:17:20 sintan-pc systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░
░░ The job identifier is 2370.
Feb 24 15:17:20 sintan-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 15:17:20 sintan-pc kernel: audit: type=1130 audit(1614160040.093:110): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 15:17:20 sintan-pc wpa_supplicant[582]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Feb 24 15:17:20 sintan-pc systemd-logind[471]: Lid opened.
Feb 24 15:17:20 sintan-pc avahi-daemon[462]: Got SIGHUP, reloading.
Feb 24 15:17:20 sintan-pc avahi-daemon[462]: No service file found in /etc/avahi/services.
Feb 24 15:17:20 sintan-pc plasmashell[1081]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationPopup.qml:116:15: QML QQuickItem: Binding loop detected for property "height"
Feb 24 15:17:23 sintan-pc audit[7339]: USER_AUTH pid=7339 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="sintan" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Feb 24 15:17:23 sintan-pc kernel: audit: type=1100 audit(1614160043.523:111): pid=7339 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="sintan" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Feb 24 15:17:23 sintan-pc kscreenlocker_greet[7088]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:27: TypeError: Cannot read property 'width' of null
Feb 24 15:17:23 sintan-pc kscreenlocker_greet[7088]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:45: TypeError: Cannot read property 'height' of null
Feb 24 15:17:23 sintan-pc kwin_x11[1004]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 58217, resource id: 4194362, major code: 18 (ChangeProperty), minor code: 0
Feb 24 15:17:25 sintan-pc kwin_x11[1004]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 60531, resource id: 41943447, major code: 15 (QueryTree), minor code: 0
Feb 24 15:17:30 sintan-pc systemd[1]: NetworkManager-dispatcher.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Feb 24 15:17:30 sintan-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 24 15:17:30 sintan-pc kernel: audit: type=1131 audit(1614160050.820:112): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Please help. @D.Dave
Do you have a dual boot with Windows?
If yes, don’t warm boot from Windows to Linux but cold boot.
You can still warm boot from Linux to Windows.
If that’s not it, let us know.
No. Manjaro is the only OS installed. But my laptop originally came with Windows preinstalled. I tried my best to remove it completely. But might it still be causing issues?
Nah, if you don’t load any Windows drivers, they can’t mess up your firmware…
Have you tried re-applying @D.Dave 's settings above?
(Maybe some package you installed fùcked messed it up again)
It’s still there. It works every other boot, so I don’t think that’s the issue.
No further bright ideas then… Sorry!
It got fixed after today’s (01/03/2021) update.
NEVER MIND, started again!
It could also indicate a break in the antenna in the hinge of the laptop lid - if it occurs again.
It’s happening.
But I don’t think it’s a hardware issue since it’s perfectly fine in some boots and causing issues in other boots. There are also no other connection issues.
I suggest testing my idea with a live stick . In this constellations, open lid, close it, open it, close it…and see what happens. You will report ?
Sure, I’ll do that tomorrow morning and let you know. Btw, since I’m testing hardware issues, it’s okay if I use XFCE instead of KDE, right? (I have one XFCE live image lying around that I made a week or so ago.)
@Manfrago I tried a live usb and it works perfectly. Here’s my journalctl output around lid closure and opening. It’s a bit different than was originally posted. I think @D.Dave 's suggestions had some kind of effect.
journalctl -xe -n 1000
Mar 04 15:56:31 sintan-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 04 15:56:31 sintan-pc kernel: kauditd_printk_skb: 13 callbacks suppressed
Mar 04 15:56:31 sintan-pc kernel: audit: type=1131 audit(1614853591.135:116): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 04 15:56:31 sintan-pc audit: BPF prog-id=10 op=UNLOAD
Mar 04 15:56:31 sintan-pc audit: BPF prog-id=9 op=UNLOAD
Mar 04 15:56:31 sintan-pc kernel: audit: type=1334 audit(1614853591.244:117): prog-id=10 op=UNLOAD
Mar 04 15:56:31 sintan-pc kernel: audit: type=1334 audit(1614853591.244:118): prog-id=9 op=UNLOAD
Mar 04 15:56:31 sintan-pc dhcpcd[515]: wlo1: no IPv6 Routers available
Mar 04 15:56:31 sintan-pc kdeinit5[2466]: Qt: Session management error: networkIdsList argument is NULL
Mar 04 15:56:36 sintan-pc kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
Mar 04 15:56:36 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Mar 04 15:56:36 sintan-pc kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
Mar 04 15:56:36 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Mar 04 15:56:36 sintan-pc systemd-logind[510]: Lid closed.
Mar 04 15:56:37 sintan-pc kscreenlocker_greet[2508]: Qt: Session management error: networkIdsList argument is NULL
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
Mar 04 15:56:38 sintan-pc kernel: wlo1: deauthenticating from 10:be:f5:fe:1e:ee by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 04 15:56:38 sintan-pc wpa_supplicant[618]: wlo1: CTRL-EVENT-DISCONNECTED bssid=10:be:f5:fe:1e:ee reason=3 locally_generated=1
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Interface wlo1.IPv6 no longer relevant for mDNS.
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Leaving mDNS multicast group on interface wlo1.IPv6 with address fe80::783a:5845:4bbe:83e8.
Mar 04 15:56:38 sintan-pc dhcpcd[515]: wlo1: carrier lost
Mar 04 15:56:38 sintan-pc wpa_supplicant[618]: rfkill: WLAN soft blocked
Mar 04 15:56:38 sintan-pc wpa_supplicant[618]: rfkill: WLAN soft blocked
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Interface wlo1.IPv4 no longer relevant for mDNS.
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Leaving mDNS multicast group on interface wlo1.IPv4 with address 192.168.0.2.
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Withdrawing address record for fe80::a60f:1d73:17d0:3a98 on wlo1.
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Withdrawing address record for fe80::783a:5845:4bbe:83e8 on wlo1.
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Withdrawing address record for 192.168.0.2 on wlo1.
Mar 04 15:56:38 sintan-pc NetworkManager[506]: <info> [1614853598.4702] manager: rfkill: Wi-Fi now disabled by radio killswitch
Mar 04 15:56:38 sintan-pc NetworkManager[506]: <info> [1614853598.4705] device (wlo1): state change: activated -> unavailable (reason 'none', sys-iface-state: 'managed')
Mar 04 15:56:38 sintan-pc NetworkManager[506]: <info> [1614853598.4879] dhcp4 (wlo1): canceled DHCP transaction
Mar 04 15:56:38 sintan-pc NetworkManager[506]: <info> [1614853598.4879] dhcp4 (wlo1): state changed bound -> done
Mar 04 15:56:38 sintan-pc dhcpcd[515]: wlo1: deleting address fe80::a60f:1d73:17d0:3a98
Mar 04 15:56:38 sintan-pc dhcpcd[515]: wlo1: deleting route to 192.168.0.0/24
Mar 04 15:56:38 sintan-pc dhcpcd[515]: wlo1: deleting default route via 192.168.0.1
Mar 04 15:56:38 sintan-pc NetworkManager[506]: <info> [1614853598.4922] manager: NetworkManager state is now DISCONNECTED
Mar 04 15:56:38 sintan-pc NetworkManager[506]: <info> [1614853598.5005] device (p2p-dev-wlo1): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
Mar 04 15:56:38 sintan-pc wpa_supplicant[618]: nl80211: deinit ifname=p2p-dev-wlo1 disabled_11b_rates=0
Mar 04 15:56:38 sintan-pc dbus-daemon[505]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.7' (uid=0 pid=506 comm="/usr/bin/NetworkManager --no-daemon ")
Mar 04 15:56:38 sintan-pc systemd[1]: Starting Network Manager Script Dispatcher Service...
░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit NetworkManager-dispatcher.service has begun execution.
░░
░░ The job identifier is 1965.
Mar 04 15:56:38 sintan-pc kded5[1041]: plasma-nm: Network connectivity limited, scheduling notification
Mar 04 15:56:38 sintan-pc dbus-daemon[505]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 04 15:56:38 sintan-pc systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░
░░ The job identifier is 1965.
Mar 04 15:56:38 sintan-pc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 04 15:56:38 sintan-pc kernel: audit: type=1130 audit(1614853598.542:119): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: Got SIGHUP, reloading.
Mar 04 15:56:38 sintan-pc avahi-daemon[501]: No service file found in /etc/avahi/services.
Mar 04 15:56:38 sintan-pc wpa_supplicant[618]: nl80211: deinit ifname=wlo1 disabled_11b_rates=0
Mar 04 15:56:38 sintan-pc systemd-logind[510]: Lid opened.
Mar 04 15:56:38 sintan-pc kscreenlocker_greet[2508]: file:///usr/lib/qt/qml/org/kde/plasma/workspace/components/KeyboardLayoutButton.qml:17: TypeError: Cannot read property 'longName' of undefined
Mar 04 15:56:43 sintan-pc audit[2609]: USER_AUTH pid=2609 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="sintan" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Mar 04 15:56:43 sintan-pc kernel: audit: type=1100 audit(1614853603.111:120): pid=2609 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="sintan" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Mar 04 15:56:43 sintan-pc kscreenlocker_greet[2508]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:27: TypeError: Cannot read property 'width' of null
Mar 04 15:56:43 sintan-pc kscreenlocker_greet[2508]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:45: TypeError: Cannot read property 'height' of null
Mar 04 15:56:43 sintan-pc kwin_x11[1045]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 23314, resource id: 157286458, major code: 18 (ChangeProperty), minor code: 0
Mar 04 15:56:43 sintan-pc appimagelauncherd[947]: Directories to watch disappeared, unintegrating AppImages formerly found in there
Mar 04 15:56:43 sintan-pc kwin_x11[1045]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 24074, resource id: 44040378, major code: 20 (GetProperty), minor code: 0
Mar 04 15:56:43 sintan-pc kwin_x11[1045]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 24075, resource id: 44040378, major code: 15 (QueryTree), minor code: 0
Mar 04 15:56:46 sintan-pc systemd[939]: Started st.
And this is the output of the same from a boot where this isn’t happening.
journalctl -xe -n 1000
Mar 04 16:02:36 sintan-pc kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
Mar 04 16:02:36 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Mar 04 16:02:36 sintan-pc systemd-logind[496]: Lid closed.
Mar 04 16:02:36 sintan-pc appimagelauncherd[936]: Done
Mar 04 16:02:36 sintan-pc kscreenlocker_greet[2440]: Qt: Session management error: networkIdsList argument is NULL
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:37 sintan-pc systemd-logind[496]: Lid opened.
Mar 04 16:02:37 sintan-pc systemd[1]: systemd-hostnamed.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit systemd-hostnamed.service has successfully entered the 'dead' state.
Mar 04 16:02:37 sintan-pc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 04 16:02:37 sintan-pc kernel: audit: type=1131 audit(1614853957.727:107): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 04 16:02:37 sintan-pc systemd-timesyncd[482]: Initial synchronization to time server 192.46.210.39:123 (2.manjaro.pool.ntp.org).
Mar 04 16:02:37 sintan-pc kscreenlocker_greet[2440]: file:///usr/lib/qt/qml/org/kde/plasma/workspace/components/KeyboardLayoutButton.qml:17: TypeError: Cannot read property 'longName' of undefined
Mar 04 16:02:37 sintan-pc audit: BPF prog-id=10 op=UNLOAD
Mar 04 16:02:37 sintan-pc audit: BPF prog-id=9 op=UNLOAD
Mar 04 16:02:37 sintan-pc kernel: audit: type=1334 audit(1614853957.219:108): prog-id=10 op=UNLOAD
Mar 04 16:02:37 sintan-pc kernel: audit: type=1334 audit(1614853957.219:109): prog-id=9 op=UNLOAD
Mar 04 16:02:41 sintan-pc audit[2502]: USER_AUTH pid=2502 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="sintan" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Mar 04 16:02:41 sintan-pc kernel: audit: type=1100 audit(1614853961.606:110): pid=2502 uid=1000 auid=1000 ses=2 msg='op=PAM:unix_chkpwd acct="sintan" exe="/usr/bin/unix_chkpwd" hostname=? addr=? terminal=? res=success'
Mar 04 16:02:41 sintan-pc kscreenlocker_greet[2440]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:27: TypeError: Cannot read property 'width' of null
Mar 04 16:02:41 sintan-pc kscreenlocker_greet[2440]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:45: TypeError: Cannot read property 'height' of null
Mar 04 16:02:41 sintan-pc kwin_x11[1034]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 18946, resource id: 167772218, major code: 18 (ChangeProperty), minor code: 0
Mar 04 16:02:47 sintan-pc kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
Mar 04 16:02:47 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Mar 04 16:02:47 sintan-pc kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
Mar 04 16:02:47 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Mar 04 16:02:47 sintan-pc systemd-logind[496]: Lid closed.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: Qt: Session management error: networkIdsList argument is NULL
Mar 04 16:02:48 sintan-pc systemd-logind[496]: Lid opened.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect.
Mar 04 16:02:48 sintan-pc kscreenlocker_greet[2504]: qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect.