Closed ashebanow closed 1 month ago
if hyprlock not installed, you can install it manually
sudo pacman -S hyprlock
or install the -git version
yay -S hyprlock-git
if you are using paru paru -S hyprlock-git
after installing,
try running hyprlock on tty to see if any errors
Oh, that was easy to fix, took care of it right away.
What I'm talking about here is that the script failed and left me in an insecure state at the end. A simple test to make sure your key apps are in fact installed would go a long way to addressing this.
On Sat, Jul 20, 2024 at 8:20 PM Ja.KooLit @.***> wrote:
if hyprlock not installed, you can install it manually
sudo pacman -S hyprlock
or install the -git version
yay -S hyprlock-git
if you are using paru paru -S hyprlock-git
after installing,
try running hyprlock on tty to see if any errors
— Reply to this email directly, view it on GitHub https://github.com/JaKooLit/Arch-Hyprland/issues/111#issuecomment-2241422568, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAACX75A2LWYFUBHZCUYQHDZNMSHVAVCNFSM6AAAAABK7FUT7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGQZDENJWHA . You are receiving this because you authored the thread.Message ID: @.***>
Bug Report
Description
Regardless of how I invoke screenlock (via hypridle, or via the waybar's logout menu, or via the SUPER-ALT-L), hyprlock never gets invoked. Digging into it, it turns out hyprlock wasn't installed correctly by the install script.
The error was there in the logs, but I failed to see it because it was buried. Having your lock screen not come up is a serious security issue, so the script should have either:
a) aborted immediately b) continued, but call out the errors very loudly at the time AND at the end of the script so people are sure to see it.
I dug in the logs, and the error looks to have been either an intermittent bug in the arch package or a networking issue.
Steps to Reproduce
[1] not sure exactly. How do you make the pacman install fail on purpose?
Expected Behavior
Because this leaves your machine completely unprotected from passers by, the install script should scream bloody murder if the install of a critical component like hyprlock fails. One solution would be to add a small test at the end of install.sh on hyprland, hyprlock, hypridle, and all the other critical pieces of the hypr ecosystem were present. I believe the My Linux For Work dotfiles have such a check that you could look at.
Actual Behavior
The script told me at the end that it was successful, so I didn't dig deep in the logs.
Screenshots
[If applicable, add screenshots to help explain your problem.]
Environment
Output of
inxi -CGIsSMnr
:Additional Information