I get this on two of my kits… one is a laptop with a 3080 Mobile, one is a PC with a 3090.
Does not happen on AMD.
When screen is locked and monitor goes off I get the screen with instructions on how to re-enable hyprlock and, therefore, unlocking.
Was at first like “ok, perhaps my problem”, but now that I verified that all my NVIDIA kits are affected I thought I issue an bug report.
I’m on 9070 XT and have been having crashes since I installed Hyprland. But I can’t consistently replicate them so I just assume they’re not easily fixable and i don’t bother. Created an alias (in .bashrc) for those 2 commands that they tell you to run after it crashes, then I just CTRL + ALT + F2, login, type hyprlock-toggle and it’s “fixed”.
I remember seeing some fix for nvidia, but nothing for amd in my quick “research”. It doesn’t happen often, but feels really random as sometimes something like a week will pass without crashes and later i will have a crash 3 days in a row 1 time.
Apparently it’s a null pointer access, see the GitHub issue, I have no idea of when it’s gonna get fixed
I used to get this, but since migrating to Hyprland DE dots, idling does nothing for me
I am also experiencing this issue unfortunately. Been having it on every distro I used so far since I started using Linux (Pop_OS, Endeavour OS, Tuxedo OS and now Arch Linux with Hyprland). I am also using the Hyprland Desktop Experience but that is not helping either unfortunately. This issue has been driving me crazy and I dont even know how i could start debug it.
Maybe…?