No input after closing the lid

Report Bugs, Issues and non- package Requests
Message
Author
jerem_
Posts: 4
Joined: Sun Apr 18, 2021 3:26 am

No input after closing the lid

#1 Post by jerem_ »

Hi,

Mouse clicks and text input does not work after closing the lid.
However, I can move the cursor and use Ctrl-Alt-Backspace to kill the desktop.

Any idea on how to solve this ?

Code: Select all

System:
  Kernel: 6.1.0-21-amd64 [6.1.90-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-21-amd64 root=UUID=<filter> ro quiet splash
    resume=UUID=<filter> resume_offset=16898048
  Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm v: 4.18.0 vt: 7
    dm: LightDM v: 1.26.0 Distro: MX-23.2_x64 Libretto January 21  2024 base: Debian GNU/Linux 12
    (bookworm)
Machine:
  Type: Laptop System: Dell product: Latitude 5400 v: N/A serial: <superuser required> Chassis:
    type: 10 serial: <superuser required>
  Mobo: Dell model: 0PD9KD v: A00 serial: <superuser required> UEFI: Dell v: 1.23.0
    date: 12/19/2022
Battery:
  ID-1: BAT0 charge: 26.2 Wh (48.5%) condition: 54.0/68.0 Wh (79.4%) volts: 7.5 min: 7.6
    model: BYD DELL 9JRYT04 type: Li-poly serial: <filter> status: discharging
CPU:
  Info: model: Intel Core i5-8365U bits: 64 type: MT MCP arch: Comet/Whiskey Lake note: check
    gen: core 8 level: v3 note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x8E (142)
    stepping: 0xC (12) microcode: 0xF8
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
    desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 749 high: 800 min/max: 400/4100 scaling: driver: intel_pstate
    governor: powersave cores: 1: 800 2: 800 3: 794 4: 400 5: 800 6: 800 7: 800 8: 800
    bogomips: 30399
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: Enhanced 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: Enhanced / Automatic IBRS; IBPB: conditional; RSB filling;
    PBRSB-eIBRS: SW sequence; BHI: SW loop, KVM: SW loop
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort mitigation: TSX disabled
Graphics:
  Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:3ea0 class-ID: 0300
  Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:2
    chip-ID: 0c45:6a09 class-ID: 0e02
  Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
  Monitor-1: eDP-1 model: AU Optronics 0x463d built: 2018 res: 1920x1080 hz: 60 dpi: 158
    gamma: 1.2 size: 309x174mm (12.17x6.85") diag: 355mm (14") ratio: 16:9 modes: 1920x1080
  API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel UHD Graphics 620 (WHL GT2)
    direct-render: Yes
Audio:
  Device-1: Intel Cannon Point-LP High Definition Audio vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:9dc8
    class-ID: 0403
  API: ALSA v: k6.1.0-21-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Cannon Point-LP CNVi [Wireless-AC] driver: iwlwifi v: kernel modules: wl
    bus-ID: 00:14.3 chip-ID: 8086:9df0 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Device-2: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel port: N/A
    bus-ID: 00:1f.6 chip-ID: 8086:15bd class-ID: 0200
  IF: eth0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth 9460/9560 Jefferson Peak (JfP) type: USB driver: btusb v: 0.8
    bus-ID: 1-10:4 chip-ID: 8087:0aaa class-ID: e001
  Report: hciconfig ID: hci0 rfk-id: 3 state: up address: <filter> bt-v: 3.0 lmp-v: 5.1
    sub-v: 100 hci-v: 5.1 rev: 100
  Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff link-mode: peripheral accept
    service-classes: rendering, capturing, object transfer, audio, telephony
Drives:
  Local Storage: total: 238.47 GiB used: 27.35 GiB (11.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Toshiba model: KBG40ZNS256G NVMe KIOXIA 256GB
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
    serial: <filter> rev: 10410106 temp: 29.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 73.85 GiB size: 72.14 GiB (97.68%) used: 27.02 GiB (37.5%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 164.37 GiB size: 160.73 GiB (97.79%) used: 334.1 MiB (0.2%) fs: ext4
    dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 19.44 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 36.0 C pch: 34.0 C mobo: 30.0 C
  Fan Speeds (RPM): cpu: 0
Repos:
  Packages: pm: dpkg pkgs: 2112 libs: 1048 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://ftp.acc.umu.se/mirror/mxlinux.org/packages/mx/repo/ bookworm main non-free
Info:
  Processes: 263 Uptime: 6m wakeups: 459 Memory: 15.44 GiB used: 2.04 GiB (13.2%) Init: SysVinit
  v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

User avatar
j2mcgreg
Global Moderator
Posts: 6820
Joined: Tue Oct 23, 2007 12:04 pm

Re: No input after closing the lid

#2 Post by j2mcgreg »

Temporarily disable Power Manager and see if the problem repeats.
HP 15; ryzen 3 5300U APU; 500 Gb SSD; 8GB ram
HP 17; ryzen 3 3200; 500 GB SSD; 12 GB ram
Idea Center 3; 12 gen i5; 256 GB ssd;

In Linux, newer isn't always better. The best solution is the one that works.

Charlie Brown

Re: No input after closing the lid

#3 Post by Charlie Brown »

What is it set to? Suspend / lock screen etc.. ? (Check both sub-tabs: When on Battery / When Plugged in ).

If you haven't already: Remove the buggy xfce4-screensaver that's known to cause such issues .

User avatar
CharlesV
Global Moderator
Posts: 7387
Joined: Sun Jul 07, 2019 5:11 pm

Re: No input after closing the lid

#4 Post by CharlesV »

You also might try when it does this, dont click the mouse and just type in your password. (I had a similar issue a while back.)

My real resolution was to always lock before I closed the lid. /-/
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

jerem_
Posts: 4
Joined: Sun Apr 18, 2021 3:26 am

Re: No input after closing the lid

#5 Post by jerem_ »

I got the same problem with "Suspend" and "Lock screen", The screen doesn't even lock with the last setting!
"Switch off display" Seems to work fine.
Uninstalling xfce4-screensaver doesn't solve this issue.

User avatar
CharlesV
Global Moderator
Posts: 7387
Joined: Sun Jul 07, 2019 5:11 pm

Re: No input after closing the lid

#6 Post by CharlesV »

On my Dell tester ( Inspiron 5570 ) .. this issue went away when I switched to the liquorix 6.6.11 kernel. (Actually, I believe it resolved at a previous 6.6 liquorix kernel, but I just check it and it no longer is an issue.)
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

Charlie Brown

Re: No input after closing the lid

#7 Post by Charlie Brown »

That lid problem is in fact a long time known issue. Not only MX-23 ...

Say, when you first suspend, then close the lid, then open, everything's fine (no matter you preferred to lock the screen or not). But when you directly close the lid yes it suspends but then that problem when you open the lid. (Shortly you're not alone).

I tried so many things (conf files, playing with Vblank settings, different kernels etc.), also been using Liquorix kernels since a long time.

... But (my) verdict is: It's absolutely something with the Xfwm, cause it's fine with the same settings (same power manager) when you login with Openbox and Fluxbox or other WMs. You can directly close the lid.. then open, the login screen welcomes you, enter password and that's it. (As it should be).

But, recently I discovered such a weird thing:

When you select something other than "suspend" (say, switch off display or lock screen) for "When on Battery", then you select suspend for "When plugged in", then it's ok. (The weird part is that they (settings) seem to affect each other and it must be a kind of bug. Another weirdness is that the problem turns back if you begin to use the laptop without the battery, as there won't be such separate settings).

User avatar
CharlesV
Global Moderator
Posts: 7387
Joined: Sun Jul 07, 2019 5:11 pm

Re: No input after closing the lid

#8 Post by CharlesV »

Charlie Brown wrote: Wed May 29, 2024 5:01 pm That lid problem is in fact a long time known issue. Not only MX-23 ...

Say, when you first suspend, then close the lid, then open, everything's fine (no matter you preferred to lock the screen or not). But when you directly close the lid yes it suspends but then that problem when you open the lid. (Shortly you're not alone).

I tried so many things (conf files, playing with Vblank settings, different kernels etc.), also been using Liquorix kernels since a long time.

... But (my) verdict is: It's absolutely something with the Xfwm, cause it's fine with the same settings (same power manager) when you login with Openbox and Fluxbox or other WMs. You can directly close the lid.. then open, the login screen welcomes you, enter password and that's it. (As it should be).

But, recently I discovered such a weird thing:

When you select something other than "suspend" (say, switch off display or lock screen) for "When on Battery", then you select suspend for "When plugged in", then it's ok. (The weird part is that they (settings) seem to affect each other and it must be a kind of bug. Another weirdness is that the problem turns back if you begin to use the laptop without the battery, as there won't be such separate settings).
Definitely something off with this one. Interestingly, on my Dell.. the 6.6. something kernel resolved it. On my HP, nothing has resolved it ... except ... locking the screen first. Then it doesnt seem to matter what I do.. ( sleep / suspend etc.) .... when I lift the lid I am presented a lock screen which unlocks perfectly.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

Charlie Brown

Re: No input after closing the lid

#9 Post by Charlie Brown »

In my trials first (just) locking the screen caused even more troubles :)

In the meantime I also tried different lockers: light-locker, i3lock, slock, xtrlock (currently, and my new favorite :D )

