After wake-up system sleeps immediately

Support
1

I am (still) experiencing that my system goes back to sleep after waking up from a keypress or mouse click:

  • after waking up it sleeps again within a second, the screen stays black
  • and then a second keypress does wake up the system.

See below for an excerpt from the log files, selected on ‘systemd’.

16.04.2025 21:29:28:162	systemd-logind	The system will suspend now!
16.04.2025 21:29:28:165	systemd	Reached target Sleep.
16.04.2025 21:29:28:168	systemd	Starting System Suspend...
16.04.2025 21:29:28:204	systemd	session-1.scope: Unit now frozen-by-parent.
16.04.2025 21:29:28:204	systemd	user@1000.service: Unit now frozen-by-parent.
16.04.2025 21:29:28:204	systemd	user-1000.slice: Unit now frozen-by-parent.
16.04.2025 21:29:28:204	systemd	user.slice: Unit now frozen.
16.04.2025 21:29:28:204	systemd-sleep	Successfully froze unit 'user.slice'.
16.04.2025 21:29:28:206	systemd-sleep	Performing sleep operation 'suspend'...

17.04.2025 10:04:54:072	systemd-sleep	System returned from sleep operation 'suspend'.
17.04.2025 10:04:54:083	systemd	user.slice: Unit now thawed.
17.04.2025 10:04:54:084	systemd	user-1000.slice: Unit now thawed.
17.04.2025 10:04:54:084	systemd	user@1000.service: Unit now thawed.
17.04.2025 10:04:54:085	systemd	session-1.scope: Unit now thawed.
17.04.2025 10:04:54:085	systemd-sleep	Successfully thawed unit 'user.slice'.
17.04.2025 10:04:54:085	systemd	Starting Network Manager Wait Online...
17.04.2025 10:04:54:085	systemd	Starting Rotate log files...
17.04.2025 10:04:54:085	systemd	Starting Daily man-db regeneration...
17.04.2025 10:04:54:085	systemd	Started Verify integrity of password and group files.
17.04.2025 10:04:54:085	systemd	systemd-suspend.service: Deactivated successfully.
17.04.2025 10:04:54:131	systemd	Finished System Suspend.
17.04.2025 10:04:54:143	systemd	Finished Network Manager Wait Online.
17.04.2025 10:04:54:146	systemd	Reached target Network is Online.
17.04.2025 10:04:54:147	systemd	Stopped target Sleep.
17.04.2025 10:04:54:147	systemd	Reached target Suspend.
17.04.2025 10:04:54:147	systemd-logind	Operation 'suspend' finished.
17.04.2025 10:04:54:171	systemd	Starting Generate mirrorlist...
17.04.2025 10:04:54:171	systemd	Stopped target Suspend.
17.04.2025 10:04:54:174	systemd	Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
17.04.2025 10:04:54:176	systemd	logrotate.service: Deactivated successfully.
17.04.2025 10:04:54:190	systemd	Finished Rotate log files.
17.04.2025 10:04:54:191	systemd	shadow.service: Deactivated successfully.
17.04.2025 10:04:54:217	systemd-logind	The system will suspend now!
17.04.2025 10:04:54:391	systemd	Starting Network Manager Script Dispatcher Service...
17.04.2025 10:04:54:420	systemd	Started Network Manager Script Dispatcher Service.
17.04.2025 10:04:54:576	systemd	Reached target Sleep.
17.04.2025 10:04:54:578	systemd	Starting System Suspend...
17.04.2025 10:04:54:603	systemd	pamac-mirrorlist.service: Deactivated successfully.
17.04.2025 10:04:54:620	systemd	Finished Generate mirrorlist.
17.04.2025 10:04:54:624	systemd	session-1.scope: Unit now frozen-by-parent.
17.04.2025 10:04:54:624	systemd	user@1000.service: Unit now frozen-by-parent.
17.04.2025 10:04:54:624	systemd	user-1000.slice: Unit now frozen-by-parent.
17.04.2025 10:04:54:624	systemd	user.slice: Unit now frozen.
17.04.2025 10:04:54:624	systemd-sleep	Successfully froze unit 'user.slice'.
17.04.2025 10:04:54:626	systemd-sleep	Performing sleep operation 'suspend'...

17.04.2025 10:04:54:710	systemd	man-db.service: Deactivated successfully.
17.04.2025 10:04:54:730	systemd	Finished Daily man-db regeneration.
17.04.2025 10:05:17:058	systemd-sleep	System returned from sleep operation 'suspend'.
17.04.2025 10:05:17:063	systemd	session-1.scope: Unit now thawed.
17.04.2025 10:05:17:063	systemd	user@1000.service: Unit now thawed.
17.04.2025 10:05:17:063	systemd	user-1000.slice: Unit now thawed.
17.04.2025 10:05:17:063	systemd	user.slice: Unit now thawed.
17.04.2025 10:05:17:064	systemd-sleep	Successfully thawed unit 'user.slice'.
17.04.2025 10:05:17:066	systemd	systemd-suspend.service: Deactivated successfully.
17.04.2025 10:05:17:098	systemd	Finished System Suspend.
17.04.2025 10:05:17:099	systemd	Stopped target Sleep.
17.04.2025 10:05:17:099	systemd	Reached target Suspend.
17.04.2025 10:05:17:099	systemd-logind	Operation 'suspend' finished.
17.04.2025 10:05:17:099	systemd	Stopped target Suspend.
17.04.2025 10:05:17:104	systemd	Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
17.04.2025 10:05:24:106	systemd	NetworkManager-dispatcher.service: Deactivated successfully.
17.04.2025 10:05:24:807	systemd	Starting Network Manager Script Dispatcher Service...
17.04.2025 10:05:24:853	systemd	Started Network Manager Script Dispatcher Service.
17.04.2025 10:05:34:863	systemd	NetworkManager-dispatcher.service: Deactivated successfully.
17.04.2025 10:05:39:197	systemd	Started ddcutil setvcp 10 65 12 60.

Of course I am happy to provide more information. I have tried to find out about timer -units as adviced by nikgnomic in another topic, but that it is above my understanding of the system.

Thanks!

and of course:

❯ inxi -zv8
System:
  Kernel: 6.6.85-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=adcda0b2-d3e3-4d08-a9bd-802191d2faf3 ro nowatchdog quiet
    apparmor=1 security=apparmor udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.12.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B360M-C v: Rev X.0x
    serial: <superuser required> part-nu: ASUS_MB_CNL uuid: <superuser required>
    UEFI: American Megatrends v: 3202 date: 07/10/2021
Battery:
  Message: No system battery data found. Is one present?
Memory:
  System RAM: total: 16 GiB available: 15.06 GiB used: 5.85 GiB (38.9%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 4 modules: 2 EC: None
    max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM1 type: no module installed
  Device-2: ChannelA-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Crucial part-no: CT8G4DFS824A.C8FDD1 serial: <filter>
  Device-3: ChannelB-DIMM1 type: no module installed
  Device-4: ChannelB-DIMM2 type: DDR4 detail: synchronous size: 8 GiB
    speed: 2400 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Micron part-no: 8ATF1G64AZ-2G3E1 serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-9500 bits: 64 type: MCP arch: Coffee Lake
    gen: core 9 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 0xA (10) microcode: 0xFA
  Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 smt: <unsupported> cache:
    L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB
    L3: 9 MiB desc: 1x9 MiB
  Speed (MHz): avg: 800 min/max: 800/4400 scaling: driver: intel_pstate
    governor: performance cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800
    bogomips: 36012
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    smap smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    disabled
  Type: mds mitigation: Clear CPU buffers; SMT disabled
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: disabled;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 00:02.0 chip-ID: 8086:3e92 class-ID: 0300
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,vesa dri: iris gpu: i915 display-ID: 0
  Monitor-1: DP-2 model: Dell P2415Q serial: <filter> built: 2015 res:
    mode: 3840x2160 hz: 60 scale: 200% (2) to: 1920x1080 dpi: 185 gamma: 1.2
    chroma: red: x: 0.659 y: 0.333 green: x: 0.302 y: 0.639 blue: x: 0.149
    y: 0.043 white: x: 0.314 y: 0.329 size: 527x296mm (20.75x11.65")
    diag: 604mm (23.8") ratio: 16:9 modes: 3840x2160, 2560x1440, 2048x1280,
    1920x1200, 1920x1080, 1920x1080i, 1600x1200, 1600x900, 1280x1024,
    1152x864, 1280x720, 1024x768, 800x600, 720x576, 720x480, 640x480, 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.3-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL
    GT2) device-ID: 8086:3e92 memory: 7.35 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: 4 device: 0 type: integrated-gpu name: Intel
    UHD Graphics 630 (CFL GT2) driver: mesa intel v: 25.0.3-arch1.1
    device-ID: 8086:3e92 surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: WinChipHead USB-MIDI driver: snd-usb-audio type: USB rev: 1.1
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-10:7 chip-ID: 4348:552d
    class-ID: 0103
  Device-2: Van Ooijen Technische Informatica Teensyduino MIDI
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-4:3 chip-ID: 16c0:0485 class-ID: 0300
  Device-3: BEHRINGER GmbH UMC202HD 192k driver: snd-usb-audio type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-7:5 chip-ID: 1397:0507
    class-ID: fe01
  API: ALSA v: k6.6.85-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.1 status: active with: 1: pipewire-pulse
    status: active 2: pipewire-media-session status: active 3: pipewire-alsa
    type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli
Network:
  Device-1: Intel Ethernet I219-V vendor: ASUSTeK driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15bc class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 2.5 TiB used: 628.2 GiB (24.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:7 vendor: Samsung model: SSD 980 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B4QFXO7 temp: 29.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Kingston model: SA2000M8250G
    size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: S5Z42109 temp: 24.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST2000DM005-2CW102
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: HDD rpm: 5425 serial: <filter> fw-rev: 0001 scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 60.95 GiB size: 59.7 GiB (97.94%) used: 28.84 GiB (48.3%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:9 label: N/A
    uuid: adcda0b2-d3e3-4d08-a9bd-802191d2faf3
  ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
    used: 27.8 MiB (5.4%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:8 label: N/A
    uuid: 7BA3-CEF8
  ID-3: /home raw-size: 57.79 GiB size: 56.71 GiB (98.13%)
    used: 16.36 GiB (28.8%) fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:10
    label: N/A uuid: ddb97e0c-1737-48cd-b6bc-2bbb94e366da
  ID-4: /mnt/VMs raw-size: 346.52 GiB size: 340.52 GiB (98.27%)
    used: 213.07 GiB (62.6%) fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:11
    label: VM uuid: 3420576a-6118-4f9d-87c7-1a54834d66a2
  ID-5: /mnt/backup raw-size: 39.06 GiB size: 38.15 GiB (97.67%)
    used: 8.2 GiB (21.5%) fs: ext4 dev: /dev/sda4 maj-min: 8:4 label: backup
    uuid: c91c82c7-4385-4984-8d0b-b457603d149d
  ID-6: /mnt/datadisk raw-size: 976.56 GiB size: 960.17 GiB (98.32%)
    used: 361.71 GiB (37.7%) fs: ext4 dev: /dev/sda2 maj-min: 8:2
    label: datadisk uuid: 73ee0977-b9bd-4123-885f-06b9f0ec03d0
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/nvme1n1p1 maj-min: 259:1 size: 198 MiB fs: vfat label: N/A
    uuid: E6D0-6FB3
  ID-2: /dev/nvme1n1p2 maj-min: 259:2 size: 51.24 GiB fs: apfs label: N/A
    uuid: 385eb76c-0634-4762-90b2-48fc0b599982
  ID-3: /dev/nvme1n1p3 maj-min: 259:3 size: 46.41 GiB fs: ext4 label: N/A
    uuid: f8a20f45-b2f8-4887-8a38-cf0442ad21ac
  ID-4: /dev/nvme1n1p4 maj-min: 259:4 size: 49.42 GiB fs: ext4 label: N/A
    uuid: 788a3f6f-f504-4f15-adb5-599fd5bedc81
  ID-5: /dev/nvme1n1p5 maj-min: 259:5 size: 40 GiB fs: ext4 label: N/A
    uuid: c22c6ba2-5463-40a1-b24f-6aab8e7ae8d7
  ID-6: /dev/nvme1n1p6 maj-min: 259:6 size: 20 GiB fs: ext4 label: homeLM20
    uuid: b389272c-7f4f-4fc8-9140-bb19f78ccec1
  ID-7: /dev/sda1 maj-min: 8:1 size: 200 MiB fs: vfat label: N/A
    uuid: A7F1-FC7C
  ID-8: /dev/sda3 maj-min: 8:3 size: 48.83 GiB fs: ext4 label: tsh_arch
    uuid: ac599558-1bdd-4e8d-ba23-f4118d013c2b
  ID-9: /dev/sda5 maj-min: 8:5 size: 439.45 GiB fs: ext4 label: 450G
    uuid: 1c54c611-0b44-498a-8e5d-d0014611ec29
  ID-10: /dev/sda6 maj-min: 8:6 size: 358.91 GiB fs: ext4 label: 367G
    uuid: 600292b8-dcfe-48ac-8d74-7735f591e86f
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 1-3:2 info: Apple Hub in Aluminum Keyboard ports: 3 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 300mA
    chip-ID: 05ac:1006 class-ID: 0900
  Device-1: 1-3.2:4 info: Apple Aluminium Keyboard (ANSI) type: keyboard,HID
    driver: apple,usbhid interfaces: 2 rev: 2.0 speed: 1.5 Mb/s (183 KiB/s)
    lanes: 1 mode: 1.0 power: 20mA chip-ID: 05ac:024f class-ID: 0300
  Device-2: 1-4:3 info: Van Ooijen Technische Informatica Teensyduino MIDI
    type: audio,HID driver: hid-generic,snd-usb-audio,usbhid interfaces: 2
    rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 16c0:0485 class-ID: 0300
  Device-3: 1-7:5 info: BEHRINGER GmbH UMC202HD 192k type: audio
    driver: snd-usb-audio interfaces: 4 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 1397:0507 class-ID: fe01
  Device-4: 1-8:6 info: Logitech Premium Optical Wheel Mouse (M-BT58)
    type: mouse driver: hid-generic,usbhid interfaces: 1 rev: 2.0
    speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 98mA
    chip-ID: 046d:c03e class-ID: 0301
  Device-5: 1-10:7 info: WinChipHead USB-MIDI type: audio
    driver: snd-usb-audio interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 78mA chip-ID: 4348:552d class-ID: 0103
  Hub-3: 2-0:1 info: super-speed hub ports: 6 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1935 libs: 495 tools: octopi,pamac,yay
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.bouwhuis.network/manjaro/testing/$repo/$arch
    2: https://manjaro.mirror.wearetriple.com/testing/$repo/$arch
    3: https://mirror.koddos.net/manjaro/testing/$repo/$arch
Processes:
  CPU top: 5 of 254
  1: cpu: 4.0% command: firefox pid: 39558 mem: 289.2 MiB (1.8%)
  2: cpu: 2.5% command: firefox pid: 41174 mem: 57.2 MiB (0.3%)
  3: cpu: 0.6% command: firefox pid: 1922 mem: 653.0 MiB (4.2%)
  4: cpu: 0.5% command: firefox pid: 40741 mem: 231.7 MiB (1.5%)
  5: cpu: 0.3% command: kwin_wayland pid: 902 mem: 336.6 MiB (2.1%)
  Memory top: 5 of 254
  1: mem: 653.0 MiB (4.2%) command: firefox pid: 1922 cpu: 0.6%
  2: mem: 495.5 MiB (3.2%) command: plasmashell pid: 1087 cpu: 0.0%
  3: mem: 397.3 MiB (2.5%) command: firefox pid: 2059 cpu: 0.0%
  4: mem: 375.4 MiB (2.4%) command: zapzap started-by: python pid: 1214
    cpu: 0.0%
  5: mem: 374.9 MiB (2.4%) command: QtWebEngineProcess pid: 1684 cpu: 0.0%
Info:
  Processes: 254 Power: uptime: 1d 19h 22m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 15 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 6.01 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.2.37 running-in: konsole inxi: 3.3.38
1 Like
2

Wow - I caught this one too… I thought it was something to do with waking up the keyboard and connecting bluetooth… but sure, if I suspend the system it needs waking up twice.

Did you test this on a clean profile? I’m going to log out and check that out right now.

4m later

  • disabled locking on the Test User, suspended and woke up… so it’s definitely something in the Home folder. Not sure how easy that is to narrow down…

  • Next step is to move the old .config folder and try again.

mv -vi .config .configOLDER && loginctl terminate-user 1000

Will that do it?

Just a little later on…

This boiled down to keyboard shortcuts. After a couple of logout/login sleep/wake, I wanted to get SLEEP back on Fn_F2…

So I moved my 18.7 kib kglobalshortcuts over, the issue instantly returned…

What’s really crazy is this:

If I suspend via krunner, or menu, this doesn’t happen.

If I suspend by binding it to a keyboard shortcut, it happens.

So, @hans - tell me how you were activating suspend.

So there is one more question:

Can anyone else confirm this?

    1. Create a new keyboard shortcut (e.g. Meta+F2) and bind it to suspend
    1. Write a bash script to suspend (for me it got the same result)
    1. Final test - dig an old wired (USB) keyboard out, bind suspend to Meta+Keypad 0… and the same result. Calling suspend from keyboard means it needs waking up twice.

Any clue? I’m curious if I can find something in BIOS for this - it’s certainly not a problem I had last month though, I’ve always suspended my system from keyboard if the sleep timer doesn’t kick in.

Ok, another test - from the sleep timer.

So finally, I tried something (with no good reasoning other than to decouple it from the keyboard) new.

I wrote another bash script ksuspend.sh

#!/bin/bash

commands() {

    systemctl suspend
}

export -f commands

konsole -e "bash -c 'commands'"
sleep 10

Obviously needed my trusty shortcut 'chmodx` due to being too lazy to type chmod +X and bound THAT to the Meta+F2 key.

Obviously binding to the correct key with the professionally applied keyboard symbol:
20250417_221129

The final result - applying suspend in this way succeeds in allowing a single wake-up event to bring it back to life…

So rather than a ‘solution’ I’ll award myself with ‘dirty workaround of the day’ award.

certificate for Manjaro dirty workaround of the day award

3 Likes
3

Wow! Thanks for looking into this!

I suspend my system in two ways:

  • automatically with Power Management Suspend Session Sleep After 20 minutes, and
  • yes, with a keyboard shortcut which I can not find with the KDE Systems Settings, Input & Output, Keyboard, Shortcuts, but in kglobalshortcutsrc it is there:
[org_kde_powerdevil]
Decrease Keyboard Brightness=Keyboard Brightness Down,Keyboard 
<removed some entries>
PowerOff=Power Off,Power Off,Power Off
Sleep=Sleep\tCtrl+Launch (6),Sleep,Suspend

I will try your prize winning script and let you know the results. And BTW wakeup sometimes succeeds in one go and sometimes not, I do not always use the keyboard shortcut, and, yes, probably BIOS / ACPI is also involved.

2 Likes
4

Hmmmm yes, I’m not sure - but I think the script mitigated the issue - but I’m also fairly sure that it did recur this morning - or maybe a symptom of my KAlarm sleep command being delayed by manually sleeping last night.

5

Not really, but how about key codes? Does that “thing” that is responsible for making computer sleep, expect a certain key code it doesn’t get? Perhaps language settings makes it “weird”, since you had the same problem regardless of the keyboard used.

6

I’m confident that I never had this problem (same install) last month when I was using a Logitech keyboard that had a ‘power’ button which I mapped to ‘sleep’… though there’s no way to test that now as it’s dead…

I just tried it again right now, and I can’t figure this out - now I see konsole window flash up and disappear. If I shorten the command to ‘sleep 5’ it still does the same thing… so maybe it is a problem with Plasma.

I can bind 'sleep to another shortcut (let’s try Shift_Alt_F2) and the machine needs waking a second time.

My language settings haven’t been touched for years, which is why I suspected an issue with my new keyboard, but just verified that it’s still present with a wired keyboard (another Logitech) which we keep in the storage room.

So now I modified my script, I see Konsole this time…

#!/bin/bash

konsole -e bash -c "
echo 'Suspending in 2 seconds...';
sleep 2;  # Show message for 2 sec
systemctl suspend &  # Run suspend in background
sleep 2; # wait for system to settle mayube...
exit  # Close Konsole immediately (suspend continues independently)
"

This works fine when I run it as ./ksuspend.sh
Also, upon resume the konsole window is gone… and I only wake up the machine one time (as you would expect).

7

Hmm, wayland vs. x11?

8

Ben, your first script runs fine on my system so far, i.e. system just wakes up after suspend with ctrl-Functionkey.
Seems your issue and mine are not the same!

1 Like
9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.