Cannot enter sleep mode with too many programs running

When my computer has my regular amount of programs running, it won’t enter sleep mode, instead logging me off and “rebooting” (I guess) the log-in screen.
However, when I stop most of the programs (e.g. Thunderbird, Firefox, etc.), then it can enter sleep mode fine.

I did a reproduction :
01:12 : Try to enter sleep mode with regular amount of programs; fail and log back in
01:13 : Close said programs
01:14 : Enter sleep mode successfully
01:30 : Wake back up

I suspect the issue comes from nvidia, because of the output of journalctl (see at Jun 30 01:12:21) and dmesg.

output of journalctl --catalog --boot=0, cut to the above timeline`:

Jun 30 01:12:19 $HOSTNAME polkitd[670]: Registered Authentication Agent for unix-process:42605:1789930 (system bus name :1.563 [/usr/bin/pkttyagent --notify-fd 6 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
Jun 30 01:12:19 $HOSTNAME systemd-logind[673]: The system will suspend now!
Jun 30 01:12:19 $HOSTNAME ModemManager[747]: <msg> [sleep-monitor-systemd] system is about to suspend
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.8796] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.8801] device (p2p-dev-wlp7s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.8807] manager: NetworkManager state is now ASLEEP
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.8815] device (enp8s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.8847] device (wlp7s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jun 30 01:12:19 $HOSTNAME 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 20634.
Jun 30 01:12:19 $HOSTNAME polkitd[670]: Unregistered Authentication Agent for unix-process:unknown (system bus name :1.563, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
Jun 30 01:12:19 $HOSTNAME 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 20634.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9212] device (enp8s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 2a01:cb05:9116:7400:f800:165f:dd1:7449 on enp8s0.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address 2a01:cb05:9116:7400:f800:165f:dd1:7449.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9224] dhcp4 (enp8s0): canceled DHCP transaction
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9224] dhcp4 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9224] dhcp4 (enp8s0): state changed no lease
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9232] dhcp6 (enp8s0): canceled DHCP transaction
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::854c:ff60:14ab:74b7 on enp8s0.*.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9233] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::854c:ff60:14ab:74b7 on enp8s0.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9233] dhcp6 (enp8s0): state changed no lease
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Interface enp8s0.IPv6 no longer relevant for mDNS.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.13 on enp8s0.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv4 with address 192.168.1.13.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Interface enp8s0.IPv4 no longer relevant for mDNS.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9524] device (enp8s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 30 01:12:19 $HOSTNAME kernel: r8169 0000:08:00.0 enp8s0: Link is Down
Jun 30 01:12:19 $HOSTNAME kernel: wlp7s0: deauthenticating from b8:66:85:82:ed:e5 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 30 01:12:19 $HOSTNAME wpa_supplicant[1019]: nl80211: send_event_marker failed: Source based routing not supported
Jun 30 01:12:19 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=b8:66:85:82:ed:e5 reason=3 locally_generated=1
Jun 30 01:12:19 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:12:19 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9917] device (wlp7s0): supplicant interface state: completed -> disconnected
Jun 30 01:12:19 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9924] device (wlp7s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33 on wlp7s0.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9932] dhcp4 (wlp7s0): canceled DHCP transaction
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9932] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9933] dhcp4 (wlp7s0): state changed no lease
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9935] dhcp6 (wlp7s0): canceled DHCP transaction
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv6 with address 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9935] dhcp6 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:12:19 $HOSTNAME NetworkManager[663]: <info>  [1751238739.9935] dhcp6 (wlp7s0): state changed no lease
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.*.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:12:19 $HOSTNAME avahi-daemon[665]: Interface wlp7s0.IPv6 no longer relevant for mDNS.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Interface wlp7s0.IPv4 no longer relevant for mDNS.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.12 on wlp7s0.
Jun 30 01:12:20 $HOSTNAME NetworkManager[663]: <info>  [1751238740.0045] device (wlp7s0): set-hw-addr: set MAC address to BE:53:FC:6E:DE:F4 (scanning)
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: New relevant interface wlp7s0.IPv4 for mDNS.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.12 on wlp7s0.IPv4.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.12 on wlp7s0.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:12:20 $HOSTNAME avahi-daemon[665]: Interface wlp7s0.IPv4 no longer relevant for mDNS.
Jun 30 01:12:20 $HOSTNAME NetworkManager[663]: <info>  [1751238740.0385] device (wlp7s0): supplicant interface state: disconnected -> interface_disabled
Jun 30 01:12:20 $HOSTNAME NetworkManager[663]: <info>  [1751238740.0386] device (wlp7s0): supplicant interface state: interface_disabled -> disconnected
Jun 30 01:12:20 $HOSTNAME NetworkManager[663]: <info>  [1751238740.0388] device (wlp7s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 30 01:12:20 $HOSTNAME NetworkManager[663]: <info>  [1751238740.0552] device (wlp7s0): set-hw-addr: reset MAC address to 10:63:C8:76:2B:EB (unmanage)
Jun 30 01:12:20 $HOSTNAME wpa_supplicant[1019]: p2p-dev-wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:12:20 $HOSTNAME wpa_supplicant[1019]: p2p-dev-wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:12:20 $HOSTNAME wpa_supplicant[1019]: nl80211: deinit ifname=p2p-dev-wlp7s0 disabled_11b_rates=0
Jun 30 01:12:20 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:12:20 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:12:20 $HOSTNAME wpa_supplicant[1019]: nl80211: deinit ifname=wlp7s0 disabled_11b_rates=0
Jun 30 01:12:20 $HOSTNAME systemd[1]: Reached target Sleep.
-- Subject: A start job for unit sleep.target has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit sleep.target has finished successfully.
-- 
-- The job identifier is 20796.
Jun 30 01:12:20 $HOSTNAME systemd[1]: Starting NVIDIA system suspend actions...
-- Subject: A start job for unit nvidia-suspend.service has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-suspend.service has begun execution.
-- 
-- The job identifier is 20799.
Jun 30 01:12:20 $HOSTNAME suspend[42690]: nvidia-suspend.service
Jun 30 01:12:20 $HOSTNAME logger[42690]: <13>Jun 30 01:12:20 suspend: nvidia-suspend.service
Jun 30 01:12:21 $HOSTNAME kernel: ------------[ cut here ]------------
Jun 30 01:12:21 $HOSTNAME kernel: WARNING: CPU: 5 PID: 42696 at nvidia/nv.c:4648 nv_set_system_power_state+0x41e/0x480 [nvidia]
Jun 30 01:12:21 $HOSTNAME kernel: Modules linked in: udp_diag tcp_diag inet_diag ccm rfcomm qrtr squashfs uhid cmac algif_hash algif_skcipher af_alg bnep uinput nvidia_uvm(POE) snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_acpi soundwire_bus intel_uncore_frequency snd_soc_sdca intel_uncore_frequency_common crc8 snd_soc_avs uvcvideo snd_soc_hda_codec intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp videobuf2_vmalloc coretemp snd_soc_core btusb uvc videobuf2_memops btrtl snd_hda_codec_realtek videobuf2_v4l2 snd_compress kvm_intel btintel snd_hda_codec_generic ac97_bus btbcm videobuf2_common btmtk videodev snd_hda_scodec_component ath10k_pci snd_pcm_dmaengine snd_hda_codec_hdmi kvm mc bluetooth snd_hda_intel snd_intel_dspcfg
Jun 30 01:12:21 $HOSTNAME kernel:  ath10k_core irqbypass snd_intel_sdw_acpi polyval_clmulni polyval_generic joydev snd_hda_codec ath ghash_clmulni_intel sha512_ssse3 mousedev iTCO_wdt snd_hda_core processor_thermal_device_pci_legacy sha256_ssse3 intel_pmc_bxt processor_thermal_device intel_rapl_msr mac80211 sha1_ssse3 iTCO_vendor_support processor_thermal_wt_hint snd_hwdep aesni_intel processor_thermal_rfim r8169 crypto_simd snd_pcm processor_thermal_rapl 8250_dw cryptd intel_rapl_common realtek rapl nvidia_drm(POE) mei_hdcp mei_pxp mdio_devres snd_timer libarc4 i2c_i801 nvidia_modeset(POE) intel_cstate processor_thermal_wt_req vfat i2c_hid_acpi spi_nor snd mei_me processor_thermal_power_floor i2c_smbus intel_lpss_pci intel_uncore processor_thermal_mbox fat cfg80211 pcspkr intel_wmi_thunderbolt wmi_bmof libphy mtd i2c_mux ideapad_laptop drm_ttm_helper i2c_hid soundcore intel_lpss intel_pch_thermal intel_soc_dts_iosf mei idma64 elan_i2c platform_profile sparse_keymap int3403_thermal intel_pmc_core rfkill int340x_thermal_zone pmt_telemetry
Jun 30 01:12:21 $HOSTNAME kernel:  pmt_class nvidia(POE) int3400_thermal pinctrl_cannonlake intel_vsec acpi_thermal_rel acpi_tad acpi_pad mac_hid sg crypto_user loop dm_mod nfnetlink ip_tables x_tables i915 i2c_algo_bit nvme drm_buddy ttm nvme_core spi_intel_pci intel_gtt serio_raw nvme_keyring spi_intel drm_display_helper nvme_auth cec video wmi
Jun 30 01:12:21 $HOSTNAME kernel: CPU: 5 UID: 0 PID: 42696 Comm: nvidia-sleep.sh Tainted: P        W  OE       6.15.3-1-MANJARO #1 PREEMPT(full)  5e8b0697e5491c80c8a92bc22d4fbb4b85976c24
Jun 30 01:12:21 $HOSTNAME kernel: Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Jun 30 01:12:21 $HOSTNAME kernel: Hardware name: LENOVO 81LK/LNVNB161216, BIOS BGCN36WW 05/24/2022
Jun 30 01:12:21 $HOSTNAME kernel: RIP: 0010:nv_set_system_power_state+0x41e/0x480 [nvidia]
Jun 30 01:12:21 $HOSTNAME kernel: Code: 75 0e eb 3f 48 8b ad d0 06 00 00 48 85 ed 74 33 48 8b bd 30 03 00 00 ba 01 00 00 00 44 89 e6 e8 08 c8 ff ff 89 c3 85 c0 74 da <0f> 0b 48 c7 c7 70 ff 17 c2 41 bc 01 00 00 00 e8 fe 12 72 f0 e9 ef
Jun 30 01:12:21 $HOSTNAME kernel: RSP: 0018:ffffcff68a17ba68 EFLAGS: 00010202
Jun 30 01:12:21 $HOSTNAME kernel: RAX: 0000000000000051 RBX: 0000000000000051 RCX: ffff8b0e04ce16b0
Jun 30 01:12:21 $HOSTNAME kernel: RDX: ffff8b0e04ce16b0 RSI: 0000000000000282 RDI: ffff8b0e04ce16a8
Jun 30 01:12:21 $HOSTNAME kernel: RBP: ffff8b0e04ce1000 R08: 0000000000000000 R09: ffffffffc1001bf4
Jun 30 01:12:21 $HOSTNAME kernel: R10: ffff8b0ec1773000 R11: fffff7010705dc00 R12: 0000000000000001
Jun 30 01:12:21 $HOSTNAME kernel: R13: 0000000000000000 R14: ffff8b0ec1773000 R15: ffff8b0e04ce16a8
Jun 30 01:12:21 $HOSTNAME kernel: FS:  00007f1a95353b80(0000) GS:ffff8b0fb2e6f000(0000) knlGS:0000000000000000
Jun 30 01:12:21 $HOSTNAME kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 30 01:12:21 $HOSTNAME kernel: CR2: 00007f1a955ac7b0 CR3: 0000000167ece003 CR4: 00000000003726f0
Jun 30 01:12:21 $HOSTNAME kernel: Call Trace:
Jun 30 01:12:21 $HOSTNAME kernel:  <TASK>
Jun 30 01:12:21 $HOSTNAME kernel:  nv_procfs_write_suspend+0xfe/0x180 [nvidia c550f7d9e312df76ef65d70bce47728b5f08ee0f]
Jun 30 01:12:21 $HOSTNAME kernel:  proc_reg_write+0x57/0xb0
Jun 30 01:12:21 $HOSTNAME kernel:  vfs_write+0xef/0x470
Jun 30 01:12:21 $HOSTNAME kernel:  ksys_write+0x73/0xe0
Jun 30 01:12:21 $HOSTNAME kernel:  do_syscall_64+0x7b/0x810
Jun 30 01:12:21 $HOSTNAME kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Jun 30 01:12:21 $HOSTNAME kernel:  ? do_syscall_64+0x87/0x810
Jun 30 01:12:21 $HOSTNAME kernel:  ? do_fcntl+0x442/0x840
Jun 30 01:12:21 $HOSTNAME kernel:  ? do_syscall_64+0x87/0x810
Jun 30 01:12:21 $HOSTNAME kernel:  ? __x64_sys_fcntl+0x90/0xf0
Jun 30 01:12:21 $HOSTNAME kernel:  ? ptep_set_access_flags+0x32/0x40
Jun 30 01:12:21 $HOSTNAME kernel:  ? wp_page_reuse+0x8d/0xa0
Jun 30 01:12:21 $HOSTNAME kernel:  ? do_wp_page+0x925/0xed0
Jun 30 01:12:21 $HOSTNAME kernel:  ? get_close_on_exec+0x34/0x40
Jun 30 01:12:21 $HOSTNAME kernel:  ? do_fcntl+0x30b/0x840
Jun 30 01:12:21 $HOSTNAME kernel:  ? __handle_mm_fault+0xae0/0xfd0
Jun 30 01:12:21 $HOSTNAME kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Jun 30 01:12:21 $HOSTNAME kernel:  ? __count_memcg_events+0xb0/0x150
Jun 30 01:12:21 $HOSTNAME kernel:  ? count_memcg_events.constprop.0+0x1a/0x30
Jun 30 01:12:21 $HOSTNAME kernel:  ? handle_mm_fault+0x1d2/0x2d0
Jun 30 01:12:21 $HOSTNAME kernel:  ? do_user_addr_fault+0x21a/0x690
Jun 30 01:12:21 $HOSTNAME kernel:  ? irqentry_exit_to_user_mode+0x2c/0x1b0
Jun 30 01:12:21 $HOSTNAME kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jun 30 01:12:21 $HOSTNAME kernel: RIP: 0033:0x7f1a95456006
Jun 30 01:12:21 $HOSTNAME kernel: Code: 5d e8 41 8b 93 08 03 00 00 59 5e 48 83 f8 fc 75 19 83 e2 39 83 fa 08 75 11 e8 26 ff ff ff 66 0f 1f 44 00 00 48 8b 45 10 0f 05 <48> 8b 5d f8 c9 c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 e5 48 83 ec 08
Jun 30 01:12:21 $HOSTNAME kernel: RSP: 002b:00007fff2308a4e0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
Jun 30 01:12:21 $HOSTNAME kernel: RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007f1a95456006
Jun 30 01:12:21 $HOSTNAME kernel: RDX: 0000000000000008 RSI: 000055e25c5956a0 RDI: 0000000000000001
Jun 30 01:12:21 $HOSTNAME kernel: RBP: 00007fff2308a500 R08: 0000000000000000 R09: 0000000000000000
Jun 30 01:12:21 $HOSTNAME kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000008
Jun 30 01:12:21 $HOSTNAME kernel: R13: 000055e25c5956a0 R14: 00007f1a955ab5c0 R15: 0000000000000000
Jun 30 01:12:21 $HOSTNAME kernel:  </TASK>
Jun 30 01:12:21 $HOSTNAME kernel: ---[ end trace 0000000000000000 ]---
Jun 30 01:12:21 $HOSTNAME nvidia-sleep.sh[42696]: /usr/bin/nvidia-sleep.sh: ligne 45 : echo: erreur d'écriture : Erreur d'entrée/sortie
Jun 30 01:12:21 $HOSTNAME systemd[1]: nvidia-suspend.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- An ExecStart= process belonging to unit nvidia-suspend.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Jun 30 01:12:21 $HOSTNAME systemd[1]: nvidia-suspend.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit nvidia-suspend.service has entered the 'failed' state with result 'exit-code'.
Jun 30 01:12:21 $HOSTNAME systemd[1]: Failed to start NVIDIA system suspend actions.
-- Subject: A start job for unit nvidia-suspend.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-suspend.service has finished with a failure.
-- 
-- The job identifier is 20799 and the job result is failed.
Jun 30 01:12:21 $HOSTNAME systemd[1]: Starting System Suspend...
-- Subject: A start job for unit systemd-suspend.service has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit systemd-suspend.service has begun execution.
-- 
-- The job identifier is 20795.
Jun 30 01:12:21 $HOSTNAME systemd-sleep[42711]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jun 30 01:12:21 $HOSTNAME systemd-sleep[42711]: This is not recommended, and might result in unexpected behavior, particularly
Jun 30 01:12:21 $HOSTNAME systemd-sleep[42711]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jun 30 01:12:21 $HOSTNAME systemd-sleep[42711]: Performing sleep operation 'suspend'...
-- Subject: System sleep state suspend entered
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The system has now entered the suspend sleep state.
Jun 30 01:12:21 $HOSTNAME kernel: PM: suspend entry (deep)
Jun 30 01:12:21 $HOSTNAME kernel: Filesystems sync: 0.005 seconds
Jun 30 01:12:24 $HOSTNAME kernel: Freezing user space processes
Jun 30 01:12:24 $HOSTNAME kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Jun 30 01:12:24 $HOSTNAME kernel: OOM killer disabled.
Jun 30 01:12:24 $HOSTNAME kernel: Freezing remaining freezable tasks
Jun 30 01:12:24 $HOSTNAME kernel: Freezing remaining freezable tasks completed (elapsed 0.095 seconds)
Jun 30 01:12:24 $HOSTNAME kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 30 01:12:24 $HOSTNAME kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jun 30 01:12:24 $HOSTNAME kernel: ata5.00: Entering standby power mode
Jun 30 01:12:24 $HOSTNAME kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jun 30 01:12:24 $HOSTNAME kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Jun 30 01:12:24 $HOSTNAME kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
Jun 30 01:12:24 $HOSTNAME kernel: nvidia 0000:01:00.0: PM: failed to suspend async: error -5
Jun 30 01:12:24 $HOSTNAME kernel: PM: Some devices failed to suspend, or early wake event detected
Jun 30 01:12:24 $HOSTNAME kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jun 30 01:12:24 $HOSTNAME kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 30 01:12:24 $HOSTNAME kernel: sd 4:0:0:0: [sda] Starting disk
Jun 30 01:12:24 $HOSTNAME kernel: ata5.00: configured for UDMA/133
Jun 30 01:12:24 $HOSTNAME kernel: ata5.00: Entering active power mode
Jun 30 01:12:24 $HOSTNAME kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Jun 30 01:12:24 $HOSTNAME kernel: OOM killer enabled.
Jun 30 01:12:24 $HOSTNAME kernel: Restarting tasks ... done.
Jun 30 01:12:24 $HOSTNAME kernel: random: crng reseeded on system resumption
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.163 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.174 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.185 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-082ee5a7-7c25-470a-9643-0c06f0466ea1: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.196 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-3c4852d6-d47b-4f46-b05e-b5edc1aa440e: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME kernel: PM: suspend exit
Jun 30 01:12:24 $HOSTNAME kernel: PM: suspend entry (s2idle)
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.207 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-dba4d603-d7ed-4931-8823-17ad585705d5: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME kernel: Filesystems sync: 0.006 seconds
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.222 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-f908627d-13bf-4a04-b91f-a64e9245323d: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.236 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-5565a099-7fe2-45c1-a22b-d7e9dfea9a2e: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.249 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-8c2f4425-77d6-4755-aca3-891fdbc66a58: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.260 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-42b3ce2f-bd9f-485a-96ae-26406230b1ff: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.270 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-55213584-9a29-4916-badf-0fb7ed682aeb: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.283 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-8e6a6715-9abc-4043-88ef-9e39c6f63e0f: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:24 $HOSTNAME fwupd[26622]: 23:12:24.297 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-309dcde8-ccb1-4062-8f78-600115a34327: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME kernel: Freezing user space processes
Jun 30 01:12:26 $HOSTNAME kernel: Freezing user space processes completed (elapsed 0.004 seconds)
Jun 30 01:12:26 $HOSTNAME kernel: OOM killer disabled.
Jun 30 01:12:26 $HOSTNAME kernel: Freezing remaining freezable tasks
Jun 30 01:12:26 $HOSTNAME kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jun 30 01:12:26 $HOSTNAME kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 30 01:12:26 $HOSTNAME kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jun 30 01:12:26 $HOSTNAME kernel: ata5.00: Entering standby power mode
Jun 30 01:12:26 $HOSTNAME kernel: NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
Jun 30 01:12:26 $HOSTNAME kernel: nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
Jun 30 01:12:26 $HOSTNAME kernel: nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
Jun 30 01:12:26 $HOSTNAME kernel: nvidia 0000:01:00.0: PM: failed to suspend async: error -5
Jun 30 01:12:26 $HOSTNAME kernel: PM: Some devices failed to suspend, or early wake event detected
Jun 30 01:12:26 $HOSTNAME kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 30 01:12:26 $HOSTNAME kernel: sd 4:0:0:0: [sda] Starting disk
Jun 30 01:12:26 $HOSTNAME kernel: ata5.00: configured for UDMA/133
Jun 30 01:12:26 $HOSTNAME kernel: ata5.00: Entering active power mode
Jun 30 01:12:26 $HOSTNAME kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Jun 30 01:12:26 $HOSTNAME kernel: OOM killer enabled.
Jun 30 01:12:26 $HOSTNAME kernel: Restarting tasks ... done.
Jun 30 01:12:26 $HOSTNAME kernel: random: crng reseeded on system resumption
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.797 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-5565a099-7fe2-45c1-a22b-d7e9dfea9a2e: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.808 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-3c4852d6-d47b-4f46-b05e-b5edc1aa440e: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.820 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-082ee5a7-7c25-470a-9643-0c06f0466ea1: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.831 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-dba4d603-d7ed-4931-8823-17ad585705d5: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.842 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME systemd-sleep[42711]: Failed to put system to sleep. System resumed again: Input/output error
-- Subject: System sleep state suspend left
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The system has now left the suspend sleep state.
Jun 30 01:12:26 $HOSTNAME kernel: PM: suspend exit
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.855 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-f908627d-13bf-4a04-b91f-a64e9245323d: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.867 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-8c2f4425-77d6-4755-aca3-891fdbc66a58: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.879 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-309dcde8-ccb1-4062-8f78-600115a34327: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.894 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-8e6a6715-9abc-4043-88ef-9e39c6f63e0f: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.905 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-42b3ce2f-bd9f-485a-96ae-26406230b1ff: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.916 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-55213584-9a29-4916-badf-0fb7ed682aeb: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:26 $HOSTNAME fwupd[26622]: 23:12:26.927 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:12:27 $HOSTNAME systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- An ExecStart= process belonging to unit systemd-suspend.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 1.
Jun 30 01:12:27 $HOSTNAME systemd[1]: systemd-suspend.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit systemd-suspend.service has entered the 'failed' state with result 'exit-code'.
Jun 30 01:12:27 $HOSTNAME systemd[1]: Failed to start System Suspend.
-- Subject: A start job for unit systemd-suspend.service has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit systemd-suspend.service has finished with a failure.
-- 
-- The job identifier is 20795 and the job result is failed.
Jun 30 01:12:27 $HOSTNAME systemd[1]: Dependency failed for Suspend.
-- Subject: A start job for unit suspend.target has failed
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit suspend.target has finished with a failure.
-- 
-- The job identifier is 20794 and the job result is dependency.
Jun 30 01:12:27 $HOSTNAME systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'.
Jun 30 01:12:27 $HOSTNAME systemd-logind[673]: Operation 'suspend' finished.
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.1692] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 30 01:12:27 $HOSTNAME ModemManager[747]: <msg> [sleep-monitor-systemd] system is resuming
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.1695] device (enp8s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:12:27 $HOSTNAME systemd[1]: Stopped target Sleep.
-- Subject: A stop job for unit sleep.target has finished
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A stop job for unit sleep.target has finished.
-- 
-- The job identifier is 20957 and the job result is done.
Jun 30 01:12:27 $HOSTNAME systemd[1]: Starting NVIDIA system resume actions...
-- Subject: A start job for unit nvidia-resume.service has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-resume.service has begun execution.
-- 
-- The job identifier is 20956.
Jun 30 01:12:27 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:12:27 qt.bluetooth.bluez: Bluetooth device is powered off
Jun 30 01:12:27 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:12:27 default: Error sending UDP packet: QAbstractSocket::NetworkError
Jun 30 01:12:27 $HOSTNAME kernel: Generic FE-GE Realtek PHY r8169-0-800:00: attached PHY driver (mii_bus:phy_addr=r8169-0-800:00, irq=MAC)
Jun 30 01:12:27 $HOSTNAME plasmashell[1215]: kpipewire_logging: PipeWire remote error:  -116 no global 37 any more
Jun 30 01:12:27 $HOSTNAME suspend[43019]: nvidia-resume.service
Jun 30 01:12:27 $HOSTNAME logger[43019]: <13>Jun 30 01:12:27 suspend: nvidia-resume.service
Jun 30 01:12:27 $HOSTNAME bluetoothd[666]: Failed to set mode: Failed (0x03)
Jun 30 01:12:27 $HOSTNAME kded6[1190]: kf.bluezqt: PendingCall Error: "Failed"
Jun 30 01:12:27 $HOSTNAME systemd[1]: nvidia-resume.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit nvidia-resume.service has successfully entered the 'dead' state.
Jun 30 01:12:27 $HOSTNAME systemd[1]: Finished NVIDIA system resume actions.
-- Subject: A start job for unit nvidia-resume.service has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-resume.service has finished successfully.
-- 
-- The job identifier is 20956.
Jun 30 01:12:27 $HOSTNAME kernel: r8169 0000:08:00.0 enp8s0: Link is Down
Jun 30 01:12:27 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:12:27 kdeconnect.core: Failed to open any MDNS client sockets
Jun 30 01:12:27 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:12:27 kdeconnect.core: Failed to open any MDNS server sockets
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3525] device (wlp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3538] device (p2p-dev-wlp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3544] manager: NetworkManager state is now DISCONNECTED
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3852] device (wlp7s0): supplicant interface state: internal-starting -> disconnected
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3852] device (p2p-dev-wlp7s0): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3858] Wi-Fi P2P device controlled by interface wlp7s0 created
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3861] manager: (p2p-dev-wlp7s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/26)
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3864] device (p2p-dev-wlp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3870] device (wlp7s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Jun 30 01:12:27 $HOSTNAME NetworkManager[663]: <info>  [1751238747.3877] device (p2p-dev-wlp7s0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Jun 30 01:12:27 $HOSTNAME kcminit[43031]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Jun 30 01:12:28 $HOSTNAME kcminit[43031]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Jun 30 01:12:28 $HOSTNAME kcminit[43031]: kcm_touchpad: Using X11 backend
Jun 30 01:12:30 $HOSTNAME kernel: r8169 0000:08:00.0 enp8s0: Link is Up - 1Gbps/Full - flow control rx/tx
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2324] device (enp8s0): carrier: link connected
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2331] device (enp8s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2353] policy: auto-activating connection 'Connexion filaire 1' (0cbc36e3-6ae5-3d97-bb57-5420fe52a401)
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2358] device (enp8s0): Activation: starting connection 'Connexion filaire 1' (0cbc36e3-6ae5-3d97-bb57-5420fe52a401)
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2359] device (enp8s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2362] manager: NetworkManager state is now CONNECTING
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2364] device (enp8s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2369] device (enp8s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 30 01:12:30 $HOSTNAME NetworkManager[663]: <info>  [1751238750.2377] dhcp4 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:30 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:12:30 $HOSTNAME avahi-daemon[665]: New relevant interface enp8s0.IPv6 for mDNS.
Jun 30 01:12:30 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::854c:ff60:14ab:74b7 on enp8s0.*.
Jun 30 01:12:31 $HOSTNAME ModemManager[747]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.4/0000:07:00.0': not supported by any plugin
Jun 30 01:12:31 $HOSTNAME ModemManager[747]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.5/0000:08:00.0': not supported by any plugin
Jun 30 01:12:32 $HOSTNAME systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2664] dhcp4 (enp8s0): state changed new lease, address=192.168.1.13, acd pending
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2671] policy: auto-activating connection 'Livebox-EDE0' (fdb79a2e-59e2-48d1-b522-627ea43c61cf)
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2688] device (wlp7s0): Activation: starting connection 'Livebox-EDE0' (fdb79a2e-59e2-48d1-b522-627ea43c61cf)
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2689] device (wlp7s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2695] device (wlp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2698] device (wlp7s0): Activation: (wifi) access point 'Livebox-EDE0' has security, but secrets are required.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2699] device (wlp7s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2701] sup-iface[c7312a63edb3ea5c,22,wlp7s0]: wps: type pbc start...
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPS-PBC-ACTIVE
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2774] device (wlp7s0): supplicant interface state: disconnected -> scanning
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2774] device (p2p-dev-wlp7s0): supplicant management interface state: disconnected -> scanning
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2897] device (wlp7s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2902] device (wlp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2905] device (wlp7s0): Activation: (wifi) connection 'Livebox-EDE0' has security, and secrets exist.  No new secrets needed.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2905] Config: added 'ssid' value 'Livebox-EDE0'
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPS-CANCEL
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2905] Config: added 'scan_ssid' value '1'
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2905] Config: added 'bgscan' value 'simple:30:-65:300'
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2905] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.2906] Config: added 'psk' value '<hidden>'
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: SME: Trying to authenticate with b8:66:85:82:ed:e0 (SSID='Livebox-EDE0' freq=2412 MHz)
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3427] device (wlp7s0): supplicant interface state: scanning -> authenticating
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3427] device (p2p-dev-wlp7s0): supplicant management interface state: scanning -> authenticating
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: authenticate with b8:66:85:82:ed:e0 (local address=10:63:c8:76:2b:eb)
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: send auth to b8:66:85:82:ed:e0 (try 1/3)
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Trying to associate with b8:66:85:82:ed:e0 (SSID='Livebox-EDE0' freq=2412 MHz)
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: authenticated
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3458] device (wlp7s0): supplicant interface state: authenticating -> associating
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3458] device (p2p-dev-wlp7s0): supplicant management interface state: authenticating -> associating
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: associate with b8:66:85:82:ed:e0 (try 1/3)
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: RX AssocResp from b8:66:85:82:ed:e0 (capab=0x1411 status=0 aid=1)
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: associated
Jun 30 01:12:32 $HOSTNAME kernel: ath: EEPROM regdomain: 0x80fa
Jun 30 01:12:32 $HOSTNAME kernel: ath: EEPROM indicates we should expect a country code
Jun 30 01:12:32 $HOSTNAME kernel: ath: doing EEPROM country->regdmn map search
Jun 30 01:12:32 $HOSTNAME kernel: ath: country maps to regdmn code: 0x37
Jun 30 01:12:32 $HOSTNAME kernel: ath: Country alpha2 being used: FR
Jun 30 01:12:32 $HOSTNAME kernel: ath: Regpair used: 0x37
Jun 30 01:12:32 $HOSTNAME kernel: ath: regdomain 0x80fa dynamically updated by country element
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Associated with b8:66:85:82:ed:e0
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3603] device (wlp7s0): supplicant interface state: associating -> associated
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3603] device (p2p-dev-wlp7s0): supplicant management interface state: associating -> associated
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3775] device (wlp7s0): supplicant interface state: associated -> 4way_handshake
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.3775] device (p2p-dev-wlp7s0): supplicant management interface state: associated -> 4way_handshake
Jun 30 01:12:32 $HOSTNAME kernel: wlp7s0: Limiting TX power to 20 (20 - 0) dBm as advertised by b8:66:85:82:ed:e0
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPA: Key negotiation completed with b8:66:85:82:ed:e0 [PTK=CCMP GTK=CCMP]
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-CONNECTED - Connection to b8:66:85:82:ed:e0 completed [id=0 id_str=]
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4130] device (wlp7s0): supplicant interface state: 4way_handshake -> completed
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4131] device (wlp7s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Livebox-EDE0"
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4132] device (p2p-dev-wlp7s0): supplicant management interface state: 4way_handshake -> completed
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4135] device (wlp7s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4151] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: New relevant interface wlp7s0.IPv6 for mDNS.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.*.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4358] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12, acd pending
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4661] dhcp4 (enp8s0): state changed new lease, address=192.168.1.13
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv4 with address 192.168.1.13.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: New relevant interface enp8s0.IPv4 for mDNS.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.13 on enp8s0.IPv4.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4694] policy: set 'Connexion filaire 1' (enp8s0) as default for IPv4 routing and DNS
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.4843] device (enp8s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME 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 20962.
Jun 30 01:12:32 $HOSTNAME 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 20962.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5491] device (enp8s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5494] device (enp8s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5505] device (enp8s0): Activation: successful, device activated.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5851] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: New relevant interface wlp7s0.IPv4 for mDNS.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.12 on wlp7s0.IPv4.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5945] device (wlp7s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5978] device (wlp7s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5981] device (wlp7s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5988] manager: NetworkManager state is now CONNECTED_SITE
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.5996] device (wlp7s0): Activation: successful, device activated.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.6155] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 30 01:12:32 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-32 noise=-54 txrate=0
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.7565] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv6 with address 2a01:cb05:9116:7400:f800:165f:dd1:7449.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Registering new address record for 2a01:cb05:9116:7400:f800:165f:dd1:7449 on enp8s0.*.
Jun 30 01:12:32 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::854c:ff60:14ab:74b7 on enp8s0.
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.7590] policy: set 'Connexion filaire 1' (enp8s0) as default for IPv6 routing and DNS
Jun 30 01:12:32 $HOSTNAME NetworkManager[663]: <info>  [1751238752.7693] dhcp6 (enp8s0): state changed new lease
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WNM: Disassociation Imminent - Disassociation Timer 15
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WNM: Preferred List Available
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: SME: Trying to authenticate with b8:66:85:82:ed:e5 (SSID='Livebox-EDE0' freq=5500 MHz)
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: disconnect from AP b8:66:85:82:ed:e0 for new auth to b8:66:85:82:ed:e5
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: authenticate with b8:66:85:82:ed:e5 (local address=10:63:c8:76:2b:eb)
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: send auth to b8:66:85:82:ed:e5 (try 1/3)
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.8707] device (wlp7s0): supplicant interface state: completed -> authenticating
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: authenticated
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.8707] device (p2p-dev-wlp7s0): supplicant management interface state: completed -> authenticating
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Trying to associate with b8:66:85:82:ed:e5 (SSID='Livebox-EDE0' freq=5500 MHz)
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.8743] device (wlp7s0): supplicant interface state: authenticating -> associating
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.8743] device (p2p-dev-wlp7s0): supplicant management interface state: authenticating -> associating
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: associate with b8:66:85:82:ed:e5 (try 1/3)
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: RX ReassocResp from b8:66:85:82:ed:e5 (capab=0x1511 status=0 aid=55)
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Associated with b8:66:85:82:ed:e5
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: associated
Jun 30 01:12:33 $HOSTNAME kernel: ath: EEPROM regdomain: 0x80fa
Jun 30 01:12:33 $HOSTNAME kernel: ath: EEPROM indicates we should expect a country code
Jun 30 01:12:33 $HOSTNAME kernel: ath: doing EEPROM country->regdmn map search
Jun 30 01:12:33 $HOSTNAME kernel: ath: country maps to regdmn code: 0x37
Jun 30 01:12:33 $HOSTNAME kernel: ath: Country alpha2 being used: FR
Jun 30 01:12:33 $HOSTNAME kernel: ath: Regpair used: 0x37
Jun 30 01:12:33 $HOSTNAME kernel: ath: regdomain 0x80fa dynamically updated by country element
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.8863] device (wlp7s0): supplicant interface state: associating -> associated
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.8864] device (p2p-dev-wlp7s0): supplicant management interface state: associating -> associated
Jun 30 01:12:33 $HOSTNAME kernel: wlp7s0: Limiting TX power to 25 (25 - 0) dBm as advertised by b8:66:85:82:ed:e5
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9437] device (wlp7s0): supplicant interface state: associated -> 4way_handshake
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9437] device (p2p-dev-wlp7s0): supplicant management interface state: associated -> 4way_handshake
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPA: Key negotiation completed with b8:66:85:82:ed:e5 [PTK=CCMP GTK=CCMP]
Jun 30 01:12:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-CONNECTED - Connection to b8:66:85:82:ed:e5 completed [id=0 id_str=]
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9841] device (wlp7s0): supplicant interface state: 4way_handshake -> completed
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9842] device (wlp7s0): ip:dhcp4: restarting
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9931] dhcp4 (wlp7s0): canceled DHCP transaction
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9931] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9931] dhcp4 (wlp7s0): state changed no lease
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9932] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:33 $HOSTNAME NetworkManager[663]: <info>  [1751238753.9933] device (p2p-dev-wlp7s0): supplicant management interface state: 4way_handshake -> completed
Jun 30 01:12:34 $HOSTNAME NetworkManager[663]: <info>  [1751238754.0083] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12, acd pending
Jun 30 01:12:34 $HOSTNAME NetworkManager[663]: <info>  [1751238754.0085] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12
Jun 30 01:12:34 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=-96 txrate=0
Jun 30 01:12:36 $HOSTNAME NetworkManager[663]: <info>  [1751238756.0805] dhcp6 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:12:36 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:12:36 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv6 with address 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33.
Jun 30 01:12:36 $HOSTNAME avahi-daemon[665]: Registering new address record for 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33 on wlp7s0.*.
Jun 30 01:12:36 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.
Jun 30 01:12:37 $HOSTNAME NetworkManager[663]: <info>  [1751238757.0728] dhcp6 (wlp7s0): state changed new lease
Jun 30 01:12:42 $HOSTNAME systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Jun 30 01:13:34 $HOSTNAME thunderbird[38986]: JavaScript error: , line 0: uncaught exception: undefined
Jun 30 01:13:35 $HOSTNAME systemd[1047]: app-org.mozilla.Thunderbird@11e253bdfd734c3fa38abcb3c5ac4888.service: Consumed 1min 6.966s CPU time, 932.5M memory peak, 135.4M memory swap peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit UNIT completed and consumed the indicated resources.
Jun 30 01:13:40 $HOSTNAME rtkit-daemon[1184]: Supervising 7 threads of 4 processes of 1 users.
Jun 30 01:13:40 $HOSTNAME rtkit-daemon[1184]: Supervising 7 threads of 4 processes of 1 users.
Jun 30 01:13:40 $HOSTNAME rtkit-daemon[1184]: Successfully made thread 43121 of process 38567 owned by '1000' RT at priority 10.
Jun 30 01:13:40 $HOSTNAME rtkit-daemon[1184]: Supervising 8 threads of 4 processes of 1 users.
Jun 30 01:13:41 $HOSTNAME systemd[1047]: app-codium@18b2b0b102774d3c9db173a7e40b983e.service: Consumed 1min 33.161s CPU time, 1.3G memory peak, 71.2M memory swap peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit UNIT completed and consumed the indicated resources.
Jun 30 01:13:42 $HOSTNAME firefox[38567]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Jun 30 01:13:42 $HOSTNAME firefox[38567]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Jun 30 01:13:42 $HOSTNAME firefox[38567]: [GFX1]: Error in eglSetDamageRegion: 0x3009
Jun 30 01:13:43 $HOSTNAME systemd[1047]: app-firefox@493a173026d7447281406a6a7324dce1.service: Consumed 42.936s CPU time, 1.4G memory peak, 129.3M memory swap peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit UNIT completed and consumed the indicated resources.
Jun 30 01:13:44 $HOSTNAME kded6[1190]: Service  ":1.349" unregistered
Jun 30 01:13:44 $HOSTNAME systemd[1047]: app-zulip\x2ddesktop@e65f91b415924a6cb9a73cbf361cbd70.service: Consumed 31.190s CPU time, 662M memory peak, 222.6M memory swap peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit UNIT completed and consumed the indicated resources.
Jun 30 01:13:46 $HOSTNAME kded6[1190]: Service  ":1.347" unregistered
Jun 30 01:13:46 $HOSTNAME systemd[1047]: app-org.keepassxc.KeePassXC@f8de9160d9ac47d7b65630bd07df70e0.service: Consumed 1.916s CPU time, 69.5M memory peak, 24.7M memory swap peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit UNIT completed and consumed the indicated resources.
Jun 30 01:13:56 $HOSTNAME systemd[1047]: app-org.kde.dolphin@404965a2b199488c92a4457129cd694a.service: Consumed 5.583s CPU time, 148M memory peak, 44.3M memory swap peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit UNIT completed and consumed the indicated resources.
Jun 30 01:14:07 $HOSTNAME polkitd[670]: Registered Authentication Agent for unix-process:43155:1800708 (system bus name :1.572 [/usr/bin/pkttyagent --notify-fd 6 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8)
Jun 30 01:14:07 $HOSTNAME systemd-logind[673]: The system will suspend now!
Jun 30 01:14:07 $HOSTNAME ModemManager[747]: <msg> [sleep-monitor-systemd] system is about to suspend
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6517] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6519] device (p2p-dev-wlp7s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6524] manager: NetworkManager state is now ASLEEP
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6525] device (enp8s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6544] device (wlp7s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME 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 21122.
Jun 30 01:14:07 $HOSTNAME polkitd[670]: Unregistered Authentication Agent for unix-process:unknown (system bus name :1.572, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale fr_FR.UTF-8) (disconnected from bus)
Jun 30 01:14:07 $HOSTNAME 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 21122.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6911] device (enp8s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 2a01:cb05:9116:7400:f800:165f:dd1:7449 on enp8s0.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address 2a01:cb05:9116:7400:f800:165f:dd1:7449.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6918] dhcp4 (enp8s0): canceled DHCP transaction
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6918] dhcp4 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::854c:ff60:14ab:74b7 on enp8s0.*.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6918] dhcp4 (enp8s0): state changed no lease
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::854c:ff60:14ab:74b7 on enp8s0.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6921] dhcp6 (enp8s0): canceled DHCP transaction
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6921] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Interface enp8s0.IPv6 no longer relevant for mDNS.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.6921] dhcp6 (enp8s0): state changed no lease
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.13 on enp8s0.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv4 with address 192.168.1.13.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Interface enp8s0.IPv4 no longer relevant for mDNS.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7274] device (enp8s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME kernel: r8169 0000:08:00.0 enp8s0: Link is Down
Jun 30 01:14:07 $HOSTNAME kernel: wlp7s0: deauthenticating from b8:66:85:82:ed:e5 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: nl80211: send_event_marker failed: Source based routing not supported
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DISCONNECTED bssid=b8:66:85:82:ed:e5 reason=3 locally_generated=1
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7787] device (wlp7s0): supplicant interface state: completed -> disconnected
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7793] device (wlp7s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7798] dhcp4 (wlp7s0): canceled DHCP transaction
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33 on wlp7s0.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv6 with address 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7803] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.*.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7803] dhcp4 (wlp7s0): state changed no lease
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7805] dhcp6 (wlp7s0): canceled DHCP transaction
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7805] dhcp6 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Interface wlp7s0.IPv6 no longer relevant for mDNS.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7806] dhcp6 (wlp7s0): state changed no lease
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Interface wlp7s0.IPv4 no longer relevant for mDNS.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.12 on wlp7s0.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.7891] device (wlp7s0): set-hw-addr: set MAC address to 2E:63:70:0E:00:45 (scanning)
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: New relevant interface wlp7s0.IPv4 for mDNS.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.12 on wlp7s0.IPv4.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.12 on wlp7s0.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:14:07 $HOSTNAME avahi-daemon[665]: Interface wlp7s0.IPv4 no longer relevant for mDNS.
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.8399] device (wlp7s0): supplicant interface state: disconnected -> interface_disabled
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.8401] device (wlp7s0): supplicant interface state: interface_disabled -> disconnected
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.8402] device (wlp7s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jun 30 01:14:07 $HOSTNAME NetworkManager[663]: <info>  [1751238847.8606] device (wlp7s0): set-hw-addr: reset MAC address to 10:63:C8:76:2B:EB (unmanage)
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: p2p-dev-wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: p2p-dev-wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: nl80211: deinit ifname=p2p-dev-wlp7s0 disabled_11b_rates=0
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-DSCP-POLICY clear_all
Jun 30 01:14:07 $HOSTNAME wpa_supplicant[1019]: nl80211: deinit ifname=wlp7s0 disabled_11b_rates=0
Jun 30 01:14:08 $HOSTNAME systemd[1]: Reached target Sleep.
-- Subject: A start job for unit sleep.target has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit sleep.target has finished successfully.
-- 
-- The job identifier is 21284.
Jun 30 01:14:08 $HOSTNAME systemd[1]: Starting NVIDIA system suspend actions...
-- Subject: A start job for unit nvidia-suspend.service has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-suspend.service has begun execution.
-- 
-- The job identifier is 21287.
Jun 30 01:14:08 $HOSTNAME suspend[43229]: nvidia-suspend.service
Jun 30 01:14:08 $HOSTNAME logger[43229]: <13>Jun 30 01:14:08 suspend: nvidia-suspend.service
Jun 30 01:14:09 $HOSTNAME systemd[1]: nvidia-suspend.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit nvidia-suspend.service has successfully entered the 'dead' state.
Jun 30 01:14:09 $HOSTNAME systemd[1]: Finished NVIDIA system suspend actions.
-- Subject: A start job for unit nvidia-suspend.service has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-suspend.service has finished successfully.
-- 
-- The job identifier is 21287.
Jun 30 01:14:09 $HOSTNAME systemd[1]: Starting System Suspend...
-- Subject: A start job for unit systemd-suspend.service has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit systemd-suspend.service has begun execution.
-- 
-- The job identifier is 21283.
Jun 30 01:14:09 $HOSTNAME systemd-sleep[43241]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jun 30 01:14:09 $HOSTNAME systemd-sleep[43241]: This is not recommended, and might result in unexpected behavior, particularly
Jun 30 01:14:09 $HOSTNAME systemd-sleep[43241]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jun 30 01:14:09 $HOSTNAME systemd-sleep[43241]: Performing sleep operation 'suspend'...
-- Subject: System sleep state suspend entered
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The system has now entered the suspend sleep state.
Jun 30 01:14:09 $HOSTNAME kernel: PM: suspend entry (deep)
Jun 30 01:14:09 $HOSTNAME kernel: Filesystems sync: 0.022 seconds
Jun 30 01:30:31 $HOSTNAME kernel: Freezing user space processes
Jun 30 01:30:31 $HOSTNAME kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jun 30 01:30:31 $HOSTNAME kernel: OOM killer disabled.
Jun 30 01:30:31 $HOSTNAME kernel: Freezing remaining freezable tasks
Jun 30 01:30:31 $HOSTNAME kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Jun 30 01:30:31 $HOSTNAME kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 30 01:30:31 $HOSTNAME kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jun 30 01:30:31 $HOSTNAME kernel: ata5.00: Entering standby power mode
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: EC: interrupt blocked
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: PM: Preparing to enter system sleep state S3
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: EC: event blocked
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: EC: EC stopped
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: PM: Saving platform NVS memory
Jun 30 01:30:31 $HOSTNAME kernel: Disabling non-boot CPUs ...
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 7 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 6 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 5 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 4 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 3 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 2 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: CPU 1 is now offline
Jun 30 01:30:31 $HOSTNAME kernel: [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -755551990. Restoring
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: PM: Low-level resume complete
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: EC: EC started
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: PM: Restoring platform NVS memory
Jun 30 01:30:31 $HOSTNAME kernel: Enabling non-boot CPUs ...
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jun 30 01:30:31 $HOSTNAME kernel: CPU1 is up
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jun 30 01:30:31 $HOSTNAME kernel: CPU2 is up
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jun 30 01:30:31 $HOSTNAME kernel: CPU3 is up
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Jun 30 01:30:31 $HOSTNAME kernel: CPU4 is up
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Jun 30 01:30:31 $HOSTNAME kernel: CPU5 is up
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Jun 30 01:30:31 $HOSTNAME kernel: CPU6 is up
Jun 30 01:30:31 $HOSTNAME kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Jun 30 01:30:31 $HOSTNAME kernel: CPU7 is up
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: PM: Waking up from system sleep state S3
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: EC: interrupt unblocked
Jun 30 01:30:31 $HOSTNAME kernel: i2c_designware i2c_designware.0: timeout while trying to abort current transfer
Jun 30 01:30:31 $HOSTNAME kernel: i2c_designware i2c_designware.0: timeout in disabling adapter
Jun 30 01:30:31 $HOSTNAME kernel: ACPI: EC: event unblocked
Jun 30 01:30:31 $HOSTNAME kernel: nvme nvme0: 8/0/0 default/read/poll queues
Jun 30 01:30:31 $HOSTNAME kernel: usb 1-8: reset high-speed USB device number 3 using xhci_hcd
Jun 30 01:30:31 $HOSTNAME kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
Jun 30 01:30:31 $HOSTNAME kernel: OOM killer enabled.
Jun 30 01:30:31 $HOSTNAME kernel: Restarting tasks ... 
Jun 30 01:30:31 $HOSTNAME kernel: i2c_designware i2c_designware.0: timeout while trying to abort current transfer
Jun 30 01:30:31 $HOSTNAME kernel: done.
Jun 30 01:30:31 $HOSTNAME kernel: random: crng reseeded on system resumption
Jun 30 01:30:31 $HOSTNAME kernel: i2c_designware i2c_designware.0: timeout in disabling adapter
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.731 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-082ee5a7-7c25-470a-9643-0c06f0466ea1: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.742 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.753 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME systemd-sleep[43241]: System returned from sleep operation 'suspend'.
-- Subject: System sleep state suspend left
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The system has now left the suspend sleep state.
Jun 30 01:30:31 $HOSTNAME kernel: PM: suspend exit
Jun 30 01:30:31 $HOSTNAME kernel: pci_bus 0000:01: Allocating resources
Jun 30 01:30:31 $HOSTNAME kernel: pci_bus 0000:06: Allocating resources
Jun 30 01:30:31 $HOSTNAME kernel: pci_bus 0000:07: Allocating resources
Jun 30 01:30:31 $HOSTNAME kernel: pci_bus 0000:08: Allocating resources
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.765 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-5565a099-7fe2-45c1-a22b-d7e9dfea9a2e: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.777 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-3c4852d6-d47b-4f46-b05e-b5edc1aa440e: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.788 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-8c2f4425-77d6-4755-aca3-891fdbc66a58: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.799 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-dba4d603-d7ed-4931-8823-17ad585705d5: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.814 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-42b3ce2f-bd9f-485a-96ae-26406230b1ff: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.828 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-f908627d-13bf-4a04-b91f-a64e9245323d: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.839 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-55213584-9a29-4916-badf-0fb7ed682aeb: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.850 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-309dcde8-ccb1-4062-8f78-600115a34327: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:31 $HOSTNAME fwupd[26622]: 23:30:31.861 FuEngine             failed to add device /sys/devices/pci0000:00/0000:00:16.0/0000:00:16.0-8e6a6715-9abc-4043-88ef-9e39c6f63e0f: failed to setup: failed to connect: 1d10887a051b3991a3314f760163248231628504 [BootGuard Configuration] has not been opened
Jun 30 01:30:32 $HOSTNAME kernel: ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Jun 30 01:30:32 $HOSTNAME kernel: sd 4:0:0:0: [sda] Starting disk
Jun 30 01:30:32 $HOSTNAME kernel: ata5.00: configured for UDMA/133
Jun 30 01:30:32 $HOSTNAME pulseaudio[1220]: Failed to create sink input: sink is suspended.
Jun 30 01:30:32 $HOSTNAME systemd[1]: systemd-suspend.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit systemd-suspend.service has successfully entered the 'dead' state.
Jun 30 01:30:32 $HOSTNAME systemd[1]: Finished System Suspend.
-- Subject: A start job for unit systemd-suspend.service has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit systemd-suspend.service has finished successfully.
-- 
-- The job identifier is 21283.
Jun 30 01:30:32 $HOSTNAME systemd[1]: systemd-suspend.service: Consumed 1.412s CPU time, 9.3M memory peak.
-- Subject: Resources consumed by unit runtime
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit systemd-suspend.service completed and consumed the indicated resources.
Jun 30 01:30:32 $HOSTNAME systemd[1]: Stopped target Sleep.
-- Subject: A stop job for unit sleep.target has finished
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A stop job for unit sleep.target has finished.
-- 
-- The job identifier is 21445 and the job result is done.
Jun 30 01:30:32 $HOSTNAME systemd[1]: Reached target Suspend.
-- Subject: A start job for unit suspend.target has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit suspend.target has finished successfully.
-- 
-- The job identifier is 21282.
Jun 30 01:30:32 $HOSTNAME systemd[1]: Starting NVIDIA system resume actions...
-- Subject: A start job for unit nvidia-resume.service has begun execution
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-resume.service has begun execution.
-- 
-- The job identifier is 21444.
Jun 30 01:30:32 $HOSTNAME systemd[1]: Stopped target Suspend.
-- Subject: A stop job for unit suspend.target has finished
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A stop job for unit suspend.target has finished.
-- 
-- The job identifier is 21450 and the job result is done.
Jun 30 01:30:32 $HOSTNAME systemd-logind[673]: Operation 'suspend' finished.
Jun 30 01:30:32 $HOSTNAME ModemManager[747]: <msg> [sleep-monitor-systemd] system is resuming
Jun 30 01:30:32 $HOSTNAME bluetoothd[666]: Failed to set mode: Failed (0x03)
Jun 30 01:30:32 $HOSTNAME kded6[1190]: kf.bluezqt: PendingCall Error: "Failed"
Jun 30 01:30:32 $HOSTNAME NetworkManager[663]: <info>  [1751239832.5499] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jun 30 01:30:32 $HOSTNAME NetworkManager[663]: <info>  [1751239832.5500] device (enp8s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:30:32 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:30:32 qt.bluetooth.bluez: Bluetooth device is powered off
Jun 30 01:30:32 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:30:32 default: Error sending UDP packet: QAbstractSocket::NetworkError
Jun 30 01:30:32 $HOSTNAME suspend[43683]: nvidia-resume.service
Jun 30 01:30:32 $HOSTNAME logger[43683]: <13>Jun 30 01:30:32 suspend: nvidia-resume.service
Jun 30 01:30:32 $HOSTNAME kernel: Generic FE-GE Realtek PHY r8169-0-800:00: attached PHY driver (mii_bus:phy_addr=r8169-0-800:00, irq=MAC)
Jun 30 01:30:32 $HOSTNAME systemd[1]: nvidia-resume.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit nvidia-resume.service has successfully entered the 'dead' state.
Jun 30 01:30:32 $HOSTNAME systemd[1]: Finished NVIDIA system resume actions.
-- Subject: A start job for unit nvidia-resume.service has finished successfully
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- A start job for unit nvidia-resume.service has finished successfully.
-- 
-- The job identifier is 21444.
Jun 30 01:30:32 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:30:32 kdeconnect.core: Failed to open any MDNS client sockets
Jun 30 01:30:32 $HOSTNAME kdeconnectd[1432]: 2025-06-30T01:30:32 kdeconnect.core: Failed to open any MDNS server sockets
Jun 30 01:30:32 $HOSTNAME NetworkManager[663]: <info>  [1751239832.7231] device (wlp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:30:32 $HOSTNAME kernel: r8169 0000:08:00.0 enp8s0: Link is Down
Jun 30 01:30:32 $HOSTNAME NetworkManager[663]: <info>  [1751239832.8138] device (wlp7s0): set-hw-addr: set MAC address to 6A:48:85:26:C6:BD (scanning)
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.0977] device (p2p-dev-wlp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.0989] manager: NetworkManager state is now DISCONNECTED
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1511] device (wlp7s0): supplicant interface state: internal-starting -> disconnected
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1513] device (p2p-dev-wlp7s0): state change: unavailable -> unmanaged (reason 'unmanaged-link-not-init', managed-type: 'removed')
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1530] Wi-Fi P2P device controlled by interface wlp7s0 created
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1554] manager: (p2p-dev-wlp7s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/27)
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1572] device (p2p-dev-wlp7s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1613] device (wlp7s0): state change: unavailable -> disconnected (reason 'supplicant-available', managed-type: 'full')
Jun 30 01:30:33 $HOSTNAME NetworkManager[663]: <info>  [1751239833.1639] device (p2p-dev-wlp7s0): state change: unavailable -> disconnected (reason 'none', managed-type: 'full')
Jun 30 01:30:33 $HOSTNAME kcminit[43695]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_mouse.so"
Jun 30 01:30:33 $HOSTNAME kcminit[43695]: Initializing  "/usr/lib/qt6/plugins/plasma/kcms/systemsettings/kcm_touchpad.so"
Jun 30 01:30:33 $HOSTNAME kcminit[43695]: kcm_touchpad: Using X11 backend
Jun 30 01:30:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Jun 30 01:30:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=2472 max_tx_power=2000 no_ir=1
Jun 30 01:30:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=2472 max_tx_power=2000
Jun 30 01:30:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Jun 30 01:30:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-BEACON-HINT before freq=2472 max_tx_power=2000 no_ir=1
Jun 30 01:30:33 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-BEACON-HINT after freq=2472 max_tx_power=2000
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.1992] device (enp8s0): carrier: link connected
Jun 30 01:30:36 $HOSTNAME kernel: r8169 0000:08:00.0 enp8s0: Link is Up - 1Gbps/Full - flow control rx/tx
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2000] device (enp8s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2019] policy: auto-activating connection 'Connexion filaire 1' (0cbc36e3-6ae5-3d97-bb57-5420fe52a401)
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2032] device (enp8s0): Activation: starting connection 'Connexion filaire 1' (0cbc36e3-6ae5-3d97-bb57-5420fe52a401)
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2033] device (enp8s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2041] manager: NetworkManager state is now CONNECTING
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2046] device (enp8s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2063] device (enp8s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 30 01:30:36 $HOSTNAME NetworkManager[663]: <info>  [1751239836.2083] dhcp4 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:30:36 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:30:36 $HOSTNAME avahi-daemon[665]: New relevant interface enp8s0.IPv6 for mDNS.
Jun 30 01:30:36 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::854c:ff60:14ab:74b7 on enp8s0.*.
Jun 30 01:30:36 $HOSTNAME ModemManager[747]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.4/0000:07:00.0': not supported by any plugin
Jun 30 01:30:36 $HOSTNAME ModemManager[747]: <msg> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1d.5/0000:08:00.0': not supported by any plugin
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0327] policy: auto-activating connection 'Livebox-EDE0' (fdb79a2e-59e2-48d1-b522-627ea43c61cf)
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0342] device (wlp7s0): Activation: starting connection 'Livebox-EDE0' (fdb79a2e-59e2-48d1-b522-627ea43c61cf)
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0349] device (wlp7s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0451] device (wlp7s0): set-hw-addr: reset MAC address to 10:63:C8:76:2B:EB (preserve)
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0516] device (wlp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0523] device (wlp7s0): Activation: (wifi) access point 'Livebox-EDE0' has security, but secrets are required.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0524] device (wlp7s0): state change: config -> need-auth (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0528] sup-iface[af6267c814ad00d5,23,wlp7s0]: wps: type pbc start...
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0541] device (wlp7s0): supplicant interface state: disconnected -> interface_disabled
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0542] device (p2p-dev-wlp7s0): supplicant management interface state: disconnected -> interface_disabled
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0569] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0570] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPS-PBC-ACTIVE
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0645] device (wlp7s0): supplicant interface state: inactive -> scanning
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0647] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> scanning
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0945] device (wlp7s0): state change: need-auth -> prepare (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0955] device (wlp7s0): state change: prepare -> config (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0962] device (wlp7s0): Activation: (wifi) connection 'Livebox-EDE0' has security, and secrets exist.  No new secrets needed.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0963] Config: added 'ssid' value 'Livebox-EDE0'
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0963] Config: added 'scan_ssid' value '1'
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0964] Config: added 'bgscan' value 'simple:30:-65:300'
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0965] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK SAE FT-SAE'
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPS-CANCEL
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.0965] Config: added 'psk' value '<hidden>'
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: SME: Trying to authenticate with b8:66:85:82:ed:e0 (SSID='Livebox-EDE0' freq=2412 MHz)
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: authenticate with b8:66:85:82:ed:e0 (local address=10:63:c8:76:2b:eb)
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: send auth to b8:66:85:82:ed:e0 (try 1/3)
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.1617] device (wlp7s0): supplicant interface state: scanning -> authenticating
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.1618] device (p2p-dev-wlp7s0): supplicant management interface state: scanning -> authenticating
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: authenticated
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Trying to associate with b8:66:85:82:ed:e0 (SSID='Livebox-EDE0' freq=2412 MHz)
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.1671] device (wlp7s0): supplicant interface state: authenticating -> associating
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: associate with b8:66:85:82:ed:e0 (try 1/3)
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.1672] device (p2p-dev-wlp7s0): supplicant management interface state: authenticating -> associating
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: RX AssocResp from b8:66:85:82:ed:e0 (capab=0x1411 status=0 aid=1)
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: associated
Jun 30 01:30:38 $HOSTNAME kernel: ath: EEPROM regdomain: 0x80fa
Jun 30 01:30:38 $HOSTNAME kernel: ath: EEPROM indicates we should expect a country code
Jun 30 01:30:38 $HOSTNAME kernel: ath: doing EEPROM country->regdmn map search
Jun 30 01:30:38 $HOSTNAME kernel: ath: country maps to regdmn code: 0x37
Jun 30 01:30:38 $HOSTNAME kernel: ath: Country alpha2 being used: FR
Jun 30 01:30:38 $HOSTNAME kernel: ath: Regpair used: 0x37
Jun 30 01:30:38 $HOSTNAME kernel: ath: regdomain 0x80fa dynamically updated by country element
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Associated with b8:66:85:82:ed:e0
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:30:38 $HOSTNAME kernel: wlp7s0: Limiting TX power to 20 (20 - 0) dBm as advertised by b8:66:85:82:ed:e0
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.1841] device (wlp7s0): supplicant interface state: associating -> associated
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.1842] device (p2p-dev-wlp7s0): supplicant management interface state: associating -> associated
Jun 30 01:30:38 $HOSTNAME systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2397] device (wlp7s0): supplicant interface state: associated -> 4way_handshake
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2398] device (p2p-dev-wlp7s0): supplicant management interface state: associated -> 4way_handshake
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2692] dhcp4 (enp8s0): state changed new lease, address=192.168.1.13, acd pending
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPA: Key negotiation completed with b8:66:85:82:ed:e0 [PTK=CCMP GTK=CCMP]
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-CONNECTED - Connection to b8:66:85:82:ed:e0 completed [id=0 id_str=]
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2812] device (wlp7s0): supplicant interface state: 4way_handshake -> completed
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2812] device (wlp7s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "Livebox-EDE0"
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2813] device (p2p-dev-wlp7s0): supplicant management interface state: 4way_handshake -> completed
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2818] device (wlp7s0): state change: config -> ip-config (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.2843] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: New relevant interface wlp7s0.IPv6 for mDNS.
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.*.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.3289] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12, acd pending
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.3916] dhcp4 (enp8s0): state changed new lease, address=192.168.1.13
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv4 with address 192.168.1.13.
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: New relevant interface enp8s0.IPv4 for mDNS.
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.13 on enp8s0.IPv4.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.3939] policy: set 'Connexion filaire 1' (enp8s0) as default for IPv4 routing and DNS
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.4079] device (enp8s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME 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 21451.
Jun 30 01:30:38 $HOSTNAME 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 21451.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.4693] device (enp8s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.4697] device (enp8s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.4712] device (enp8s0): Activation: successful, device activated.
Jun 30 01:30:38 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-31 noise=-113 txrate=0
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.4976] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv4 with address 192.168.1.12.
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: New relevant interface wlp7s0.IPv4 for mDNS.
Jun 30 01:30:38 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.12 on wlp7s0.IPv4.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5108] device (enp8s0): conflict detected for IP address 192.168.1.13 with host 10:63:C8:76:2B:EB
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5112] device (wlp7s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5243] device (wlp7s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5246] device (wlp7s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5255] manager: NetworkManager state is now CONNECTED_SITE
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5265] device (wlp7s0): Activation: successful, device activated.
Jun 30 01:30:38 $HOSTNAME NetworkManager[663]: <info>  [1751239838.5566] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 30 01:30:39 $HOSTNAME NetworkManager[663]: <info>  [1751239839.0168] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface enp8s0.IPv6 with address fe80::854c:ff60:14ab:74b7.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface enp8s0.IPv6 with address 2a01:cb05:9116:7400:f800:165f:dd1:7449.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for 2a01:cb05:9116:7400:f800:165f:dd1:7449 on enp8s0.*.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::854c:ff60:14ab:74b7 on enp8s0.
Jun 30 01:30:39 $HOSTNAME NetworkManager[663]: <info>  [1751239839.0194] policy: set 'Connexion filaire 1' (enp8s0) as default for IPv6 routing and DNS
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.12 on wlp7s0.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 192.168.1.13 on enp8s0.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Withdrawing address record for ::1 on lo.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Withdrawing address record for 127.0.0.1 on lo.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Host name conflict, retrying with $HOSTNAME-3
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.*.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.12 on wlp7s0.IPv4.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for 2a01:cb05:9116:7400:f800:165f:dd1:7449 on enp8s0.*.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for 192.168.1.13 on enp8s0.IPv4.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for ::1 on lo.*.
Jun 30 01:30:39 $HOSTNAME avahi-daemon[665]: Registering new address record for 127.0.0.1 on lo.IPv4.
Jun 30 01:30:39 $HOSTNAME NetworkManager[663]: <info>  [1751239839.0289] dhcp6 (enp8s0): state changed new lease
Jun 30 01:30:39 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WNM: Disassociation Imminent - Disassociation Timer 15
Jun 30 01:30:39 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WNM: Preferred List Available
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: SME: Trying to authenticate with b8:66:85:82:ed:e5 (SSID='Livebox-EDE0' freq=5500 MHz)
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: disconnect from AP b8:66:85:82:ed:e0 for new auth to b8:66:85:82:ed:e5
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: authenticate with b8:66:85:82:ed:e5 (local address=10:63:c8:76:2b:eb)
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: send auth to b8:66:85:82:ed:e5 (try 1/3)
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: authenticated
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.2485] device (wlp7s0): supplicant interface state: completed -> authenticating
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.2485] device (p2p-dev-wlp7s0): supplicant management interface state: completed -> authenticating
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Trying to associate with b8:66:85:82:ed:e5 (SSID='Livebox-EDE0' freq=5500 MHz)
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: associate with b8:66:85:82:ed:e5 (try 1/3)
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.2556] device (wlp7s0): supplicant interface state: authenticating -> associating
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.2556] device (p2p-dev-wlp7s0): supplicant management interface state: authenticating -> associating
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: RX ReassocResp from b8:66:85:82:ed:e5 (capab=0x1511 status=0 aid=56)
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: associated
Jun 30 01:30:40 $HOSTNAME kernel: ath: EEPROM regdomain: 0x80fa
Jun 30 01:30:40 $HOSTNAME kernel: ath: EEPROM indicates we should expect a country code
Jun 30 01:30:40 $HOSTNAME kernel: ath: doing EEPROM country->regdmn map search
Jun 30 01:30:40 $HOSTNAME kernel: ath: country maps to regdmn code: 0x37
Jun 30 01:30:40 $HOSTNAME kernel: ath: Country alpha2 being used: FR
Jun 30 01:30:40 $HOSTNAME kernel: ath: Regpair used: 0x37
Jun 30 01:30:40 $HOSTNAME kernel: ath: regdomain 0x80fa dynamically updated by country element
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: Associated with b8:66:85:82:ed:e5
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.2682] device (wlp7s0): supplicant interface state: associating -> associated
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.2682] device (p2p-dev-wlp7s0): supplicant management interface state: associating -> associated
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3152] device (wlp7s0): supplicant interface state: associated -> 4way_handshake
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3153] device (p2p-dev-wlp7s0): supplicant management interface state: associated -> 4way_handshake
Jun 30 01:30:40 $HOSTNAME kernel: wlp7s0: Limiting TX power to 25 (25 - 0) dBm as advertised by b8:66:85:82:ed:e5
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: WPA: Key negotiation completed with b8:66:85:82:ed:e5 [PTK=CCMP GTK=CCMP]
Jun 30 01:30:40 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-CONNECTED - Connection to b8:66:85:82:ed:e5 completed [id=0 id_str=]
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3570] device (wlp7s0): supplicant interface state: 4way_handshake -> completed
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3572] device (wlp7s0): ip:dhcp4: restarting
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3645] dhcp4 (wlp7s0): canceled DHCP transaction
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3646] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3646] dhcp4 (wlp7s0): state changed no lease
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3648] dhcp4 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3651] device (p2p-dev-wlp7s0): supplicant management interface state: 4way_handshake -> completed
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3830] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12, acd pending
Jun 30 01:30:40 $HOSTNAME NetworkManager[663]: <info>  [1751239840.3835] dhcp4 (wlp7s0): state changed new lease, address=192.168.1.12
Jun 30 01:30:40 $HOSTNAME avahi-daemon[665]: Server startup complete. Host name is $HOSTNAME-3.local. Local service cookie is 3093452386.
Jun 30 01:30:41 $HOSTNAME wpa_supplicant[1019]: wlp7s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-38 noise=-95 txrate=0
Jun 30 01:30:45 $HOSTNAME kglobalacceld[1141]: kf.globalaccel.kglobalacceld: KKeyServer::xcbKeyPressEventToQt failed
Jun 30 01:30:46 $HOSTNAME NetworkManager[663]: <info>  [1751239846.0570] dhcp6 (wlp7s0): activation: beginning transaction (timeout in 45 seconds)
Jun 30 01:30:46 $HOSTNAME avahi-daemon[665]: Leaving mDNS multicast group on interface wlp7s0.IPv6 with address fe80::16f2:7bc:f4cb:deac.
Jun 30 01:30:46 $HOSTNAME avahi-daemon[665]: Joining mDNS multicast group on interface wlp7s0.IPv6 with address 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33.
Jun 30 01:30:46 $HOSTNAME avahi-daemon[665]: Registering new address record for 2a01:cb05:9116:7400:6828:5d5a:b55b:ed33 on wlp7s0.*.
Jun 30 01:30:46 $HOSTNAME avahi-daemon[665]: Withdrawing address record for fe80::16f2:7bc:f4cb:deac on wlp7s0.
Jun 30 01:30:46 $HOSTNAME NetworkManager[663]: <info>  [1751239846.3709] dhcp6 (wlp7s0): state changed new lease
Jun 30 01:30:48 $HOSTNAME systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://forum.manjaro.org/c/support
-- 
-- The unit NetworkManager-dispatcher.service has successfully entered the 'dead' state.
Jun 30 01:30:50 $HOSTNAME kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jun 30 01:30:50 $HOSTNAME kernel: sd 4:0:0:0: [sda] Stopping disk

for good measure, output of dmesg:

[17866.537994] r8169 0000:08:00.0 enp8s0: Link is Down
[17866.543838] wlp7s0: deauthenticating from b8:66:85:82:ed:e5 by local choice (Reason: 3=DEAUTH_LEAVING)
[17867.704891] ------------[ cut here ]------------
[17867.704896] WARNING: CPU: 5 PID: 42696 at nvidia/nv.c:4648 nv_set_system_power_state+0x41e/0x480 [nvidia]
[17867.705518] Modules linked in: udp_diag tcp_diag inet_diag ccm rfcomm qrtr squashfs uhid cmac algif_hash algif_skcipher af_alg bnep uinput nvidia_uvm(POE) snd_sof_pci_intel_cnl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_acpi soundwire_bus intel_uncore_frequency snd_soc_sdca intel_uncore_frequency_common crc8 snd_soc_avs uvcvideo snd_soc_hda_codec intel_tcc_cooling snd_hda_ext_core x86_pkg_temp_thermal intel_powerclamp videobuf2_vmalloc coretemp snd_soc_core btusb uvc videobuf2_memops btrtl snd_hda_codec_realtek videobuf2_v4l2 snd_compress kvm_intel btintel snd_hda_codec_generic ac97_bus btbcm videobuf2_common btmtk videodev snd_hda_scodec_component ath10k_pci snd_pcm_dmaengine snd_hda_codec_hdmi kvm mc bluetooth snd_hda_intel snd_intel_dspcfg
[17867.705585]  ath10k_core irqbypass snd_intel_sdw_acpi polyval_clmulni polyval_generic joydev snd_hda_codec ath ghash_clmulni_intel sha512_ssse3 mousedev iTCO_wdt snd_hda_core processor_thermal_device_pci_legacy sha256_ssse3 intel_pmc_bxt processor_thermal_device intel_rapl_msr mac80211 sha1_ssse3 iTCO_vendor_support processor_thermal_wt_hint snd_hwdep aesni_intel processor_thermal_rfim r8169 crypto_simd snd_pcm processor_thermal_rapl 8250_dw cryptd intel_rapl_common realtek rapl nvidia_drm(POE) mei_hdcp mei_pxp mdio_devres snd_timer libarc4 i2c_i801 nvidia_modeset(POE) intel_cstate processor_thermal_wt_req vfat i2c_hid_acpi spi_nor snd mei_me processor_thermal_power_floor i2c_smbus intel_lpss_pci intel_uncore processor_thermal_mbox fat cfg80211 pcspkr intel_wmi_thunderbolt wmi_bmof libphy mtd i2c_mux ideapad_laptop drm_ttm_helper i2c_hid soundcore intel_lpss intel_pch_thermal intel_soc_dts_iosf mei idma64 elan_i2c platform_profile sparse_keymap int3403_thermal intel_pmc_core rfkill int340x_thermal_zone pmt_telemetry
[17867.705658]  pmt_class nvidia(POE) int3400_thermal pinctrl_cannonlake intel_vsec acpi_thermal_rel acpi_tad acpi_pad mac_hid sg crypto_user loop dm_mod nfnetlink ip_tables x_tables i915 i2c_algo_bit nvme drm_buddy ttm nvme_core spi_intel_pci intel_gtt serio_raw nvme_keyring spi_intel drm_display_helper nvme_auth cec video wmi
[17867.705691] CPU: 5 UID: 0 PID: 42696 Comm: nvidia-sleep.sh Tainted: P        W  OE       6.15.3-1-MANJARO #1 PREEMPT(full)  5e8b0697e5491c80c8a92bc22d4fbb4b85976c24
[17867.705697] Tainted: [P]=PROPRIETARY_MODULE, [W]=WARN, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
[17867.705699] Hardware name: LENOVO 81LK/LNVNB161216, BIOS BGCN36WW 05/24/2022
[17867.705702] RIP: 0010:nv_set_system_power_state+0x41e/0x480 [nvidia]
[17867.706190] Code: 75 0e eb 3f 48 8b ad d0 06 00 00 48 85 ed 74 33 48 8b bd 30 03 00 00 ba 01 00 00 00 44 89 e6 e8 08 c8 ff ff 89 c3 85 c0 74 da <0f> 0b 48 c7 c7 70 ff 17 c2 41 bc 01 00 00 00 e8 fe 12 72 f0 e9 ef
[17867.706193] RSP: 0018:ffffcff68a17ba68 EFLAGS: 00010202
[17867.706196] RAX: 0000000000000051 RBX: 0000000000000051 RCX: ffff8b0e04ce16b0
[17867.706198] RDX: ffff8b0e04ce16b0 RSI: 0000000000000282 RDI: ffff8b0e04ce16a8
[17867.706200] RBP: ffff8b0e04ce1000 R08: 0000000000000000 R09: ffffffffc1001bf4
[17867.706202] R10: ffff8b0ec1773000 R11: fffff7010705dc00 R12: 0000000000000001
[17867.706204] R13: 0000000000000000 R14: ffff8b0ec1773000 R15: ffff8b0e04ce16a8
[17867.706206] FS:  00007f1a95353b80(0000) GS:ffff8b0fb2e6f000(0000) knlGS:0000000000000000
[17867.706208] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[17867.706210] CR2: 00007f1a955ac7b0 CR3: 0000000167ece003 CR4: 00000000003726f0
[17867.706213] Call Trace:
[17867.706216]  <TASK>
[17867.706220]  nv_procfs_write_suspend+0xfe/0x180 [nvidia c550f7d9e312df76ef65d70bce47728b5f08ee0f]
[17867.706727]  proc_reg_write+0x57/0xb0
[17867.706735]  vfs_write+0xef/0x470
[17867.706743]  ksys_write+0x73/0xe0
[17867.706749]  do_syscall_64+0x7b/0x810
[17867.706759]  ? syscall_exit_to_user_mode+0x37/0x1c0
[17867.706762]  ? do_syscall_64+0x87/0x810
[17867.706766]  ? do_fcntl+0x442/0x840
[17867.706770]  ? do_syscall_64+0x87/0x810
[17867.706776]  ? __x64_sys_fcntl+0x90/0xf0
[17867.706779]  ? ptep_set_access_flags+0x32/0x40
[17867.706785]  ? wp_page_reuse+0x8d/0xa0
[17867.706790]  ? do_wp_page+0x925/0xed0
[17867.706794]  ? get_close_on_exec+0x34/0x40
[17867.706798]  ? do_fcntl+0x30b/0x840
[17867.706803]  ? __handle_mm_fault+0xae0/0xfd0
[17867.706806]  ? syscall_exit_to_user_mode+0x37/0x1c0
[17867.706811]  ? __count_memcg_events+0xb0/0x150
[17867.706814]  ? count_memcg_events.constprop.0+0x1a/0x30
[17867.706817]  ? handle_mm_fault+0x1d2/0x2d0
[17867.706821]  ? do_user_addr_fault+0x21a/0x690
[17867.706825]  ? irqentry_exit_to_user_mode+0x2c/0x1b0
[17867.706828]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[17867.706831] RIP: 0033:0x7f1a95456006
[17867.706859] Code: 5d e8 41 8b 93 08 03 00 00 59 5e 48 83 f8 fc 75 19 83 e2 39 83 fa 08 75 11 e8 26 ff ff ff 66 0f 1f 44 00 00 48 8b 45 10 0f 05 <48> 8b 5d f8 c9 c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 e5 48 83 ec 08
[17867.706861] RSP: 002b:00007fff2308a4e0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
[17867.706865] RAX: ffffffffffffffda RBX: 0000000000000008 RCX: 00007f1a95456006
[17867.706867] RDX: 0000000000000008 RSI: 000055e25c5956a0 RDI: 0000000000000001
[17867.706869] RBP: 00007fff2308a500 R08: 0000000000000000 R09: 0000000000000000
[17867.706870] R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000008
[17867.706872] R13: 000055e25c5956a0 R14: 00007f1a955ab5c0 R15: 0000000000000000
[17867.706877]  </TASK>
[17867.706879] ---[ end trace 0000000000000000 ]---
[17868.064640] PM: suspend entry (deep)
[17868.070297] Filesystems sync: 0.005 seconds
[17868.520195] Freezing user space processes
[17868.522437] Freezing user space processes completed (elapsed 0.002 seconds)
[17868.522443] OOM killer disabled.
[17868.522444] Freezing remaining freezable tasks
[17868.617537] Freezing remaining freezable tasks completed (elapsed 0.095 seconds)
[17868.617609] printk: Suspending console(s) (use no_console_suspend to debug)
[17868.633982] sd 4:0:0:0: [sda] Synchronizing SCSI cache
[17868.667858] ata5.00: Entering standby power mode
[17868.668898] NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
[17868.668902] nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
[17868.669483] nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
[17868.669488] nvidia 0000:01:00.0: PM: failed to suspend async: error -5
[17869.232573] PM: Some devices failed to suspend, or early wake event detected
[17869.253366] nvme nvme0: 8/0/0 default/read/poll queues
[17869.538286] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[17869.539187] sd 4:0:0:0: [sda] Starting disk
[17869.540108] ata5.00: configured for UDMA/133
[17869.540201] ata5.00: Entering active power mode
[17870.719315] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[17870.720210] OOM killer enabled.
[17870.720217] Restarting tasks ... done.
[17870.725390] random: crng reseeded on system resumption
[17870.791776] PM: suspend exit
[17870.791845] PM: suspend entry (s2idle)
[17870.798531] Filesystems sync: 0.006 seconds
[17871.283155] Freezing user space processes
[17871.287682] Freezing user space processes completed (elapsed 0.004 seconds)
[17871.287693] OOM killer disabled.
[17871.287697] Freezing remaining freezable tasks
[17871.289321] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
[17871.289330] printk: Suspending console(s) (use no_console_suspend to debug)
[17871.297708] sd 4:0:0:0: [sda] Synchronizing SCSI cache
[17871.301433] ata5.00: Entering standby power mode
[17871.306942] NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.
[17871.306952] nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
[17871.308138] nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
[17871.308149] nvidia 0000:01:00.0: PM: failed to suspend async: error -5
[17871.865088] PM: Some devices failed to suspend, or early wake event detected
[17872.170424] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[17872.171370] sd 4:0:0:0: [sda] Starting disk
[17872.172310] ata5.00: configured for UDMA/133
[17872.172406] ata5.00: Entering active power mode
[17873.358360] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[17873.359216] OOM killer enabled.
[17873.359222] Restarting tasks ... done.
[17873.364948] random: crng reseeded on system resumption
[17873.431543] PM: suspend exit
[17873.783492] Generic FE-GE Realtek PHY r8169-0-800:00: attached PHY driver (mii_bus:phy_addr=r8169-0-800:00, irq=MAC)
[17873.935470] r8169 0000:08:00.0 enp8s0: Link is Down
[17876.816445] r8169 0000:08:00.0 enp8s0: Link is Up - 1Gbps/Full - flow control rx/tx
[17878.927432] wlp7s0: authenticate with b8:66:85:82:ed:e0 (local address=10:63:c8:76:2b:eb)
[17878.927437] wlp7s0: send auth to b8:66:85:82:ed:e0 (try 1/3)
[17878.929349] wlp7s0: authenticated
[17878.931285] wlp7s0: associate with b8:66:85:82:ed:e0 (try 1/3)
[17878.936179] wlp7s0: RX AssocResp from b8:66:85:82:ed:e0 (capab=0x1411 status=0 aid=1)
[17878.939091] wlp7s0: associated
[17878.939398] ath: EEPROM regdomain: 0x80fa
[17878.939406] ath: EEPROM indicates we should expect a country code
[17878.939410] ath: doing EEPROM country->regdmn map search
[17878.939413] ath: country maps to regdmn code: 0x37
[17878.939416] ath: Country alpha2 being used: FR
[17878.939419] ath: Regpair used: 0x37
[17878.939423] ath: regdomain 0x80fa dynamically updated by country element
[17878.970562] wlp7s0: Limiting TX power to 20 (20 - 0) dBm as advertised by b8:66:85:82:ed:e0
[17880.393528] wlp7s0: disconnect from AP b8:66:85:82:ed:e0 for new auth to b8:66:85:82:ed:e5
[17880.455159] wlp7s0: authenticate with b8:66:85:82:ed:e5 (local address=10:63:c8:76:2b:eb)
[17880.455167] wlp7s0: send auth to b8:66:85:82:ed:e5 (try 1/3)
[17880.456235] wlp7s0: authenticated
[17880.459284] wlp7s0: associate with b8:66:85:82:ed:e5 (try 1/3)
[17880.462640] wlp7s0: RX ReassocResp from b8:66:85:82:ed:e5 (capab=0x1511 status=0 aid=55)
[17880.465329] wlp7s0: associated
[17880.465503] ath: EEPROM regdomain: 0x80fa
[17880.465505] ath: EEPROM indicates we should expect a country code
[17880.465507] ath: doing EEPROM country->regdmn map search
[17880.465508] ath: country maps to regdmn code: 0x37
[17880.465510] ath: Country alpha2 being used: FR
[17880.465511] ath: Regpair used: 0x37
[17880.465513] ath: regdomain 0x80fa dynamically updated by country element
[17880.514952] wlp7s0: Limiting TX power to 25 (25 - 0) dBm as advertised by b8:66:85:82:ed:e5
[17974.313222] r8169 0000:08:00.0 enp8s0: Link is Down
[17974.318962] wlp7s0: deauthenticating from b8:66:85:82:ed:e5 by local choice (Reason: 3=DEAUTH_LEAVING)
[17976.016446] PM: suspend entry (deep)
[17976.039342] Filesystems sync: 0.022 seconds
[17976.174255] Freezing user space processes
[17976.175658] Freezing user space processes completed (elapsed 0.001 seconds)
[17976.175662] OOM killer disabled.
[17976.175664] Freezing remaining freezable tasks
[17976.176608] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[17976.176669] printk: Suspending console(s) (use no_console_suspend to debug)
[17976.199074] sd 4:0:0:0: [sda] Synchronizing SCSI cache
[17976.232842] ata5.00: Entering standby power mode
[17976.827338] ACPI: EC: interrupt blocked
[17976.925902] ACPI: PM: Preparing to enter system sleep state S3
[17976.927652] ACPI: EC: event blocked
[17976.927656] ACPI: EC: EC stopped
[17976.927657] ACPI: PM: Saving platform NVS memory
[17976.927831] Disabling non-boot CPUs ...
[17976.930645] smpboot: CPU 7 is now offline
[17976.933283] smpboot: CPU 6 is now offline
[17976.936052] smpboot: CPU 5 is now offline
[17976.938874] smpboot: CPU 4 is now offline
[17976.942131] smpboot: CPU 3 is now offline
[17976.944703] smpboot: CPU 2 is now offline
[17976.947336] smpboot: CPU 1 is now offline
[17204.578367] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -755551990. Restoring
[17976.953847] ACPI: PM: Low-level resume complete
[17976.953922] ACPI: EC: EC started
[17976.953923] ACPI: PM: Restoring platform NVS memory
[17976.955004] Enabling non-boot CPUs ...
[17976.955046] smpboot: Booting Node 0 Processor 1 APIC 0x2
[17976.958726] CPU1 is up
[17976.958753] smpboot: Booting Node 0 Processor 2 APIC 0x4
[17976.961790] CPU2 is up
[17976.961814] smpboot: Booting Node 0 Processor 3 APIC 0x6
[17976.964822] CPU3 is up
[17976.964846] smpboot: Booting Node 0 Processor 4 APIC 0x1
[17976.965719] CPU4 is up
[17976.965743] smpboot: Booting Node 0 Processor 5 APIC 0x3
[17976.966476] CPU5 is up
[17976.966499] smpboot: Booting Node 0 Processor 6 APIC 0x5
[17976.967227] CPU6 is up
[17976.967248] smpboot: Booting Node 0 Processor 7 APIC 0x7
[17976.968010] CPU7 is up
[17976.970749] ACPI: PM: Waking up from system sleep state S3
[17976.975285] ACPI: EC: interrupt unblocked
[17978.172078] i2c_designware i2c_designware.0: timeout while trying to abort current transfer
[17978.197382] i2c_designware i2c_designware.0: timeout in disabling adapter
[17978.197588] ACPI: EC: event unblocked
[17978.209114] nvme nvme0: 8/0/0 default/read/poll queues
[17978.485556] usb 1-8: reset high-speed USB device number 3 using xhci_hcd
[17978.643496] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_ops [i915])
[17978.645560] OOM killer enabled.
[17978.645566] Restarting tasks ... 
[17978.645922] i2c_designware i2c_designware.0: timeout while trying to abort current transfer
[17978.648447] done.
[17978.648475] random: crng reseeded on system resumption
[17978.673416] i2c_designware i2c_designware.0: timeout in disabling adapter
[17978.715679] PM: suspend exit
[17978.716992] pci_bus 0000:01: Allocating resources
[17978.719679] pci_bus 0000:06: Allocating resources
[17978.719707] pci_bus 0000:07: Allocating resources
[17978.719829] pci_bus 0000:08: Allocating resources
[17979.064687] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[17979.193551] sd 4:0:0:0: [sda] Starting disk
[17979.194648] ata5.00: configured for UDMA/133
[17979.526411] Generic FE-GE Realtek PHY r8169-0-800:00: attached PHY driver (mii_bus:phy_addr=r8169-0-800:00, irq=MAC)
[17979.677616] r8169 0000:08:00.0 enp8s0: Link is Down
[17983.153511] r8169 0000:08:00.0 enp8s0: Link is Up - 1Gbps/Full - flow control rx/tx
[17985.115489] wlp7s0: authenticate with b8:66:85:82:ed:e0 (local address=10:63:c8:76:2b:eb)
[17985.115507] wlp7s0: send auth to b8:66:85:82:ed:e0 (try 1/3)
[17985.117476] wlp7s0: authenticated
[17985.121442] wlp7s0: associate with b8:66:85:82:ed:e0 (try 1/3)
[17985.128218] wlp7s0: RX AssocResp from b8:66:85:82:ed:e0 (capab=0x1411 status=0 aid=1)
[17985.131737] wlp7s0: associated
[17985.131922] ath: EEPROM regdomain: 0x80fa
[17985.131929] ath: EEPROM indicates we should expect a country code
[17985.131934] ath: doing EEPROM country->regdmn map search
[17985.131937] ath: country maps to regdmn code: 0x37
[17985.131942] ath: Country alpha2 being used: FR
[17985.131946] ath: Regpair used: 0x37
[17985.131950] ath: regdomain 0x80fa dynamically updated by country element
[17985.134182] wlp7s0: Limiting TX power to 20 (20 - 0) dBm as advertised by b8:66:85:82:ed:e0
[17987.147896] wlp7s0: disconnect from AP b8:66:85:82:ed:e0 for new auth to b8:66:85:82:ed:e5
[17987.200312] wlp7s0: authenticate with b8:66:85:82:ed:e5 (local address=10:63:c8:76:2b:eb)
[17987.200326] wlp7s0: send auth to b8:66:85:82:ed:e5 (try 1/3)
[17987.201488] wlp7s0: authenticated
[17987.209438] wlp7s0: associate with b8:66:85:82:ed:e5 (try 1/3)
[17987.213140] wlp7s0: RX ReassocResp from b8:66:85:82:ed:e5 (capab=0x1511 status=0 aid=56)
[17987.216297] wlp7s0: associated
[17987.216535] ath: EEPROM regdomain: 0x80fa
[17987.216542] ath: EEPROM indicates we should expect a country code
[17987.216545] ath: doing EEPROM country->regdmn map search
[17987.216548] ath: country maps to regdmn code: 0x37
[17987.216552] ath: Country alpha2 being used: FR
[17987.216556] ath: Regpair used: 0x37
[17987.216560] ath: regdomain 0x80fa dynamically updated by country element
[17987.276819] wlp7s0: Limiting TX power to 25 (25 - 0) dBm as advertised by b8:66:85:82:ed:e5
[17997.434666] sd 4:0:0:0: [sda] Synchronizing SCSI cache
[17997.435164] sd 4:0:0:0: [sda] Stopping disk

inxi -zv1 (I don’t see why more verbose is useful by default)

System:
  Kernel: 6.15.3-1-MANJARO arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.3.5 Distro: Manjaro Linux
CPU:
  Info: quad core Intel Core i5-9300H [MT MCP] speed (MHz): avg: 800
    min/max: 800/2400
Graphics:
  Device-1: Intel CoffeeLake-H GT2 [UHD Graphics 630] driver: i915 v: kernel
  Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: nvidia
    v: 575.64
  Device-3: Chicony Integrated Camera (1280x720@30) driver: uvcvideo
    type: USB
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8 driver: X:
    loaded: modesetting,nvidia unloaded: nouveau dri: iris gpu: i915
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 25.1.4-arch1.1
    renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-smi wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Drives:
  Local Storage: total: 1.38 TiB used: 471.14 GiB (33.5%)
Info:
  Memory: total: 8 GiB available: 7.62 GiB used: 5.75 GiB (75.4%)
  Processes: 312 Uptime: 6h 3m Shell: Zsh inxi: 3.3.38

I’m available for more info and more experiments

Please provide system information as described (below).

Regards.


Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with Forum requirements, and the many ways to use the forum to your benefit:


Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command with appropriate parameters will achieve this (naturally, formatted according to forum guidelines) and will generally be more useful for those wishing to help:

inxi --filter --verbosity=8

or the short form:

inxi -zv8

Be prepared to provide output from other commands whenever asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Highly Recommended
Required Reading
Technical Resources

I already provided inxi -zv1, I can’t find what output you need. I don’t want to provide inxi -zv8 for no reason because, even if “filtered”, it still contains too much information to my liking

There’s usually a reason. In this case, the information will allow others to quickly note any possible contributors to your issue that may be revealed from the information given.

Without it, you are only limiting the scope of others who might wish to help, without playing the game of 100 questions.

Very few others have any difficulty providing that same information. Personally identifiable information is filtered by the command; this includes hardware serial numbers, user names, and more; as described in the inxi man page (link previously given).

There is no logical reason for you to withhold the information requested, whether or not it’s to your liking. I imagine not being able to enter sleep mode with too many programs running is also not to your liking.

That said, one could argue that you have a right to only share minimal information, whether or not it’s actually useful.

Members are here to help if they can, but only if you help them to help you. On that note, I’ll simply wish you luck.

I’m sure someone else will offer to help when they are able.

Regards.

3 Likes

I can’t see anything obvious in the logs, but perhaps I just missed it.

Have you read this :arrow_down:?

https://wiki.archlinux.org/title/NVIDIA/Tips_and_tricks#Preserve_video_memory_after_suspend

I do have PreserveVideoMemoryAllocations: 1 and TemporaryFilePath: "/var/tmp"

Have you read the rest? Files system compatibility, etc.

You could try without it, and enable/disable the systemd services to see if it changes anything.

One suggestion I haven’t seen mentioned yet is a process of elimination:

Close one program at a time; when suspend works, try with just that program running and see if it stalls.

1 Like

Have you read the rest? Files system compatibility, etc.

/ is ext4, I should have enough room, it has worked well in the past (I should have said that earlier)

I’m not sure I’m confident enough to edit kernel options though

Close one program at a time; when suspend works, try with just that program running and see if it stalls.

I tried that already, but it’s not one specific program or set of programs (e.g. KeePassXC doesn’t seem to cause issues on its own, Firefox always seems to block, Dolphin doesn’t block on its own but does when KeePassXC also runs)

Many Linux forums routinely ask for inxi -zv8 because it’s the fastest way to diagnose obscure issues… but if you’re worried about anything specific, how about a more pragmatic approach:

Obliterate any MACs, IPs, and UUIDs before posting.

inxi -zv8 | grep -vE 'MAC|UUID|IP'

Is that better?

1 Like

Even without that overly paranoid step, the filtered inxi output should have been more than adequate.

I might add that completing the forum profile (hardware related information) would also be generally useful for those wishing to help.

I note that there isn’t an overly large percentage of available RAM, and how much that, together with available swap, may be contibuting to the OP’s issue can’t be known easily, as they refuse to provide the information.

Additionally, they speak of entering “sleep mode” which doesn’t specifically state whether they mean Suspend to RAM or Hibernation; another important distinction.

Much of this might have been made obvious with full information provided from the onset. :man_shrugging:

Alas, perhaps I somehow misunderstood the OP’s comment;

2 Likes

When you are using a discrete GPU allocating swap to the safe side, the calculation could be

ram * 2 + gpu

So when your system is 8GB ram and say GPU is 4GB it would be

8 * 2 + 4 = 20GB

You can read more on the interweb

The following inxi command will provide basic information including swap

  • -F is basic system info
  • -z is filter
  • -c0 is removing color

and upload to a pastbin - where it will be removed after 30d (720h)

inxi -Fzc0 | curl -F 'file=@-' -Fexpires=720 https://0x0.st
1 Like

My mind was on RAM/SWAP availability too; if the OP is too afraid to provide decent system info, maybe this will help without revealing anything else other than the aforementioned:

free -h
1 Like

It seems to be suspend.

1 Like
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 10 GiB used: 266.7 MiB (2.6%)
    priority: -2 dev: <somewhere (NVME)> maj-min: 259:9 label: N/A
    uuid: <>

I did mean suspend to RAM. However, hibernation has never worked, so I’m also interested in ideas to fix that.

I did some more tests, opening a REPL and allocating stuff to fill the RAM, and it does appear to be related. Enough used RAM consistently blocks suspension, with a threshold around 86% (6.5GB).
However, when filling the RAM with regular programs instead (Firefox and 4 different electron-based programs), the threshold is lowered slightly (maybe loading some webpage used the GPU).

Unless you want to constantly monitor what you have loaded in memory, I’d suggest you might need to reach for your wallet and add additional RAM.

A total of 16GB RAM might improve your situation greatly.

Regards.

3 Likes

Is there really no issue to investigate? Is it normal that suspension fails silently and that an unexplained error trace appears in journalctl?
The issue disappears when I close the instance of VSCodium that I’m not using anyways, so I can live with this, but I’d like to report the issue to the place and people that can fix it

Not expected to be “normal” but certainly possible, if there’s no space left in memory to create the latest log entries before committing to disk? :thinking:

As for hibernate, a separate thread on that might be appropriate; we can likely help with that.

Let’s do some basic math, shall we?

Say you have 6.5 GB of data in RAM; some of it is the OS itself; the rest is comprised of every other application you have running, and whatever memory requirements they may have.

Now, you might think the remaining ~1.5 GB is plenty of overhead, but it really isn’t.

You mentioned having browsers open;

Every browser tab you have open uses more memory; Electron based applications are renowned for using excessive amounts of memory; Flatpak applications can use more memory; and so on.

There is an obvious correlation between how much RAM is used (or rather, how much is available) when you system tries to suspend (to RAM) and when that usage is high, it fails; other times it suspends normally.

You have already made the case, yourself; your system fails to suspend when it becomes low on resources; and that’s something that only you can control.

Looking for something else to blame equates to chasing ghosts, in my opinion. I can only repeat;


That said, you could also consider hibernating instead of suspending your system. It would be slower as data is written to swap instead of being held in RAM.

Plus, with only 8 GB of system RAM (and the greater percentage already being used) you would likely need to create a fairly sizable swap partition to compensate - off hand, I’d guess anywhere from 16 GB to 20 GB.

@linux-aarhus has already given you some links (above) which should be helpful, if you take that route.

We can only make suggestions; the rest is up to you.

Regards.

4 Likes

I have vague memories of suspend sometimes failing for me too. When my RAM was almost, but not quite full. So maybe there’s some overhead. :man_shrugging:

Whilst someone should probably check just in case it can be improved upon, there seems to be a practical limit that we need to work with.

Sometimes certain software can prevent a suspend, I remember having trouble with Unreal Engine 5 and Stable Diffusion. As they’re both RAM hungry, It may (or may not) be connected with the “limit”.

Anyway if you’re hitting 80-90% regularly then you probably need more RAM, especially if it gets in the way of doing things. Either that or you have to adapt your use to the lack of RAM.

The 10GiB that they already have should do, but it depends. :man_shrugging: