Issue with sleep behavior

Support
1

The interaction between standby and hibernate is not functioning as expected. Normally, I can close the laptop lid and it goes into standby mode. It only loses a small amount of battery power overnight. I don’t just close the lid, I actively put it into standby mode first.
I did that yesterday as well. This morning, I opened the laptop and saw that the battery was only at 2%. This leads me to two questions:

  1. Why does it wake up on its own when the lid is closed?
  2. The power settings are actually set to put it into hibernate mode when the battery is at 5%—why isn’t it doing that?
# journalctl -b | grep -i sleep

Jan 03 20:53:52 t14 NetworkManager[1007]: <info>  [1767470032.6141] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 03 20:53:52 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] system is about to suspend
Jan 03 20:53:52 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Jan 03 20:53:52 t14 kwin_wayland[1182]: Failed to delay sleep: The operation inhibition has been requested for is already running
Jan 03 20:53:52 t14 NetworkManager[1007]: <info>  [1767470032.6279] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 03 20:53:52 t14 NetworkManager[1007]: <info>  [1767470032.6286] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 03 20:53:52 t14 NetworkManager[1007]: <info>  [1767470032.8343] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 03 20:53:53 t14 systemd[1]: Reached target Sleep.
Jan 03 20:53:53 t14 systemd-sleep[2558578]: Successfully froze unit 'user.slice'.
Jan 03 20:53:53 t14 systemd-sleep[2558578]: Performing sleep operation 'suspend'...
Jan 03 23:41:21 t14 systemd-sleep[2558578]: System returned from sleep operation 'suspend'.
Jan 03 23:41:21 t14 systemd-sleep[2558578]: Successfully thawed unit 'user.slice'.
Jan 03 23:41:21 t14 systemd[1]: Stopped target Sleep.
Jan 03 23:41:21 t14 NetworkManager[1007]: <info>  [1767480081.2832] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 03 23:41:21 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] system is resuming
Jan 03 23:41:31 t14 NetworkManager[1007]: <info>  [1767480091.5133] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 03 23:41:31 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] system is about to suspend
Jan 03 23:41:31 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Jan 03 23:41:31 t14 kwin_wayland[1182]: Failed to delay sleep: The operation inhibition has been requested for is already running
Jan 03 23:41:31 t14 NetworkManager[1007]: <info>  [1767480091.5227] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 03 23:41:31 t14 NetworkManager[1007]: <info>  [1767480091.5235] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 03 23:41:31 t14 NetworkManager[1007]: <info>  [1767480091.6280] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 03 23:41:32 t14 systemd[1]: Reached target Sleep.
Jan 03 23:41:32 t14 systemd-sleep[2558836]: Successfully froze unit 'user.slice'.
Jan 03 23:41:32 t14 systemd-sleep[2558836]: Performing sleep operation 'suspend'...
Jan 04 02:33:56 t14 systemd-sleep[2558836]: System returned from sleep operation 'suspend'.
Jan 04 02:33:56 t14 systemd-sleep[2558836]: Successfully thawed unit 'user.slice'.
Jan 04 02:33:56 t14 systemd[1]: Stopped target Sleep.
Jan 04 02:33:56 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] system is resuming
Jan 04 02:33:56 t14 NetworkManager[1007]: <info>  [1767490436.7191] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 04 02:34:07 t14 NetworkManager[1007]: <info>  [1767490447.0322] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 04 02:34:07 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] system is about to suspend
Jan 04 02:34:07 t14 ModemManager[1059]: <msg> [sleep-monitor-systemd] ready to sleep; dropping inhibitor
Jan 04 02:34:07 t14 kwin_wayland[1182]: Failed to delay sleep: The operation inhibition has been requested for is already running
Jan 04 02:34:07 t14 NetworkManager[1007]: <info>  [1767490447.0430] manager: NetworkManager state is now DISABLED (ASLEEP)
Jan 04 02:34:07 t14 NetworkManager[1007]: <info>  [1767490447.0437] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 04 02:34:07 t14 NetworkManager[1007]: <info>  [1767490447.1772] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 04 02:34:07 t14 systemd[1]: Reached target Sleep.
Jan 04 02:34:07 t14 systemd-sleep[2559021]: Successfully froze unit 'user.slice'.
Jan 04 02:34:07 t14 systemd-sleep[2559021]: Performing sleep operation 'suspend'...

As you can see, I actively selected standby mode at 8:53 p.m. The laptop performed all activities after this time independently with the lid closed. Do you require any further information?

EDIT: Link to current system information.

System:
  Kernel: 6.18.2-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: hpet avail: acpi_pm parameters: quiet splash
    rd.luks.uuid=4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495
    rd.luks.uuid=6a3c9f2b-3620-43f9-a499-6e333ad9a5da
    root=/dev/mapper/luks-4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495
    resume=/dev/mapper/luks-6a3c9f2b-3620-43f9-a499-6e333ad9a5da rw
    rootflags=subvol=@,rw modprobe.blacklist=pcspkr hibernate.compressor=lz4
  Desktop: KDE Plasma v: 6.5.4 tk: Qt v: N/A wm: kwin_wayland with: docker
    dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 21KJ v: ThinkBook 14 G6 ABP
    serial: <filter> Chassis: type: 10 v: ThinkBook 14 G6 ABP serial: <filter>
  Mobo: LENOVO model: LNVNB161216 v: SDK0K17763 WIN serial: <filter>
    part-nu: LENOVO_MT_21KJ_BU_idea_FM_IDEAPAD
    uuid: dc2ca586-094d-5daf-afee-e578e2f0ca54 Firmware: UEFI vendor: LENOVO
    v: MNCN35WW date: 03/19/2025
Battery:
  ID-1: BAT0 charge: 26.4 Wh (61.8%) condition: 42.7/45 Wh (94.8%)
    power: 26.6 W volts: 12.36 min: 11.58 model: SMP L22M3PE0 type: Li-poly
    serial: <filter> charging: status: charging type: long_life
    avail: long_life,standard cycles: 71
Memory:
  System RAM: total: 32 GiB available: 29.21 GiB used: 15.41 GiB (52.8%)
  Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Channel-A DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: CT16G4SFRA32A.M16FR serial: <filter>
  Device-2: Channel-B DIMM 0 type: DDR4 detail: synchronous unbuffered
    (unregistered) size: 16 GiB speed: 3200 MT/s volts: curr: 1.2 min: 1.2
    max: 1.2 width (bits): data: 64 total: 64 manufacturer: Crucial
    part-no: CT16G4SFRA32A.M16FR serial: <filter>
PCI Slots:
  Slot: 1 type: PCIe status: available info: J10 length: short volts: 3.3
    bus-ID: 0200:00:01.1
  Slot: 2 type: PCIe status: available info: J79 length: short volts: 3.3
    bus-ID: 0200:00:01.6
  Slot: N/A type: N/A status: available info: M.2, J92 length: short
    volts: 3.3 bus-ID: 0200:00:01.2
  Slot: N/A type: N/A status: available info: M.2, J90 length: short
    volts: 3.3 bus-ID: 0200:00:01.4
  Slot: N/A type: N/A status: available info: M.2, J19 length: short
    volts: 3.3 bus-ID: 0200:00:01.7
  Slot: N/A type: N/A status: available info: M.2 length: short volts: 3.3
    bus-ID: 0200:00:01.5
