hyprwm / hyprlock

Hyprland's GPU-accelerated screen locking utility
BSD 3-Clause "New" or "Revised" License
765 stars 59 forks source link

Hyprlock just sometimes unlocking #517

Closed LajnaLegenden closed 3 days ago

LajnaLegenden commented 4 days ago

Regression?

No

Hyprlock Info and Version

<0.4.1>

Hyprlock config ```sh background { path = "/home/lajna/nixConfig/bgs/*.jpeg" color = "rgb(27, 36, 41)" } input-field { size = 200, 50 outline_thickness = 3 dots_size = 0.33 dots_spacing = 0.15 outer_color = "rgb(109, 142, 152)" inner_color = "rgb(225, 234, 234)" font_color = "rgb(27, 36, 41)" fade_on_empty = true placeholder_text = "Password..." hide_input = false position = 0, -20 halign = center valign = center } label { text = Welcome back, $USER color = "rgb(225, 234, 234)" font_size = 25 font_family = Sans position = 0, 80 halign = center valign = center } ```

Compositor Info and Version

System/Version info ```sh Hyprland, built from branch at commit 6ae89940c761d4ed4317df0af29e8df41d472091 (). Date: 2024-10-09 Tag: , commits: 5323 built against aquamarine 0.4.2 flags: (if any) System Information: System name: Linux Node name: nixos-gaming Release: 6.6.54 Version: #1-NixOS SMP PREEMPT_DYNAMIC Fri Oct 4 14:30:05 UTC 2024 GPU information: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU106 [GeForce RTX 2070] [10de:1f02] (rev a1) (prog-if 00 [VGA controller]) 10:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev cb) (prog-if 00 [VGA controller]) NVRM version: NVIDIA UNIX x86_64 Kernel Module 550.120 Fri Sep 13 10:10:01 UTC 2024 os-release: ANSI_COLOR="1;34" BUG_REPORT_URL="https://github.com/NixOS/nixpkgs/issues" BUILD_ID="24.11.20241006.c31898a" DOCUMENTATION_URL="https://nixos.org/learn.html" HOME_URL="https://nixos.org/" ID=nixos IMAGE_ID="" IMAGE_VERSION="" LOGO="nix-snowflake" NAME=NixOS PRETTY_NAME="NixOS 24.11 (Vicuna)" SUPPORT_URL="https://nixos.org/community.html" VERSION="24.11 (Vicuna)" VERSION_CODENAME=vicuna VERSION_ID="24.11" plugins: csgo-vulkan-fix by Vaxry ver 1.2 ```

Description

Running hyprlock once from the terminal works as expected, unlocks fine. Running the same command once more, does not unlock the computer, instead just making the password field orange indefinitely. Unlocking with pkill -USR1 hyprlock does remove it, but leaves a black screen with the x cursor. Only way back into hyprland is to kill it and relaunch from another tty.

How to reproduce

hyprlock > log.txt hyprlock > log.txt # second time wont work for some reason

Crash reports, logs, images, videos

log.txt This is from the second run.

PaideiaDilemma commented 4 days ago

Ok so what might happen is that due to config errors you might not have a working representation of the input field. Try to normally enter your password and see if it unlocks, cause I can see that your config has some problems. Quotes around rgb() not allowed.

Config error in file /home/lajna/.config/hypr/hyprlock.conf at line 3: cannot parse ""rgb(27, 36, 41)"" as an int.
Config error in file /home/lajna/.config/hypr/hyprlock.conf at line 11: cannot parse ""rgb(109, 142, 152)"" as an int.
Config error in file /home/lajna/.config/hypr/hyprlock.conf at line 12: cannot parse ""rgb(225, 234, 234)"" as an int.
Config error in file /home/lajna/.config/hypr/hyprlock.conf at line 13: cannot parse ""rgb(27, 36, 41)"" as an int.
Config error in file /home/lajna/.config/hypr/hyprlock.conf at line 24: cannot parse ""rgb(225, 234, 234)"" as an int.

If that is not it, then hyprlock crashed the second time. In that case you would need to check coredumpctl and see if you can get me a stack trace.

Unlocking with pkill -USR1 hyprlock does remove it, but leaves a black screen with the x cursor. Only way back into hyprland is to kill it and relaunch from another tty.

Don't you have new session lock panic screen? With your hl version you should see lockdead.png

Also checking if -git/the flake fixes it is also a good idea.

LajnaLegenden commented 3 days ago

Fixing the colors did solve the issue. Saw those in the logs and assumed that it was not the cause.