Question about #qutebrowser and/or #SwayIdle #Swaylock When watching YT/browservideos. Is there a way to prevent the screenlock to activate?

Holy crap I figured it out. #swaylock is silently waiting for me to scan my fingerprint.

Now how do I disable fingerprint from swaylock? Or do I? Hm.

Ok #linux people. #sway. #fedora. #sericea. #swaylock.

Swaylock fails to unlock about 4-7 times, without producing any sort of error. It's not an authentication failure. It just silently doesn't unlock ... until it does. /etc/pam.d has a swaylock entry with the apparently correct contents.

This is perplexing. I don't know where the error is occurring so I'm having trouble, uh, troubleshooting.

Strange thing:

Still playing with #Sway and I use #swaylock to lock the screen.

Works ok for normal user: screen is locked and I can unlock with typing my usual normal user password and I find myself on sway desktop again. Good.

But if I use user ROOT this does not work at all. I always get „wrong password“.

Is there a special reason for this? (configuration?)

Useful command-line options for #swaylock

swaylock -c 00000000 -u

I had some #Wayland related issues on #openSUSE #Tumbleweed for a while, where thinks like #swaylock or setting wallpaper in #sway just wouldn't work. After some investigation it seemed that a Wayland related package update would automagically fix the problem.

After procrastinating for weeks, I decided to run `zypper dup`, and reboot.

I have my wallpaper back. I have my lockscreen back. Nice :)
I now just hope that the #opensuseway project also works as intended: https://en.opensuse.org/Portal:OpenSUSEway

Last time I tried, i had some issues with the login screen (greetd?)

#InterestingBug: Both #swaylock and #waylock fail to unlock sometimes, forcing me to reboot.