CPU:
  Info: model: AMD Ryzen 5 7530U with Radeon Graphics socket: FP6 bits: 64
    type: MT MCP arch: Zen 3 gen: 3 level: v3 note: check built: 2021-22
    process: TSMC n7 (7nm) family: 0x19 (25) model-id: 0x50 (80) stepping: 0
    microcode: 0xA500014
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 6 threads: 12 tpc: 2
    smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB
    desc: 6x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 2945 min/max: 411/4548 boost: enabled
    base/boost: 2000/4550 scaling: driver: amd-pstate-epp governor: powersave
    volts: 1.2 V ext-clock: 100 MHz cores: 1: 2945 2: 2945 3: 2945 4: 2945
    5: 2945 6: 2945 7: 2945 8: 2945 9: 2945 10: 2945 11: 2945 12: 2945
    bogomips: 47911
  Flags: 3dnowprefetch abm adx aes aperfmperf apic arat avic avx avx2 bmi1
    bmi2 bpext cat_l3 cdp_l3 clflush clflushopt clwb clzero cmov cmp_legacy
    constant_tsc cpb cppc cpuid cqm cqm_llc cqm_mbm_local cqm_mbm_total
    cqm_occup_llc cr8_legacy cx16 cx8 de debug_swap decodeassists erms
    extapic extd_apicid f16c flushbyasid fma fpu fsgsbase fsrm fxsr fxsr_opt
    ht hw_pstate ibpb ibrs ibs invpcid irperf lahf_lm lbrv lm mba mca mce
    misalignsse mmx mmxext monitor movbe msr mtrr mwaitx nonstop_tsc nopl npt
    nrip_save nx ospke osvw overflow_recov pae pat pausefilter pclmulqdq
    pdpe1gb perfctr_core perfctr_llc perfctr_nb pfthreshold pge pku pni
    popcnt pse pse36 rapl rdpid rdpru rdrand rdseed rdt_a rdtscp rep_good sep
    sha_ni skinit smap smca smep ssbd sse sse2 sse4_1 sse4_2 sse4a ssse3
    stibp succor svm svm_lock syscall tce topoext tsc tsc_scale umip
    user_shstk v_spec_ctrl v_vmsave_vmload vaes vgif vmcb_clean vme vmmcall
    vpclmulqdq wbnoinvd wdt xgetbv1 xsave xsavec xsaveerptr xsaveopt xsaves
    xtopology
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Barcelo vendor: Lenovo
    driver: amdgpu v: kernel arch: GCN-5 code: Vega process: GF 14nm
    built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: eDP-1
    empty: DP-1,DP-2,HDMI-A-1 bus-ID: 05:00.0 chip-ID: 1002:15e7
    class-ID: 0300 temp: 57.0 C
  Device-2: Chicony Integrated Camera (1920x1080) driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:2 chip-ID: 04f2:b7b4
    class-ID: fe01 serial: <filter>
  Display: unspecified server: X.Org v: 24.1.9 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    alternate: fbdev,vesa dri: radeonsi gpu: amdgpu display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 508x317mm (20.00x12.48")
    s-diag: 599mm (23.57") monitors: <missing: xrandr>
  Monitor-1: eDP-1 model: Lenovo 0x9125 built: 2022 res: 1920x1200 dpi: 162
    gamma: 1.2 chroma: red: x: 0.592 y: 0.349 green: x: 0.329 y: 0.557 blue:
    x: 0.153 y: 0.118 white: x: 0.314 y: 0.329 size: 301x188mm (11.85x7.4")
    diag: 355mm (14") ratio: 16:10 modes: 1920x1200, 1920x1080, 1600x1200,
    1680x1050, 1280x1024, 1440x900, 1280x800, 1280x720, 1024x768, 800x600,
    640x480
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 25.3.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon Graphics (radeonsi
    renoir ACO DRM 3.64 6.18.2-1-MANJARO) device-ID: 1002:15e7
    memory: 1.95 GiB unified: no
  API: Vulkan v: 1.4.335 layers: 2 device: 0 type: integrated-gpu name: AMD
    Radeon Graphics (RADV RENOIR) driver: mesa radv v: 25.3.1-arch1.2
    device-ID: 1002:15e7 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Advanced Micro Devices [AMD/ATI] Renoir/Cezanne HDMI/DP Audio
    vendor: Lenovo driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
    lanes: 16 bus-ID: 05:00.1 chip-ID: 1002:1637 class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Audio Coprocessor vendor: Lenovo
    driver: N/A alternate: snd_pci_acp3x, snd_rn_pci_acp3x, snd_pci_acp5x,
    snd_pci_acp6x, snd_acp_pci, snd_rpl_pci_acp6x, snd_pci_ps,
    snd_sof_amd_renoir, snd_sof_amd_rembrandt, snd_sof_amd_vangogh,
    snd_sof_amd_acp63, snd_sof_amd_acp70 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 05:00.5 chip-ID: 1022:15e2 class-ID: 0480
  Device-3: Advanced Micro Devices [AMD] Ryzen HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 05:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.18.2-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.9 status: n/a (root, process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp2s0 state: down mac: <filter>
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network vendor: Lenovo
    driver: rtw89_8852be v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 03:00.0 chip-ID: 10ec:b852 class-ID: 0280
  IF: wlp3s0 state: up 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
  IF-ID-1: br-0721f811e847 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IP v6: <filter> virtual: proto kernel_ll scope: link
  IF-ID-2: docker0 state: down mac: <filter>
  IP v4: <filter> scope: global broadcast: <filter>
  IF-ID-3: veth439b13b state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-4: veth578f52b state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-5: veth69a5955 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-6: veth7f79111 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-7: vetha206c79 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-8: vethb9fb928 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  IF-ID-9: vethd9ac777 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  Info: services: NetworkManager, nginx, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 0bda:4853
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci1 rfk-id: 18 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: luks-4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495 maj-min: 253:0
    type: LUKS dm: dm-0 size: 897.5 GiB
  Components:
  p-1: nvme0n1p2 maj-min: 259:2 size: 897.51 GiB
  Device-2: luks-6a3c9f2b-3620-43f9-a499-6e333ad9a5da maj-min: 253:1
    type: LUKS dm: dm-1 size: 31.98 GiB
  Components:
  p-1: nvme0n1p3 maj-min: 259:3 size: 32 GiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 931.51 GiB used: 797.74 GiB (85.6%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B4QFXO7 temp: 49.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 6d 1h cycles: 569
    read-units: 5,098,394 [2.61 TB] written-units: 11,432,234 [5.85 TB]
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 897.5 GiB size: 897.5 GiB (100.00%)
    used: 398.72 GiB (44.4%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
    maj-min: 253:0 mapped: luks-4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495
    label: N/A uuid: 037a9e11-cb1b-48ea-84c6-8e9a343add20
  ID-2: /efi raw-size: 2 GiB size: 2 GiB (99.80%) used: 293.1 MiB (14.3%)
    fs: vfat block-size: 512 B dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 3455-2BAE
  ID-3: /home raw-size: 897.5 GiB size: 897.5 GiB (100.00%)
    used: 398.72 GiB (44.4%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
    maj-min: 253:0 mapped: luks-4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495
    label: N/A uuid: 037a9e11-cb1b-48ea-84c6-8e9a343add20
  ID-4: /home/<filter>/Development/storage raw-size: N/A size: 897.5 GiB
    used: 398.72 GiB (44.4%) fs: fuse source: ERR-102
  ID-5: /var/cache raw-size: 897.5 GiB size: 897.5 GiB (100.00%)
    used: 398.72 GiB (44.4%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
    maj-min: 253:0 mapped: luks-4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495
    label: N/A uuid: 037a9e11-cb1b-48ea-84c6-8e9a343add20
  ID-6: /var/dev/code raw-size: N/A size: 897.5 GiB used: 398.72 GiB (44.4%)
    fs: fuse source: ERR-102
  ID-7: /var/dev/share raw-size: N/A size: 897.5 GiB
    used: 398.72 GiB (44.4%) fs: fuse source: ERR-102
  ID-8: /var/log raw-size: 897.5 GiB size: 897.5 GiB (100.00%)
    used: 398.72 GiB (44.4%) fs: btrfs block-size: 4096 B dev: /dev/dm-0
    maj-min: 253:0 mapped: luks-4bd4a6cf-50a3-4dc4-8855-3f3d4f3f6495
    label: N/A uuid: 037a9e11-cb1b-48ea-84c6-8e9a343add20
Swap:
  Kernel: swappiness: 0 (default 60) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 31.98 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/dm-1 maj-min: 253:1
    mapped: luks-6a3c9f2b-3620-43f9-a499-6e333ad9a5da label: swap
    uuid: aa787332-d764-4142-b2af-179e75107bce
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-4:2 info: Chicony Integrated Camera (1920x1080) type: video
    driver: uvcvideo interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 04f2:b7b4 class-ID: fe01
    serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 2 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
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-3:2 info: Shenzhen Goodix FingerPrint type: <vendor specific>
    driver: N/A interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 27c6:550a class-ID: ff00
  Device-2: 3-4:3 info: Realtek Bluetooth Radio type: bluetooth
    driver: btusb interfaces: 2 rev: 1.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 500mA chip-ID: 0bda:4853 class-ID: e001 serial: <filter>
  Hub-4: 4-0:1 info: super-speed hub ports: 2 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: 74.2 C mobo: N/A gpu: amdgpu temp: 59.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1403 libs: 371 tools: pamac
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirror.23m.com/manjaro/stable/$repo/$arch
    2: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    3: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    4: https://manjaro.kurdy.org/stable/$repo/$arch
Processes:
  CPU top: 5 of 494
  1: cpu: 8.7% command: firefox pid: 2569557 mem: 288.3 MiB (0.9%)
  2: cpu: 6.1% command: firefox pid: 2656971 mem: 306.3 MiB (1.0%)
  3: cpu: 2.0% command: electron pid: 1866428 mem: 526.8 MiB (1.7%)
  4: cpu: 1.9% command: zsh pid: 2660820 mem: 8.86 MiB (0.0%)
  5: cpu: 1.7% command: firefox pid: 3291 mem: 980.4 MiB (3.2%)
  Memory top: 5 of 494
  1: mem: 3073.8 MiB (10.2%) command: java pid: 1541542 cpu: 0.1%
  2: mem: 1192.1 MiB (3.9%) command: EN started-by: okular pid: 1635469
    cpu: 0.0%
  3: mem: 980.4 MiB (3.2%) command: firefox pid: 3291 cpu: 1.7%
  4: mem: 715.4 MiB (2.3%) command: java pid: 1114369 cpu: 0.3%
  5: mem: 657.6 MiB (2.1%) command: EN started-by: okular pid: 1660334
    cpu: 0.0%
Info:
  Processes: 494 Power: uptime: 6d 7h 30m states: freeze,mem,disk
    suspend: s2idle wakeups: 14 hibernate: suspend avail: platform, shutdown,
    reboot, test_resume image: 0 KiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 258 default: graphical
    tool: systemctl
  Compilers: gcc: 15.2.1 Shell: Zsh (sudo) v: 5.9 running-in: konsole
    inxi: 3.3.40

Mod edit:- inxi output copied from pastebin for the benefit of those wishing to help. No charge.

2

@kullermann

As always, system information might prove useful:

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, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):
inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)
inxi man pages (manual)
Running `inxi` within a `chroot` environment
  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0
Your privacy is respected
3

For sure. My fault. Added to the original post.

5

You seem to be using suspend-then-hibernate - so it wakes up every few hours to check the battery level.

systemctl suspend-then-hibernate initially suspends the system to RAM as long as possible, then wakes it with an RTC alarm and hibernates. The RTC alarm is set with HibernateDelaySec in systemd-sleep.conf(5). The default value is set by estimating the battery discharge rate to keep the system with 5% of battery, or two hours without one. Said estimation is obtained from the change in battery level after the time specified by SuspendEstimationSec in systemd-sleep.conf(5), at which the system will briefly wake up to do the measurement (a measure is also made if the system is manually woken up from suspension).

Do you usually find it hibernating in the morning?

Based on the behaviour described in the Arch wiki, and assuming it was asleep, the most obvious explanation is a poor estimate and/or bad timing. If so, the next wake-up would’ve put it into hibernation, unless the battery died first. :man_shrugging:

Let’s see if it keeps happening. Take a note of your battery level before you suspend, just in case it proves useful.

1 Like
6

I’d suggest increasing the Hibernation threshold to something like 10%. Sometimes the hibernation process itself can take a bit of power (and time) and it’s never a good idea to run a Li-Ion battery pack completely flat as that is known to destroy the electrodes and/or blow an internal “fuse” rendering the thing useless.

2 Likes
7

You seem to be using suspend-then-hibernate - so it wakes up every few hours to check the battery level.

That makes sense, thank you for the explanation. As far as I understand, a “real” suspend-to-RAM would be the S3 state, right? However, my ThinkBook “only” supports S2idle, even though I would actually prefer the old S3.

Do you usually find it hibernating in the morning?

I rarely disconnect the laptop from the power supply; it is connected to the docking station most of the time, so it is difficult for me to assess its behavior. However, the last few times it was in standby mode overnight, it usually consumed about 20% of the battery during that time.

I understand that battery power can also be consumed between the times when it is woken up for testing. But if it otherwise only consumes 20% battery power over several hours in standby mode, I am surprised that it consumed almost 60% within 6 hours (between 9 p.m. and 3 a.m.) this time.

I’d suggest increasing the Hibernation threshold to something like 10%.

That makes sense too. I’ll keep an eye on it and see if I can reactivate S3 mode indirectly. Lenovo no longer offers it officially, but Enabling the S3 sleep state (suspend-to-RAM) on the Lenovo Yoga 7 AMD Gen 7 (and possibly, others) – Saverio Miroddi – 64K RAM SYSTEM  38911 BASIC BYTES FREE seems worth a try to me.

1 Like
8

I think I’ve found something. Sorry, the screenshot is only in German, but for the power settings when running on battery and with a low charge, the power saving mode is set to “Standby.” Should I perhaps change that to “Standby and then Hibernate”?

Bildschirmfoto_20260105_171819
Bildschirmfoto_20260105_171819770×627 46.9 KB

9

It happened again. Yesterday at 9 p.m., I manually activated standby mode and closed the laptop. I can see in the log that it woke up at 1 a.m., 2 a.m., and 5 a.m. (presumably for the check). When I opened it again at 8 a.m. this morning, the battery was at 2%. This is doubly annoying.
Firstly, that it doesn’t at least go into hibernation mode. I increased the critical battery level limit to 10% and the standby mode is now set to “Standby and then hibernation.”
Secondly, why is the battery consumption so high in the first place? I turned it off yesterday with about 60% battery life, and after 11 hours of standby, it’s almost completely empty!
But something just occurred to me. I updated to Manjaro 26.0 a few days ago, and since then, there’s only Wayland. Before that, I had only used X11. Could that have something to do with it? How can I further debug both problems?

10

I’m not getting any notifications, and it doesn’t look like anyone else is either.

Please click the Reply button below the post that you want to reply to, then that person will be notified. You can also mention people like this: @kullermann :smiley:

So it’s intermittent?
Or was last night the first time you left it unplugged since your last post?

~4hr, ~1hr, ~3hr intervals, and ~3hrs between the last wake and you opening it. Last time it was ~3hrs each time.

You could try a smaller delay. I’d try 7200 (2hrs), and/or 3600 (1hr)

SuspendEstimationSec=

The RTC alarm will wake the system after the specified timespan to measure the system battery capacity level and estimate battery discharging rate. Only used by systemd-suspend-then-hibernate.service(8). Refer to suspend-then-hibernate for details on how this option interacts with other options/system battery state.

Added in version 253.

Unfortunately our :crystal_ball: is broken - we’re saving up to buy a new one. :grin:

Might be possible :man_shrugging:

You could install X11 and test to see if there’s a difference, but KDE will be removing it completely in the near future.

Your profile says you use XFCE, but you seem to be using KDE so please update your profile. :smiley:

Well, we need to know what’s happening - so I’d start with looking for clues in the logs, what actually happens vs a successful suspend-then-hibernate.

We can’t tell if the logs we’ve seen so far are complete, as they just stop around 2am after entering sleep (only you know what happened afterwards). Ideally we’d see from you putting it to sleep all the way up to you opening the laptop (unfiltered of course), that way we know we’re not missing anything.

Can I assume you’re suspending properly?

Note that systemd-suspend.service, systemd-hibernate.service, systemd-hybrid-sleep.service, and systemd-suspend-then-hibernate.service should never be executed directly. Instead, trigger system sleep with a command such as systemctl suspend or systemctl hibernate.

Is there any evidence of a failed hibernation?

Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units, respectively) will run all executables in /usr/lib/systemd/system-sleep/ and pass two arguments to them. The first argument will be “pre”, the second either “suspend”, “hibernate”, “hybrid-sleep”, or “suspend-then-hibernate” depending on the chosen action. An environment variable called “SYSTEMD_SLEEP_ACTION” will be set and contain the sleep action that is processing. This is primarily helpful for “suspend-then-hibernate” where the value of the variable will be “suspend”, “hibernate”, or “suspend-after-failed-hibernate” in cases where hibernation has failed

2 Likes