-
-
Notifications
You must be signed in to change notification settings - Fork 958
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lock screen loses keyboard focus after playing with hyprctl monitor #1548
Comments
more precision: the keyboard will work again if eDP-1 is reactivated after that sequence |
how bout this patch? |
hum that does not seem to help. |
after reading the code for refocus, I was trying some stuff with the mouse, and I got this crash
|
my suspicion, that may be completely off, is that it may depend on where the mouse actually is when I turn the laptop monitor off. And since this crash seems to be related to input manager and some mouse thingy... |
I confirm that this always crashes when I'm facing the issue with the keyboard not inputing anything on the lock screen then I click with the mouse |
trying to follow the logs
It seems to me that we miss a ``Set keyboard focus to surface XXX` |
actually, for both the crash and kb |
the first one did not work. let me try the second |
the second one fixes the mouse crash, but still not the kb |
so you're telling me the first fixes the kb but not the second? |
no I edited the message :) it did NOT fix the kb |
pushed the second to fix the crash. Not sure what does the kb bug. |
here's my config put both script in PATH or adapt: lid.sh #!/bin/env bash
if grep -q open /proc/acpi/button/lid/LID0/state; then
clam.sh off
else
if [[ "$(clam.sh count)" == "1" ]]; then
systemctl suspend
else
clam.sh on
fi
fi clam.sh #!/bin/env bash
case "$1" in
count)
cat /sys/class/drm/*/status | grep -c '^connected'
;;
on)
if [[ $(clam.sh count) -gt 1 ]]; then
hyprctl keyword monitor eDP-1,disable
fi
;;
off)
hyprctl keyword monitor eDP-1,preferred,auto,1
;;
esac then in Hyprland.conf
|
this seems to happen everytime now after resume |
well, not for me. |
hmmm. It may be due to my usbguard setup. It used to work fine before, but something may have changed when we moved to the new screenlocker protocol, ending up breaking my scripts. With usbguard off, it seems this does not happen anymore. I'll reopen if I notice it again |
It's happening again. It used to be fairly rare for a while, but now it's back at it after every resume |
so this seems to be due to the fact that to prevent a crash in Hyprland when plugging/unplugging monitors while suspended, I force to enable eDP-1 before going into sleep, and rerun my routines to enable/disable it based on the lid switch status on resume File: .bin/lockscreen.sh
File: .bin/suspend.sh
File: .bin/clam.sh
File: .bin/lid.sh
In hyprland conf I run swayidle like this
This systematically makes swaylock unresponsive until I open the lid. I really whish I don't need all of this and could have a proper clamshell mode management like sway describes here https://github.com/swaywm/sway/wiki#clamshell-mode |
seems relevant swaywm/swaylock#282 |
I guess all of my troubles are caused by the need to call clam.sh off when I suspend. otherwise hyprland crashes systematically when I suspend with a monitor plugged, unplug it while suspended, then resume
|
is this still a thing? |
Yep, still a thing for me. My particular situation involves DPMS MST, a USB-C hub with various outputs, and the machine's physical connector getting (dis/re)connected when I switch between home & work. I suspect that the issue is linked to the lockscreen triggering when the monitors are disconnected and then losing focus when they're reconnected. Have seen a few things in this area though; gut feel is that perhaps some logic is needed to ensure that overlay layer is always focused when screen is locked. |
Have a laptop, an external display.
run
`After that sequence, the keyboard does not input anything anymore. I could not reproduce on Sway
The text was updated successfully, but these errors were encountered: