Maximilian Seidler
Maximilian Seidler
Ufff ok @AndreasBackx give me more details. In the screenshots it seems like hyprlock crashed. does that always happens? Any particular steps to reproduce? Monitor configuration? I can see that...
@AndreasBackx A few things regarding your logs: 1. `pidof lock || lock` does not seem to work since `[LOG] onLockFinished called. Seems we got yeeten. Is another lockscreen running?` 2....
Hmm probably a hyprland problem then. maybe https://github.com/hyprwm/Hyprland/issues/8288 is the same?
That is odd. > The only thing amiss in the logs afterward are some extra graphical outputs occurring directly after that line, only when the bug happens That kinda stands...
Can someone get some logs from hyprland (+your exact hyprland version) when that happens?
Yeah i think you are right about that @rohrsben. Can you try to disable fadeout via `general:no_fade_out` and check if you can still reproduce it?
@wosym also with the `general:no_fade_out` option set to true?
So here is what I think happens: The session is actually still locked. The workspace shows, because Hyprland allows rendering the workspace when a lock screen client and surface is...
Thanks for reporting guys. I think this is an actual problem with fade out that i am going to fix soon!
As of https://github.com/hyprwm/hyprlock/pull/582, fade-out was re-implemented. Let me know if anyone is still having this issue!