[Solved] Problems with laptop screen and keyboard after screen locking

jones · 2019-08-07 09:49:40

Hello,

I am using light-locker and slock to automatically darken + lock my laptop screen.
I am experiencing 2 sets of problems.

The first kind of problem occurs after I locked the laptop via SUPER+L.

I have to enter my user pw twice, once for the normal LightDM-screen and once for slock's lock (seeing how the screen turns blue or red, depending on my entry).
If the screen was switched off (I have not enable suspend or hibernation on my laptop in general), I can't use the laptop's keyboard after I logged in.
Luckily the touchpad/mouse (if attached) works. To get the keyboard to work, I have to minimize and maximize one of the active open programs via XFCE's task bar, so I simply use the touchpad to click on an icon twice.

The second kind of problem is this:

When I leave the laptop for a while, the screen goes black automatically, as it should. After the defined amount of time (10s in my case), the screenlock via light-lockers happens.
For getting back in, I have to switch TTY's and then go back to tty7 so the screen turns on.
Then I am re-directed to a message saying "screen is locked, login screen will be shown in a few seconds" or something to that effect. After a few seconds, the LightDM screen is shown.
If I do not switch between the consoles, the screen would stay black.
After I logged in, the problem with using the keyboard does not occur.

Is this related?
So far I haven't found any tangible bits on how to solve this, would anyone here know to do that?

$ pacman -Q slock
slock 1.4-3
$ pacman -Q light-locker
light-locker 1.8.0-2
$ cat /usr/bin/xflock4
PATH=/bin:/usr/bin
export PATH

# First test for the command set in the session's xfconf channel
LOCK_CMD=$(xfconf-query -c xfce4-session -p /general/LockCommand)

# Lock by xscreensaver or gnome-screensaver, if a respective daemon is running
for lock_cmd in \
    "$LOCK_CMD" \
    "xscreensaver-command -lock" \
    "gnome-screensaver-command --lock"
do
    if [ ! -z "$lock_cmd" ]; then
        $lock_cmd >/dev/null 2>&1 && exit
    fi
done

# else run another access locking utility, if installed
for lock_cmd in \
  "xlock -mode blank" \
  "slock"
  do
    set -- $lock_cmd
    if command -v -- $1 >/dev/null 2>&1; then
        $lock_cmd >/dev/null 2>&1 &
	# turn off display backlight:
	xset dpms force off
        exit
    fi
done

# else access locking failed
exit 1

And maybe this is relevant:

$ modinfo i915
filename:       /lib/modules/5.2.6-arch1-1-ARCH/kernel/drivers/gpu/drm/i915/i915.ko.xz
license:        GPL and additional rights
description:    Intel Graphics
author:         Intel Corporation
author:         Tungsten Graphics, Inc.
firmware:       i915/bxt_dmc_ver1_07.bin
firmware:       i915/skl_dmc_ver1_27.bin
firmware:       i915/kbl_dmc_ver1_04.bin
firmware:       i915/glk_dmc_ver1_04.bin
firmware:       i915/cnl_dmc_ver1_07.bin
firmware:       i915/icl_dmc_ver1_07.bin
firmware:       i915/kbl_guc_ver9_39.bin
firmware:       i915/bxt_guc_ver9_29.bin
firmware:       i915/skl_guc_ver9_33.bin
firmware:       i915/kbl_huc_ver02_00_1810.bin
firmware:       i915/bxt_huc_ver01_8_2893.bin
firmware:       i915/skl_huc_ver01_07_1398.bin

Last edited by jones (2019-08-08 09:31:31)

seth · 2019-08-07 14:26:55

I am using light-locker and slock to automatically darken + lock my laptop screen.

And we'll hit the breaks right here to discuss: why??

I'm rather surprised that this works at all because I would expect both (any) locker to refuse action if unable to grab the keyboard.

jones · 2019-08-07 15:13:53

I honestly cannot recall.

seth · 2019-08-07 15:30:27

Well, stop doing that.
There's no point in running two screenlockers on top of each other.

If the problems are gone, you were probably facing some race condition out of that setup.

jones · 2019-08-08 09:33:18

seth wrote:

Well, stop doing that.
There's no point in running two screenlockers on top of each other.
If the problems are gone, you were probably facing some race condition out of that setup.

Did stop doing that.
Solution for me:

pacman -R slock

And per toz's post, I added "light-locker-command -l" to the xflock4 file so now it says:

# Lock by light-locker, xscreensaver or gnome-screensaver, if a respective daemon is running
for lock_cmd in \
    "light-locker-command -l"\
    "xscreensaver-command -lock" \
    "gnome-screensaver-command --lock"
do
    $lock_cmd >/dev/null 2>&1 && exit
done

Life is breezy again.

Thanks for helping, Seth.

Last edited by jones (2019-08-08 11:52:51)

Arch Linux

#1 2019-08-07 09:49:40

[Solved] Problems with laptop screen and keyboard after screen locking

#2 2019-08-07 14:26:55

Re: [Solved] Problems with laptop screen and keyboard after screen locking

#3 2019-08-07 15:13:53

Re: [Solved] Problems with laptop screen and keyboard after screen locking

#4 2019-08-07 15:30:27

Re: [Solved] Problems with laptop screen and keyboard after screen locking

#5 2019-08-08 09:33:18

Re: [Solved] Problems with laptop screen and keyboard after screen locking

Board footer