Open Lord-Valen opened 1 year ago
I'm not sure what the best course of action is here. We could set sway as the default runner for the greeter, but it's a bit of a stretch to enable it by default in my opinion. I use it and it works fine, but I'm not sure whether users would want sway to be the default. Configuring it is also more involved.
If you wish to use sway to get around this problem, you can take a look at my configuration.
If we want to stick with just cage in the module, it's probably best to see if we can get -m last
working for now. Or wait for https://github.com/cage-kiosk/cage/issues/247 implementation, though cage's development velocity has slowed down significantly.
Alternatively, we could add a compositor option to the module, giving the option to switch between cage and a minimal sway configuration (and possibly others in the future).
As a workaround until then you might be interested in https://github.com/NixOS/nixpkgs/pull/261816.
Describe the bug
The default behaviour for cage is to "Extend the display across all connected outputs". The greeter therefore spans across all monitors. In multihead setups, this often results in the login prompt being split between two or more monitors. For obvious reasons, that isn't desirable.
Steps To Reproduce
Steps to reproduce the behavior:
programs.regreet.enable = true
services.greetd.enable = true
Expected behavior
The greeter appears on one monitor or appears separately on each monitor.
Additional context
cage -m last
should restrict cage to the last connected device but that results in an otherwise blank screen with the following error:Notify maintainers
@fufexan @Peter015
Metadata