Suspend or Sleep after closing notebook lid not working with kernel 7.x

Support System Updates
1

Hello!

Not sure if that category is correct.

I use manjaro testing on my aged notebook Fujitsu U727 (works in general very good)

A suspend from plasma menu oder via systemctl hibernate or systemct sleeps works perfectly

The settings in plasma powermanagement were inspected many times

I recovered some earlier timeshift “snapshots” and lid closing always does suspend/sleep. So I assume no plasma update was causing this.

Then I played with other kernels

  • with manjaro latest 6.12.87 its working,
  • with older 6.19-lqx kernels also working,
  • with manjaro 7.1.0-rc3-1 its not working
  • with liquorix 7.0.7-lqx its not working

I dont see any error messages in journal (var/log/syslog)

What system information can I provide and share with you?
Has anyone other such a problem?

2

I can confirm, neither suspend nor sleep are triggered when I close my laptop lid with 7.x kernels. They work fine if I trigger them manually. And both work on 6.18 normally. Can’t test 6.19.

3

On my xfce with 7.1 (intel laptop) it works. Maybe something plasma or video related?

1 Like
4

It certainly wouldn’t hurt to provide some system info:

inxi -zv8

Note that the output produced by this command is privacy-filtered.

Please also remember to use proper code formatting as this makes it much easier to read on the Forum:

[Mini How-To] format code or command output