But again, no matter what settings and what preferences (whether to lock the screen or not and with what locker).. no problems when you login with a different WM.

(Btw. also tried to restart Xfwm via shortcut keys etc.. , in vain ... or xrandr ... with shortcut, nothing works with Xfwm)

User avatar
CharlesV
Global Moderator
Posts: 7387
Joined: Sun Jul 07, 2019 5:11 pm

Re: No input after closing the lid

#10 Post by CharlesV »

Interesting ... So like I said my Dell and HP's are both set as follows:

Power Manager:
_General: All on Do Nothing

_On Battery:
___Suspend after 28 min
___Laptop Lid = Suspend

_Plugged In
___Suspend never
___LaptopLid = Suspend

_Display
__On Battery
____Blank after: 5 min
____Put to Sleep after: 15 min
____Switch off after: 20 min
__Plugged in
____Blank, Put to sleep and Switch off all = Never

____ Brightness on inactivity (on both battery and plugged in) = 10%

_Security tab
__Light Loicker
____ Auto lock: never
____ Delay Locking after screen saver: 1 seconds
____ Lock screen when going to sleepL OFF


XScreenSaver:
__ Blank after 10 min
__ Cycle after 10 minutes
__ Lock Screen after 0 minutes: is ON

_Advanced Tab
___ Display Power Management is all OFF
___ Blanking
_____Fade to black when blanking and unblanking is on, 3 seconds


My Desktop I lock when I walk away, and in the rare times that I dont, the screen saver kicks on and displays an unlock dialog .

The Dell Inspiron now works perfectly. (MX 23 )

The HP... if I just close the lid, then when I open it I get the screen / desktop I was on, but nothing works, unless I just type in my password. (no dialog shows) . If I lock it first, then it doesnt seem to matter what I do it always works fine - with a login dialog. ( MX 21, but same condition with MX23 )

Now... having said that.. I *rarely* have my HP off power and in this state. However, it seems to work well in that case too. As long as I lock it first.
*QSI = Quick System Info from menu (Copy for Forum)
*MXPI = MX Package Installer
*Please check the solved checkbox on the post that solved it.
*Linux -This is the way!

Post Reply

Return to “Bugs and Non-Package Requests Forum”