Compositor does not support the input inhibitor protocol, refusing to run insecurely

[rbroggi]

swaylock-effects is not compatible with the latest wlroots. Here you can find more details. Any chance we can upgrade swaylock-effects to use the latest features of vanilla swaylock and use ext-session-lock-v1 protocol instead of the deprecated wlr-input-inhibitor-unstable-v1?

[mxaddict]

I'm getting this same error, but regular swaylock works just fine.

[main.c:1824] Compositor does not support the input inhibitor protocol, refusing to run insecurely

I think upstream swaylock has updated to use the new protocol.

[mxaddict]

swaylock-effects is not compatible with the latest wlroots. Here you can find more details. Any chance we can upgrade swaylock-effects to use the latest features of vanilla swaylock and use ext-session-lock-v1 protocol instead of the deprecated wlr-input-inhibitor-unstable-v1?

Hmm, after more testing, it seems that the aur package swaylock-effects is out of date

I installed swaylock-effects-git and this version works.

[AlifiChiganjati]

swaylock-effects is not compatible with the latest wlroots. Here you can find more details. Any chance we can upgrade swaylock-effects to use the latest features of vanilla swaylock and use ext-session-lock-v1 protocol instead of the deprecated wlr-input-inhibitor-unstable-v1?

Hmm, after more testing, it seems that the aur package swaylock-effects is out of date

I installed swaylock-effects-git and this version works.

cool thanks mate

[AyushmaanAggarwal]

92 has more information about this issue, and how this project is no longer maintained

[ImDooMLorD]

somehow, reinstalling swaylock-effects clean using yay makes it work again for me yay -S swaylock-effects-git

[AyushmaanAggarwal]

The reason swaylock-effects-git works is because the upstream of swaylock-effects-git is NOT this package but the more up to date but not actively maintained repo here https://github.com/jirutka/swaylock-effects. More details are in #92

[githubkuyaya]

I get that error too, but moving to swaylock-effects-git is not really optimal too, as that fork somehow is a lot clunkier. I bounded a hotkey SUPER + l to execute swaylock with fade-in=0.1 in the config. Unfortunately, the animation takes about ~1 second to even start and the indicator appears instantly, and the animation being out of sync with the indicator looks ugly. This repo seems to work more smoothly (as long as it was still working) :(

[TonyTwoStep]

Can confirm on OpenSUSE without a dedicated build in the repos, building from source using the more up-to-date https://github.com/jirutka/swaylock-effects, which @AyushmaanAggarwal mentioned is what the swaylock-effects-git AUR package is based on, fixes this issue for me.

[githubkuyaya]

I get that error too, but moving to swaylock-effects-git is not really optimal too, as that fork somehow is a lot clunkier. I bounded a hotkey SUPER + l to execute swaylock with fade-in=0.1 in the config. Unfortunately, the animation takes about ~1 second to even start and the indicator appears instantly, and the animation being out of sync with the indicator looks ugly. This repo seems to work more smoothly (as long as it was still working) :(

Update: Although the fade-in is still buggy for me in every repo I've tried, hyprlock was released 2 months ago with a lot more customization options. Additionally, the fade-in seems to work smooth there, just wanted to put this here for everyone else that didn't know about it :)

[mortie]

So I'm using swaylock-effects from this repo (which indeed doesn't support the input inhibitor protocol), and I'm not seeing these issues... I'm running Fedora 40 with Sway, using swaylock-effects, and it still Just Works™. Ideally this repo should obviously be updated to support input-inhibitor, but I don't quite understand why it works for me but not others 🤔

[mxaddict]

So I'm using swaylock-effects from this repo (which indeed doesn't support the input inhibitor protocol), and I'm not seeing these issues... I'm running Fedora 40 with Sway, using swaylock-effects, and it still Just Works™. Ideally this repo should obviously be updated to support input-inhibitor, but I don't quite understand why it works for me but not others 🤔

I switched to hyprlock a few days ago, been loving it, maybe give it a shot.