Select and copy all the text in the Terminal window (minus the prompt, if you are using zsh).
Then paste the output in between two lines containing three backticks
```
or three tildes
~~~

Or:
Copy & paste, then highlight the pasted text and click the </> button at the top of the reply window (easier for smaller outputs).

Cheers! :wink:

Just a thought … have you tried toggling the settings in the plasma power management? This sometimes fixes things.

7

Here it is the inxi -zv8 output:

System:
  Kernel: 6.12.87-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 16.1.1 clocksource: tsc
    avail: acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=2a6ea263-311d-4e93-be20-63a9d4e0f143 rw
    resume=UUID=950af021-7f7d-4287-9d86-a66dd5b6a0a1 quiet splash udev.log_priority=3
    resume=UUID=950af021-7f7d-4287-9d86-a66dd5b6a0a1
  Console: pty pts/1 DM: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: FUJITSU product: LIFEBOOK U727 v: 10601736746 serial: <superuser required>
    Chassis: type: 10 v: LIFEBOOK U727 serial: <superuser required>
  Mobo: FUJITSU model: FJNB2B1 v: B4 serial: <superuser required> part-nu: SK01
    uuid: <superuser required> Firmware: UEFI vendor: FUJITSU // Insyde v: Version 1.22
    date: 06/26/2023
Battery:
  ID-1: CMB1 charge: 18.9 Wh (100%) condition: 18.9/45 Wh (42%) volts: 11.2 min: 10.8
    model: Fujitsu CP753143-01 type: Li-ion serial: <filter> charging: status: full control:
    start: N/A end: 100% cycles: N/A
Memory:
  System RAM: total: 16 GiB available: 15.45 GiB used: 3.72 GiB (24.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 32 GiB slots: 2 modules: 2 EC: None max-module-size: 16 GiB note: est.
  Device-1: ChannelA-DIMM0 type: DDR4 detail: synchronous unbuffered (unregistered) size: 8 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M471A1K43CB1-CRC serial: <filter>
  Device-2: ChannelB-DIMM0 type: DDR4 detail: synchronous unbuffered (unregistered) size: 8 GiB
    speed: 2133 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M471A1K43CB1-CRC serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i5-6200U bits: 64 type: MT MCP arch: Skylake gen: core 6 level: v3
    note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x4E (78) stepping: 3
    microcode: 0xF0
  Topology: cpus: 1x dies: 1 clusters: 2 cores: 2 threads: 4 tpc: 2 smt: enabled cache:
    L1: 128 KiB desc: d-2x32 KiB; i-2x32 KiB L2: 512 KiB desc: 2x256 KiB L3: 3 MiB desc: 1x3 MiB
  Speed (MHz): avg: 400 min/max: 400/2800 scaling: driver: intel_pstate governor: powersave
    cores: 1: 400 2: 400 3: 400 4: 400 bogomips: 19204
  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 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 status: Vulnerable: No microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  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: conditional; RSB filling;
    PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Skylake-U GT2 [HD Graphics 520] vendor: Fujitsu driver: i915 v: kernel
    arch: Gen-9 process: Intel 14n built: 2015-16 ports: active: none off: eDP-1 empty: DP-1, DP-2,
    HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:1916 class-ID: 0300
  Device-2: Chicony FJ Camera driver: uvcvideo type: USB rev: 2.0 speed: 480 Mb/s lanes: 1
    mode: 2.0 bus-ID: 1-8:6 chip-ID: 04f2:b5b9 class-ID: 0e02
  Display: unspecified server: X.org v: 1.21.1.22 with: Xwayland v: 24.1.11
    compositor: kwin_wayland driver: X: loaded: modesetting alternate: fbdev,vesa dri: iris
    gpu: i915 tty: 163x41
  Monitor-1: eDP-1 model: LG Display 0x054c built: 2016 res: 1920x1080 dpi: 177 gamma: 1.2
    chroma: red: x: 0.592 y: 0.357 green: x: 0.333 y: 0.561 blue: x: 0.153 y: 0.110 white: x: 0.314
    y: 0.329 size: 276x156mm (10.87x6.14") diag: 317mm (12.5") ratio: 16:9 modes: 1920x1080
  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 inactive: x11
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 26.0.6-arch1.1 note: console (EGL sourced)
    renderer: Mesa Intel HD Graphics 520 (SKL GT2), llvmpipe (LLVM 22.1.3 256 bits)
  API: Vulkan v: 1.4.341 layers: 2 device: 0 type: integrated-gpu name: Intel HD Graphics 520
    (SKL GT2) driver: mesa intel v: 26.0.6-arch1.1 device-ID: 8086:1916 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
    wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Fujitsu driver: snd_hda_intel v: kernel
    alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:9d70 class-ID: 0403
  API: ALSA v: k6.12.87-1-MANJARO status: kernel-api with: aoss type: oss-emulator
    tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.6.4 status: active 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: Intel Ethernet I219-LM vendor: Fujitsu driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:156f class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 8086:24f3 class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IP v4: <filter> type: noprefixroute scope: global broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  IF-ID-1: wwan0 state: down mac: <filter>
  Info: services: NetworkManager, smbd, sshd, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:5 chip-ID: 8087:0a2b class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
  Device-1: sec.crypt maj-min: 254:0 type: LUKS dm: dm-0 size: 184 MiB
  Components:
  p-1: loop0 maj-min: 7:0 size: 200 MiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 931.51 GiB used: 105.92 GiB (11.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO Plus 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: 4B2QEXM7 temp: 24.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 24.06 GiB (24.6%) fs: ext4
    dev: /dev/nvme0n1p10 maj-min: 259:10 label: mj_root uuid: 2a6ea263-311d-4e93-be20-63a9d4e0f143
  ID-2: /boot/efi raw-size: 2 GiB size: 1.98 GiB (99.22%) used: 55.2 MiB (2.7%) fs: vfat
    dev: /dev/nvme0n1p2 maj-min: 259:2 label: SYSTEM uuid: 7CCE-BC41
  ID-3: /home raw-size: 100 GiB size: 97.87 GiB (97.87%) used: 81.81 GiB (83.6%) fs: ext4
    dev: /dev/nvme0n1p11 maj-min: 259:11 label: mj_home uuid: f2c11f82-c30a-49d2-8943-f2b1c712030d
  ID-4: /home/<filter>/.sec raw-size: 184 MiB size: 166.9 MiB (90.73%) used: 421 KiB (0.2%)
    fs: ext4 dev: /dev/dm-0 maj-min: 254:0 mapped: sec.crypt label: N/A uuid: N/A
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 16 GiB used: 256 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p6 maj-min: 259:6 label: N/A uuid: 950af021-7f7d-4287-9d86-a66dd5b6a0a1
Unmounted:
  ID-1: /dev/nvme0n1p1 maj-min: 259:1 size: 1 GiB fs: ntfs label: Recovery uuid: 02C4CE1FC4CE1537
  ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 128 MiB fs: <superuser required> label: N/A
    uuid: N/A
  ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 245 GiB fs: ntfs label: Windows
    uuid: FA7ECFCC7ECF7FBD
  ID-4: /dev/nvme0n1p5 maj-min: 259:5 size: 100 GiB fs: ext4 label: deb13_root
    uuid: 237a33a7-83d1-41d4-bdf8-093e32c98bb4
  ID-5: /dev/nvme0n1p7 maj-min: 259:7 size: 100 GiB fs: ext4 label: deb13_home
    uuid: c135211c-5fe4-4d81-a5c7-5574874d510e
  ID-6: /dev/nvme0n1p8 maj-min: 259:8 size: 100 GiB fs: ext4 label: N/A
    uuid: a2779175-051f-41dd-a9dd-599fa68f85ea
  ID-7: /dev/nvme0n1p9 maj-min: 259:9 size: 100 GiB fs: ext4 label: N/A
    uuid: d890ba01-f2fd-48fb-a71f-1ef0d49a85b6
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 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-1:2 info: Google Nexus/Pixel Device (MTP) type: still imaging driver: N/A
    interfaces: 1 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 18d1:4ee1 class-ID: 0601 serial: <filter>
  Device-2: 1-2:8 info: SiGma Micro XM102K Optical Wheel Mouse type: mouse
    driver: hid-generic,usbhid interfaces: 1 rev: 1.1 speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0
    power: 100mA chip-ID: 1c4f:0034 class-ID: 0301
  Hub-2: 1-6:4 info: Cypress Unprogrammed CY7C65632/34 hub HX2VL ports: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA chip-ID: 04b4:6570 class-ID: 0900
  Device-1: 1-7:5 info: Intel Bluetooth wireless interface type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 8087:0a2b class-ID: e001
  Device-2: 1-8:6 info: Chicony FJ Camera type: video driver: uvcvideo interfaces: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA chip-ID: 04f2:b5b9 class-ID: 0e02
  Device-3: 1-9:7 info: Sierra Wireless EM7305 Modem type: communication,CDC-data
    driver: cdc_mbim interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 1199:9041 class-ID: 0a00
  Hub-3: 2-0:1 info: super-speed hub ports: 6 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s) lanes: 1
    mode: 3.2 gen-1x1 chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1531 libs: 412 tools: pamac,yay pm: flatpak pkgs: 0
  Active pacman repo servers in: /etc/pacman.conf
    1: https://liquorix.net/archlinux/$repo/$arch
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://ask4.mm.fcix.net/manjaro/testing/$repo/$arch
    2: https://mirror.xenyth.net/manjaro/testing/$repo/$arch
    3: https://mirror.dc.uz/manjaro/testing/$repo/$arch
    4: https://ftp.cc.uoc.gr/mirrors/linux/manjaro/testing/$repo/$arch
    5: https://ftp.linux.org.tr/manjaro/testing/$repo/$arch
    6: https://irltoolkit.mm.fcix.net/manjaro/testing/$repo/$arch
    7: https://forksystems.mm.fcix.net/manjaro/testing/$repo/$arch
    8: https://manjaro.mirrors.lavatech.top/testing/$repo/$arch
    9: https://mirrors.ocf.berkeley.edu/manjaro/testing/$repo/$arch
    10: https://mirror.fcix.net/manjaro/testing/$repo/$arch
    11: https://mirrors.ustc.edu.cn/manjaro/testing/$repo/$arch
    12: https://mirrors.ft.uam.es/manjaro/testing/$repo/$arch
    13: https://ftp.halifax.rwth-aachen.de/manjaro/testing/$repo/$arch
    14: https://mirror.alpix.eu/manjaro/testing/$repo/$arch
    15: https://mirrors.gigenet.com/manjaro/testing/$repo/$arch
    16: http://ftp.uni-kl.de/pub/linux/manjaro/testing/$repo/$arch
    17: https://mirror.aarnet.edu.au/pub/manjaro/testing/$repo/$arch
    18: https://mirror.alwyzon.net/manjaro/testing/$repo/$arch
    19: https://mirror.bakertelekom.fr/manjaro/testing/$repo/$arch
    20: https://manjaro.ynh.ovh/testing/$repo/$arch
    21: https://mirrors.manjaro.org/repo/testing/$repo/$arch
    22: https://mirror.23m.com/manjaro/testing/$repo/$arch
    23: https://opencolo.mm.fcix.net/manjaro/testing/$repo/$arch
    24: https://cofractal-ewr.mm.fcix.net/manjaro/testing/$repo/$arch
    25: https://mirrors.eric.ovh/manjaro/testing/$repo/$arch
    26: https://mirror.archlinux.tw/Manjaro/testing/$repo/$arch
    27: https://distrohub.kyiv.ua/manjaro/testing/$repo/$arch
    28: https://ftp.tsukuba.wide.ad.jp/Linux/manjaro/testing/$repo/$arch
    29: https://manjaro.repo.cure.edu.uy/testing/$repo/$arch
    30: https://ftp.belnet.be/mirrors/manjaro/repos/testing/$repo/$arch
    31: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/testing/$repo/$arch
    32: https://mirror.freedif.org/Manjaro/testing/$repo/$arch
    33: https://ba.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
    34: https://manjaro.mirror.wearetriple.com/testing/$repo/$arch
    35: https://ct.mirror.garr.it/mirrors/manjaro/testing/$repo/$arch
    36: https://mirror.2degrees.nz/manjaro/testing/$repo/$arch
    37: https://mirror.math.princeton.edu/pub/manjaro/testing/$repo/$arch
    38: https://ftp.gwdg.de/pub/linux/manjaro/testing/$repo/$arch
    39: https://kartolo.sby.datautama.net.id/manjaro/testing/$repo/$arch
    40: https://muug.ca/mirror/manjaro/testing/$repo/$arch
    41: https://ftp.tu-chemnitz.de/pub/linux/manjaro/testing/$repo/$arch
    42: https://mirrors.cicku.me/manjaro/testing/$repo/$arch
    43: https://ftp.lysator.liu.se/pub/manjaro/testing/$repo/$arch
    44: https://mirror.xeonbd.com/manjaro/testing/$repo/$arch
    45: https://mirror.kamtv.ru/manjaro/testing/$repo/$arch
    46: https://mirror.dkm.cz/manjaro/testing/$repo/$arch
    47: https://linorg.usp.br/manjaro/testing/$repo/$arch
    48: https://manjaro.grena.ge/testing/$repo/$arch
    49: https://mirror.bouwhuis.network/manjaro/testing/$repo/$arch
    50: https://mirror.futureweb.be/manjaro/testing/$repo/$arch
    51: https://mirror.rabisu.com/mirrors/manjaro/testing/$repo/$arch
    52: https://mirror.vinehost.net/manjaro/testing/$repo/$arch
    53: https://ftp.free.org/mirrors/repo.manjaro.org/repos/testing/$repo/$arch
    54: https://gsl-syd.mm.fcix.net/manjaro/testing/$repo/$arch
    55: https://codingflyboy.mm.fcix.net/manjaro/testing/$repo/$arch
    56: https://mirrors.atlas.net.co/manjaro/testing/$repo/$arch
    57: https://manjaro.mirror.garr.it/manjaro/testing/$repo/$arch
    58: https://mirrors.up.pt/pub/manjaro/testing/$repo/$arch
    59: https://nocix.mm.fcix.net/manjaro/testing/$repo/$arch
    60: https://southfront.mm.fcix.net/manjaro/testing/$repo/$arch
    61: https://mirror.dimensiondata.com/mirrors/manjaro.org/testing/$repo/$arch
    62: https://mirror.yandex.ru/mirrors/manjaro/testing/$repo/$arch
    63: https://mirrors.sjtug.sjtu.edu.cn/manjaro/testing/$repo/$arch
    64: https://mirrors.sonic.net/manjaro/testing/$repo/$arch
    65: https://mirrors.dotsrc.org/manjaro/testing/$repo/$arch
    66: https://coresite.mm.fcix.net/manjaro/testing/$repo/$arch
    67: https://mirror.init7.net/manjaro/testing/$repo/$arch
    68: https://mirror1.sox.rs/manjaro/testing/$repo/$arch
    69: https://manjaro.mirrors.uk2.net/testing/$repo/$arch
    70: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/testing/$repo/$arch
    71: https://mirror.telepoint.bg/manjaro/testing/$repo/$arch
    72: https://mirrors.xtom.jp/manjaro/testing/$repo/$arch
    73: https://manjaro.mirror.liquidtelecom.com/testing/$repo/$arch
    74: https://mirrors.tuna.tsinghua.edu.cn/manjaro/testing/$repo/$arch
    75: https://fosszone.csd.auth.gr/manjaro/testing/$repo/$arch
    76: https://ohioix.mm.fcix.net/manjaro/testing/$repo/$arch
    77: https://mirror.raiolanetworks.com/manjaro/testing/$repo/$arch
    78: https://ftp.psnc.pl/linux/manjaro/testing/$repo/$arch
    79: https://ftp.caliu.cat/pub/distribucions/manjaro/testing/$repo/$arch
    80: https://ziply.mm.fcix.net/manjaro/testing/$repo/$arch
    81: https://repo.ialab.dsu.edu/manjaro/testing/$repo/$arch
    82: https://mirror.netcologne.de/manjaro/testing/$repo/$arch
    83: https://ftpmirror1.infania.net/mirror/manjaro/testing/$repo/$arch
    84: https://mirror.truenetwork.ru/manjaro/testing/$repo/$arch
    85: https://mirror.csclub.uwaterloo.ca/manjaro/testing/$repo/$arch
    86: https://manjaro.c3sl.ufpr.br/testing/$repo/$arch
    87: https://ftp.snt.utwente.nl/pub/linux/manjaro/testing/$repo/$arch
    88: https://mirror.it4i.cz/manjaro/testing/$repo/$arch
    89: https://mirrors2.manjaro.org/testing/$repo/$arch
    90: https://mirror.phoepsilonix.love/manjaro/testing/$repo/$arch
    91: https://mirror.datacenter.by/pub/mirrors/manjaro/testing/$repo/$arch
    92: https://mirror.nyist.edu.cn/manjaro/testing/$repo/$arch
    93: https://mirrors.ucr.ac.cr/manjaro/testing/$repo/$arch
    94: http://ossmirror.mycloud.services/os/linux/manjaro/testing/$repo/$arch
    95: https://nnenix.mm.fcix.net/manjaro/testing/$repo/$arch
    96: https://volico.mm.fcix.net/manjaro/testing/$repo/$arch
    97: https://mirror.easyname.at/manjaro/testing/$repo/$arch
    98: https://ftp.yz.yamagata-u.ac.jp/pub/linux/manjaro/testing/$repo/$arch
Processes:
  CPU top: 5 of 230
  1: cpu: 4.1% command: firefox pid: 2098 mem: 304.8 MiB (1.9%)
  2: cpu: 2.4% command: firefox pid: 2599 mem: 611.1 MiB (3.8%)
  3: cpu: 1.5% command: firefox pid: 1793 mem: 600.5 MiB (3.7%)
  4: cpu: 1.1% command: kscreenlocker_greet pid: 3813 mem: 257.7 MiB (1.6%)
  5: cpu: 0.6% command: firefox pid: 2413 mem: 138.3 MiB (0.8%)
  Memory top: 5 of 230
  1: mem: 611.1 MiB (3.8%) command: firefox pid: 2599 cpu: 2.4%
  2: mem: 600.5 MiB (3.7%) command: firefox pid: 1793 cpu: 1.5%
  3: mem: 514.4 MiB (3.2%) command: thunderbird pid: 1611 cpu: 0.2%
  4: mem: 326.3 MiB (2.0%) command: plasmashell pid: 1161 cpu: 0.2%
  5: mem: 304.8 MiB (1.9%) command: firefox pid: 2098 cpu: 4.1%
Info:
  Processes: 230 Power: uptime: 5h 42m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 6.15 GiB
    services: org_kde_powerdevil, power-profiles-daemon, upowerd Init: systemd v: 260
    default: graphical tool: systemctl
  Compilers: clang: 22.1.5 gcc: 16.1.1 Shell: Bash v: 5.3.9 running-in: pty pts/1 (SSH)
    inxi: 3.3.40

Yes, I did, I reset to defaults, but same behaviour

I also found, that the display brightness could not be adjusted on the keyboard anymore. With 6.12.87 manjaro kernel no problem. It shows increasing or decreacing percent after pressing in the screen but nothing changes in brightness…

Possibly the new kernel dropped support for these older gpu graphics? If there is a setting I can make to do verbose logging of events. I did a web search an ran a command (i didn’t remember now :zipper_mouth_face:) but that reports the recognition of the lid close and lid open as a HID event.

Thanks for any answer anyways

Mod edit: Consecutive posts merged to keep things tidy. :wink:

8

If you want live logging you could run journalctl -f to monitor what’s going on.
I get powerdevilentries show up when I change the screen brightness.

9

I am not experiencing that issue.

System:
  Host: daphne Kernel: 7.0.5-2-MANJARO arch: x86_64 bits: 64
    compiler: gcc v: 16.1.1 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-7.0-x86_64
    root=UUID=5aa9dd24-270a-4fe0-b9b1-5745bdc4f888 rw quiet
    splash udev.log_priority=3 sysrq_always_enabled=1
    resume=UUID=4dc86597-0ba0-495d-8e95-cb30a5f34cef
  Desktop: KDE Plasma v: 6.6.5 tk: Qt v: N/A info: frameworks
    v: 6.26.0 wm: kwin_wayland vt: 2 dm: N/A Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: SLIMBOOK product: Elemental15-I13D5 v: N/A
    serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: SLIMBOOK model: Elemental15-I13D5
    serial: <superuser required> uuid: <superuser required>
    Firmware: UEFI vendor: INSYDE v: 1.07.02TGO date: 10/28/2025
Battery:
  ID-1: BAT0 charge: 48.5 Wh (100%)
    condition: 48.5/48.3 Wh (100.5%) volts: 17.29 min: 15.2
    model: Notebook BAT type: Li-ion serial: 0001 charging:
    status: full cycles: N/A
Memory:
  System RAM: total: 8 GiB available: 7.46 GiB
    used: 6.4 GiB (85.8%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 1 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Controller0-ChannelA-DIMM0 type: DDR5
    detail: synchronous size: 8 GiB speed: 5200 MT/s volts: curr: 1
    width (bits): data: 64 total: 64
    manufacturer: Wilk Elektronik S.A. part-no: GR5600S564L46S/8G
    serial: 66734909
  Device-2: Controller1-ChannelA-DIMM0
    type: no module installed
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core 5 120U bits: 64 type: MST AMCP
    arch: Raptor Lake level: v3 note: check built: 2022+
    process: Intel 7 (10nm) family: 6 model-id: 0xBA (186)
    stepping: 3 microcode: 0x6134
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 10 threads: 12
    mt: 2 tpc: 2 st: 8 smt: enabled cache: L1: 928 KiB desc: d-8x32
    KiB, 2x48 KiB; i-2x32 KiB, 8x64 KiB L2: 6.5 MiB
    desc: 2x1.2 MiB, 2x2 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 626 min/max: 400/5000:3800 scaling:
    driver: intel_pstate governor: powersave cores: 1: 626 2: 626
    3: 626 4: 626 5: 626 6: 626 7: 626 8: 626 9: 626 10: 626
    11: 626 12: 626 bogomips: 59904
10

There are kernel modules that control these buttons on laptops. My guess is something has changed in one of these modules for your particular device, or it isn’t being loaded at all.

Can you compare the output of lsmod | sort between running a kernel that works and one that doesn’t.

The modules you’re looking for will be something like (for my system) dell-laptop, dell-wmi, etc. Yours will be different perhaps fujitsu-laptop. There may be other modules that are relevant that aren’t named fujitsu too.

11

short update:
In all kernels I tested are those modules loaded:
6.12.88, 7.0.8-lqx, 7.1.0-rc3-1:

fujitsu_laptop         32768  0
sparse_keymap          12288  1 fujitsu_laptop
video                  81920  2 fujitsu_laptop,i915

In 7.1.0-rc3-1 the display brightness adjustment does not work (still showing changes in percent), in other it does.

Closing lid does only trigger sleep/hibernate in 6.12.88

12

That’s good! It’s loaded the module ok then. Were there any other change in which modules were loaded?

I can’t find any mention of fujitsu-laptop in the kernel changelogs between those kernels so hopefully it rules a change out too. Yet it does seem to be a driver issue.

I’m not sure where to go from here if it’s a driver issue.

We can then troubleshoot with systemd which handles a lot of power related settings.

  1. Backup /etc/systemd/logind.conf

  2. Edit /etc/systemd/logind.conf

Find the following lines:

#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore

Uncomment them (remove the #)

  1. Save and close the file

  2. Restart the login daemon with:

sudo systemctl restart systemd-logind

  1. Test the lid switch.

If that didn’t work, you can try leaving those entries uncommented but change all the values to ignore. Restart the login daemon again and test again.

Hopefully one of those scenarios works.

13

I gave a try, but neither of the two options is getting me back the close-lid and suspend function

On the contrary: After uncommenting that three entries in the logind.conf I restarted the daemon as described but I got journal flooding with these entries, until I restarted the system.

Mai 17 14:53:55 shiva kwin_wayland[988]: Applying output configuration failed!
Mai 17 14:53:55 shiva kwin_wayland[988]: Failed to find a working output layer configuration! Enabled layers:
Mai 17 14:53:55 shiva kwin_wayland[988]: src KWin::RectF(0,0 1920x1080) -> dst KWin::Rect(0,0 1920x1080)
Mai 17 14:53:55 shiva kwin_wayland[988]: drmModeListLessees() failed: Permission denied
Mai 17 14:53:55 shiva kwin_wayland[988]: Atomic modeset test failed! Permission denied
Mai 17 14:53:55 shiva kwin_wayland[988]: Applying output configuration failed!
Mai 17 14:53:55 shiva kwin_wayland[988]: Failed to find a working output layer configuration! Enabled layers:
Mai 17 14:53:55 shiva kwin_wayland[988]: src KWin::RectF(0,0 1920x1080) -> dst KWin::Rect(0,0 1920x1080)
Mai 17 14:53:55 shiva kwin_wayland[988]: drmModeListLessees() failed: Permission denied
Mai 17 14:53:55 shiva kwin_wayland[988]: Atomic modeset test failed! Permission denied
Mai 17 14:53:55 shiva kwin_wayland[988]: Applying output configuration failed!
Mai 17 14:53:55 shiva kwin_wayland[988]: Failed to find a working output layer configuration! Enabled layers:
Mai 17 14:53:55 shiva kwin_wayland[988]: src KWin::RectF(0,0 1920x1080) -> dst KWin::Rect(0,0 1920x1080)
Mai 17 14:53:55 shiva kwin_wayland[988]: drmModeListLessees() failed: Permission denied
Mai 17 14:53:55 shiva kwin_wayland[988]: Atomic modeset test failed! Permission denied

But after restaring, plasmashell uses 100% of CPU-Time.
Only when I undid the entry, then restarted, the behaviour is as before. Weiered…

The next step I do, I will do an separate new installation, I habe plenty of space on my nvme…

Appendix: I installed cachyos with plasma on other partition and it’s the same: with kernel 7.x lid is not working, with LTS kernel 6.18.31 it works flawlessly!

Appendix 2: With xfce it is the same

Appendix 3: The same in Debian 13 with Kernel 7.x and plasma 6.3.6

14

Its sounding more like a kernel driver issue then. I’m not up to date with how kernel drivers are written but many years ago I had a similar issue with some hardware and had to recompile an older kernel driver for a newer kernel. I wonder whether you could use the older fujitsu-laptop driver on the newer kernel.

Might be worth reporting on the linux kernel bug tracker though, particularly since you’ve taken the time to test multiple kernels and distros.

1 Like
15

Many thanks for all your answers,
I opened this “Bug”

2 Likes