On wake up after suspend, hyprlock has no UI and cannot be unlocked. #695
Labels
bug
Something isn't working
Comments
|
Same here! I tried setting monitor option on hyprlock config, because I can move the mouse, but Hyprland won't respond to any command. One note, it's working for me until dpms off is triggered. In other words, seems to be working until the monitor powers off. hyprlock.confhypridle.confI've tried also staring hypridle like this hypridle >> ~/.hypridle.log but I can't see anything relevant (at least for me) in the logs. hypridle.log |
|
I also have the same behavior and similar configs. Not sure if it's the same with others, but I also have another issue where after waking from suspend, switching tty, and unlocking with I've been tracking #678 since it's similar and I'm hoping number 2 in that list of things to fix will help somehow. |
|
I can confirm this, my current workaround is to turn off and on my monitor. After that the UI is visible again. |
Nice, based on reports here could we day hyprctl dispatch dpms off causes this? Manual suspension doesn't have this issue since it doesn't use that. |
For me this workaround is not working. In my case it looks like hyprlock is running but, it wont' show in the defined monitor. (I'm currently using only one monitor connected through DP) I think the bug it's related to dpms off and the monitor powering off since it has no signal. I go to another TTY and I can see that hyprlock is running. But I always have to run 'hyprctl --instance 0 dispatch exit' or reboot to get back in my desktop. My graphics card: ╰─❯ lspci | grep -i vga
2d:00.0 VGA compatible controller: NVIDIA Corporation GA104 [GeForce RTX 3070 Lite Hash Rate] (rev a1)Hope this info is helfpul. |
Exactly! I tried the workaround and no luck, im also on nvidia and on my old installation it used to work. I'll try removing dpms management from hypridle until this is fixed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Regression?
No
Hyprlock Info and Version
0.7.0
Hyprlock config
general { grace = 0 hide_cursor = true no_fade_in = true no_fade_out = true } auth { pam:enabled = true } background { monitor = DP-1 color = rgba(25, 23, 36, 1) # Base color (dark background) } input-field { monitor = DP-1 size = 20%, 5% outline_thickness = 1 inner_color = rgba(25, 23, 36, 0.0) # Transparent inner color placeholder_text = type here outer_color = rgba(235, 188, 186, 1) # Rose color for outer border check_color = rgba(156, 207, 216, 1) # Pine color for check fail_color = rgba(235, 111, 146, 1) # Fail color (reddish) fail_text = password incorrect dots_rounding = 0 dots_text_format = * dots_fade_time = 0 dots_center = false font_color = rgb(224, 222, 244) # Text color (light) fade_on_empty = false rounding = 0 position = 0, -20 halign = center valign = center font_family = Iosevka Term } label { monitor = DP-1 text = cmd[] uname --kernel-release color = rgba(224, 222, 244, 1.0) # Text color (light) font_size = 16 font_family = Iosevka Term position = 0, -150 halign = center valign = center } label { monitor = DP-1 text = cmd[update:1000] date +"%H:%M" color = rgba(156, 207, 216, 1.0) # Pine color for time font_size = 55 font_family = Iosevka Term position = 0, 250 halign = center valign = center } label { monitor = DP-1 text = $USER color = rgba(235, 188, 186, 1.0) # Rose color for username font_size = 25 font_family = Iosevka Term position = 0, 80 halign = center valign = center } shape { monitor = DP-1 size = 40%, 35% position = 0, 0 color = rgba(25, 23, 36, 0) # Transparent background rounding = 0 border_size = 1 border_color = rgba(224, 222, 244, 0.8) # Light border color }Compositor Info and Version
System/Version info
Description
After suspension from HYPRIDLE? I'm not sure why when manually done, the bug does not happen. It might, the bug doesn't happen 100% of times as there were times that hyprlock would normally start.
When I let hypridle suspend with systemctl after 900 seconds, after some time being suspended on wake up hyprlock will lock the screen and there will be no UI, or any way to unlock (even ending the process in another tty and following the instructions on the "oops your screenlocker died" screen). Cursor can be moved around and the screen is active but can't do any keybinds/actions except the ones binded with bindl.
This hasn't happened before on my old installations. And it doesn't happen 100% of the times, I'd say 90%.
Tried checking my configs and even rebuilding them, also hypridle config.
If needed hypridle config is here
How to reproduce
Leave hypridle to suspend your pc then try waking up.
Crash reports, logs, images, videos
No response
The text was updated successfully, but these errors were encountered: