MX 21 - Wake from screensaver state

[Red_Stag]

Dear All,

Been using MX Linux 19.4 for quite some time and decided to try transition to MX Linux 21 recently. Has not felt like a good transition. After installing 21 and when the PC goes into screen saver mode I cannot get back to the login screen unless I press CTRL+ALT+DEL (at least once and sometimes twice). Is this the behaviour one would expect? MX 19 did not work like this?

I am thinking some kind of keyboard mapping issue and have included output from few keyboard commands that I searched up.

Any advice / opinions / comments as to what is happening would be greatly appreciated?

Code: Select all

Snapshot created on: 20220115_1229
System:    Kernel: 5.10.0-10-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-10-amd64 
           root=UUID=<filter> ro quiet splash 
           Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: xfwm 4.16.1 vt: 7 
           dm: LightDM 1.26.0 Distro: MX-21_x64 Wildflower October 20  2021 
           base: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop System: Hewlett-Packard product: HP Compaq 8000 Elite CMT PC v: N/A 
           serial: <filter> Chassis: type: 6 serial: <filter> 
           Mobo: Hewlett-Packard model: 3647h serial: <filter> BIOS: Hewlett-Packard 
           v: 786G7 v01.14 date: 10/14/2015 
CPU:       Info: Dual Core model: Intel Core2 Duo E8400 bits: 64 type: MCP arch: Penryn 
           family: 6 model-id: 17 (23) stepping: A (10) microcode: A0E cache: L2: 6 MiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 11970 
           Speed: 2993 MHz min/max: 1998/3000 MHz Core speeds (MHz): 1: 2993 2: 2993 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: EPT disabled 
           Type: mds status: Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled 
           Type: meltdown mitigation: PTI 
           Type: spec_store_bypass status: Vulnerable 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 mitigation: Full generic retpoline, STIBP: disabled, RSB filling 
           Type: srbds status: Not affected 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel 4 Series Integrated Graphics vendor: Hewlett-Packard driver: i915 
           v: kernel bus-ID: 00:02.0 chip-ID: 8086:2e12 class-ID: 0300 
           Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: loaded: intel 
           display-ID: :0.0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") 
           s-diag: 582mm (22.9") 
           Monitor-1: VGA1 res: 1920x1080 hz: 60 dpi: 96 size: 509x286mm (20.0x11.3") 
           diag: 584mm (23") 
           OpenGL: renderer: Mesa DRI Intel Q45/Q43 (ELK) v: 2.1 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel 82801JD/DO HD Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3a6e class-ID: 0403 
           Sound Server-1: ALSA v: k5.10.0-10-amd64 running: yes 
           Sound Server-2: PulseAudio v: 14.2 running: yes 
Network:   Device-1: Intel 82567LM-3 Gigabit Network vendor: Hewlett-Packard driver: e1000e 
           v: kernel port: 2100 bus-ID: 00:19.0 chip-ID: 8086:10de class-ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel modules: wl port: 21e0 
           bus-ID: 20:00.0 chip-ID: 8086:24f3 class-ID: 0280 
           IF: wlan0 state: up mac: <filter> 
RAID:      Supported mdraid levels: raid1 linear multipath raid0 raid6 raid5 raid4 raid10 
           Device-1: md0 maj-min: 9:0 type: mdraid level: mirror status: active size: 1.82 TiB 
           Info: report: 2/2 UU blocks: 1953383488 chunk-size: N/A super-blocks: 1.2 
           Components: Online: 
           0: sdc maj-min: 8:32 size: 1.82 TiB 
           1: sdd maj-min: 8:48 size: 1.82 TiB 
Drives:    Local Storage: total: raw: 7.97 TiB usable: 6.15 TiB used: 1.65 TiB (26.8%) 
           SMART Message: Unable to run smartctl. Root privileges required. 
           ID-1: /dev/sda maj-min: 8:0 vendor: Silicon Power model: SPCC Solid State Disk 
           size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 3.0 Gb/s type: SSD 
           serial: <filter> rev: V4.9 temp: 45 C scheme: GPT 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST4000DM004-2CV104 size: 3.64 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 5425 
           serial: <filter> rev: 0001 temp: 33 C scheme: GPT 
           ID-3: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: 0001 temp: 36 C 
           ID-4: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000DM008-2FR102 size: 1.82 TiB 
           block-size: physical: 4096 B logical: 512 B speed: 3.0 Gb/s type: HDD rpm: 7200 
           serial: <filter> rev: 0001 temp: 37 C 
           ID-5: /dev/sde maj-min: 8:64 type: USB vendor: Western Digital 
           model: WD My Passport 0730 size: 465.73 GiB block-size: physical: 512 B 
           logical: 512 B type: N/A serial: <filter> rev: 1008 scheme: GPT 
Partition: ID-1: / raw-size: 30.27 GiB size: 29.63 GiB (97.87%) used: 8.02 GiB (27.1%) fs: ext4 
           dev: /dev/sda5 maj-min: 8:5 
Swap:      Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 4.88 GiB used: 3.5 MiB (0.1%) priority: -2 
           dev: /dev/sda2 maj-min: 8:2 
Sensors:   System Temperatures: cpu: 50.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Repos:     Packages: note: see --pkg apt: 1999 lib: 990 flatpak: 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 bullseye-updates main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/debian.list 
           1: deb http://deb.debian.org/debian bullseye main contrib non-free
           2: deb http://security.debian.org/debian-security bullseye-security main contrib non-free
           Active apt repos in: /etc/apt/sources.list.d/mx.list 
           1: deb http://mirror.datamossa.io/mxlinux/mx/repo/ bullseye main non-free
           Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
           1: deb http://linux.teamviewer.com/deb stable main
Info:      Processes: 260 Uptime: 4d 15h 49m wakeups: 1 Memory: 7.65 GiB used: 2.8 GiB (36.7%) 
           Init: SysVinit v: 2.96 runlevel: 5 default: 5 tool: systemctl Compilers: gcc: 10.2.1 
           alt: 10 Shell: quick-system-in default: Bash v: 5.1.4 running-in: quick-system-in 
           inxi: 3.3.06 

Output from $ cat ~/.config/xfce4/xfconf/xfce-perchannel-xml/keyboards.xml

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

<channel name="keyboards" version="1.0">
  <property name="Default" type="empty">
    <property name="Numlock" type="bool" value="false"/>
  </property>
</channel>

Output from $ cat /etc/default/keyboard

Code: Select all

# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS="grp:rctrl_rshift_toggle,terminate:ctrl_alt_bksp,grp_led:scroll"

BACKSPACE="guess"

Output from $ setxkbmap -query

Code: Select all

# KEYBOARD CONFIGURATION FILE

# Consult the keyboard(5) manual page.

XKBMODEL="pc105"
XKBLAYOUT="us"
XKBVARIANT=""
XKBOPTIONS="grp:rctrl_rshift_toggle,terminate:ctrl_alt_bksp,grp_led:scroll"

BACKSPACE="guess"

[Huckleberry Finn]

... when the PC goes into screen saver mode...

... Or are we talking about wake up after suspend? (Since there's no screensaver on 21 by default)

• What if you uncheck "lock screen before sleep" in Power Manager?

• What if you suspend with
  

  Code: Select all

  sudo pm-suspend

  ?

• Also what happens when you just lock the screen? Any problems there?

[Huckleberry Finn]

Oh la la, just do this : viewtopic.php?p=664466#p664466

(Yes, though it already shows Intel :) )

Display: x11 server: X.Org 1.20.11 compositor: xfwm4 v: 4.16.1 driver: loaded: intel

[Red_Stag]

Thank you HF,

Just to clarify I do not use the suspend state and never have (to my knowledge). If the machine goes into a suspend state then that can only be the result of a default setting. I recall seeing a lot of talk about suspend states and it seemed to raise a level of discomfort with many, on this basis I steered away from it.

I have made the change recommended as per (viewtopic.php?p=664466#p664466) but the experience of trying to get back into the PC after having walked away for a few minutes seems just as inconsistent. I also notice that my conky is now flickering intermittently, sigh.

[Huckleberry Finn]

Meanwhile, you can undo it the same way.

Also, (at least, since it was ok with MX 19) you can install antiX 4.19 kernel from MX Package Installer - Popular Apps tab with 2 clicks, then boot with (via "Advanced Options" in Grub) and try.

You can even make it the default one with "MX Boot Options" - "Boot to".

(Please try the 3 tests (even with both kernels), nothing to afraid / no harm :) )

[Red_Stag]

Dear HF,

First off thank you, the explanations and leads have helped enormously. I now understand a few more things, namely:

1) understand that there is no screensaver in default MX21 install, and
2) The behaviour I observed was a PC that was running yet did not respond to ANY keyboard inputs except CTRL+ALT+DEL. So pressing CTRL+ALT+DEL the first time locked the screen and pressing CTRL+ALT+DEL a second time wakes the screen. Just for clarity, it is the second CTRL+ALT+DEL input that results in the display shows anything, and
3) The first time I used (Menu => "MX Tweak" : "Other" tab : "Use Intel instead of modesetting ... " ... Apply , reboot. ) I mistakenly did not select "apply"
4) So, in summary I am re-testing this (Menu => "MX Tweak" : "Other" tab : "Use Intel instead of modesetting ... " ... Apply , reboot. ) setting now and the behaviour seems much more predictable.
5) Also, I installed Xscreensaver because I don't like the PC being accessible without a password.

Thank you again for your time and patience, your responses it is very much appreciated. Kudos to you

[Huckleberry Finn]

You're welcome :)

...installed Xscreensaver because I don't like the PC being accessible without a password...

Yes, but that was just to first determine whether the culprit was light-locker. If so, I was going to suggest this.

But of course, if everything's fine and if you like Xscreensaver, just go on with that...