Basti

Why using betterlockscreen then and not just i3lock-color directly?

Might be related to spaces in paths, as I don't use betterlockscreen anymore I'm open to pull-requests but won't fix it myself ✌🏻

Hey, can please everyone having issues try the pull-request #395 and let me know if it fixes your issues so I can make a release?

Please recheck with the newest release v4.2.0 ✌🏻

Thanks for your contribution! Seems reasonable, but looking at the flake.nix dev-environment I previously used there are more missing: https://github.com/betterlockscreen/betterlockscreen/blob/next/flake.nix#L19 Would you be open to extend the PR with them?

As stated here: https://github.com/betterlockscreen/betterlockscreen/discussions/366 I'm no longer using betterlockscreen and will not merge new features/improvements other than keep it working as is if something is breaking due to updates etc....

Does this also happen if you use i3lock-color alone with just a color? If yes I suggest to create an upstream issue there - otherwise I would need more output/logs/service-config...

> With home-manager https://github.com/nix-community/home-manager/commit/f99eace7c167b8a6a0871849493b1c613d0f1b80 and nixpkgs faf912b086576fd1a15fca610166c98d47bc667e and this configuration: Not sure what's the issue is but it appears to me that you are building from random hashes from February...

Hey, I just wanted to report another use-case which is affected by this when upgrading from podman v4 to v5 - using e.g. xDebug in the container with your IDE...

> if you use named (user-defined) networks (default in compose) This, are there plans to change this or restore the functionality of `host.containers.internal` somehow else?