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 |
|
This is what probably happens:
TLDR: This is partially #684 and partially a Hyprland issue that's fixed in -git. |
|
I've r
This didn't work either, so I think the problem is solely with suspension. I also updated to -git and no luck still |
Weird thing in my case it's that if I leave it to get to suspension, It work's flawlessly. |
|
I'm experiencing a similar problem booting after hibernation with a kernel dump of: The detailed stack trace in gdb is: |
|
@wind-mask thanks for the trace. That one should be covered by #699 |
|
Seems this was an issue with nvidia-open and suspension that hyprland has issues with now. It is mentioned on their wiki and after switching to nvidia-dkms, it isn't happening anymore.
|
I still have the same problem regardless of using It definitely seems to be a dpms off problem for me because if I manually lock then turn off and back on monitor I see my desktop rather than hyprlock. This is slightly different from when I suspend where I briefly get the same lockscreen from when I locked it before it disappears, showing the desktop. I've also tested doing a suspend but waking before the monitor turns off completely and the issue no longer happens in that case. Log from running Oddly enough, the problem I mentioned previously about hyprlock continuing to run after unlocking no longer happens when running from terminal instead of using |
|
Hi all, I just merged #686 and am curious if that fixes it.
I also doubt that it is an nvidia problem. Although using nvidia proprietary means more threads involved which can lead to race conditions showing themselfs more easily.
I found this in your logs: That means you somehow send SIGUSR1 to hyprlock, which is a way to unlock hyprlock.
That was fixed by hyprwm/Hyprland#9399 and #687 |
Sorry, forgot to mention that after it showed the desktop I then unlocked like I normally do. To be more clear the general ranges (not exact ofc) are:
This still happens although I was incorrect on why it was working then; it continues running after a SIGUSR1 only when I wakeup from a suspend or hibernation otherwise it is indeed fixed.
Unfortunately, does not fix the issue for me :/ |
|
I've done some more testing/updating so I'm going to put all my relevant info here. I also modified the hyprlock logging code to include timestamps. Logs have been slightly edited for brevity by removing all the Notes:
systeminfo.log
This other issue also no longer happens. Either I was somehow running old versions even after updating and killing all my hyprland/hyprlock processes, or it only occurs when the main issue happens as well. |
Can confirm, it wasn't happening when I switched to nvidia proprietary for some time, but now still occurs when waking up from suspend, less often but still happens. Hope your comments help and we get this fixed. |
|
Same issue here. I'm on a desktop, just upgraded hypr* after a couple months away and now my resume just shows a naked desktop. Cursor works, but I can't interact with anything. Edit: Hypridle config |
|
Confirmed that suspend works with no issues. Seems to be specific to DPMS, but only after an indeterminate amount of time (seems to be >1 hour for the resume to freeze). Nothing in journalctl. |
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: