You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Installing hyprlock ...
Sync Explicit (1): hyprlock-0.3.0-1
Sync Explicit (1): hyprlock-0.3.0-1
resolving dependencies...
resolving dependencies...
looking for conflicting packages...
looking for conflicting packages...
Package (1) New Version Net Change Download Size
extra/hyprlock 0.3.0-1 0.37 MiB 0.15 MiB
Total Download Size: 0.15 MiB
Total Installed Size: 0.37 MiB
:: Proceed with installation? [Y/n]
Package (1) New Version Net Change Download Size
extra/hyprlock 0.3.0-1 0.37 MiB 0.15 MiB
Total Download Size: 0.15 MiB
Total Installed Size: 0.37 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
:: Retrieving packages...
hyprlock-0.3.0-1-x86_64 downloading...
error: failed retrieving file 'hyprlock-0.3.0-1-x86_64.pkg.tar.zst.sig' from arch.jsc.mx : The requested URL returned error: 520
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
hyprlock-0.3.0-1-x86_64 downloading...
error: failed retrieving file 'hyprlock-0.3.0-1-x86_64.pkg.tar.zst.sig' from arch.jsc.mx : The requested URL returned error: 520
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
Errors occurred, no packages were upgraded.
-> error installing repo packages
-> error installing repo packages
�[1A�[K�[31m[ERROR]�(B�[m hyprlock failed to install :( , please check the install.log. You may need to install manually! Sorry I have tried :(
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.]
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.
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
The text was updated successfully, but these errors were encountered: