This space intentionally left blank.
I'm not going to add a tray icon, but having a way to temporarily disable/enable might make sense. Someone could then make a tray icon that calls that.
post your greetd configuration file.
On Thu, 2022-06-16 at 19:28 +0000, ~sunderland93 wrote:
Greetd is fails to start on Ubuntu 22.04 due to pam_unix error:
`Jun 16 22:41:28 acer systemd: Started Greeter daemon. Jun 16 22:41:28 acer greetd: pam_unix(greetd:account): could not identify user (from getpwnam(ubuntu))
Did you create the user for the greeter configured in your configuration file ("greeter" by default)?
greetd does not know about displays at all (it only cares about VTs), so yes it should be possible to use in a headless setup as long as the greeter can do its job.
In your case, the greeter is failing to start or exits prematurely, suggesting that it does not like the setup. You would need to share your configuration files/scripts used, and to look at the debug logs from the thing you are starting.
Note that greetd sessions do not inherit the environment from the greetd main process at all as it is creating new user sessions. If you want to pass environment variables (like WLR_BACKENDS=headless) to the greeter/session, you will need to do so using /etc/profile, $HOME/.profile or wrapper scripts around what you are starting.
It doesn't make much sense to run seatd inside a container. If you really want sway to run inside a container, run seatd outside and expose the socket, keeping the container unprivileged. You'd have to set permissions on the socket to match the container of course.
The seatd executable is intended to be run as a daemon as root. You specify to it what group you would like to give access to its services, and your user should be in that group.
Your user is then not required to be in input or video groups to open these devices, avoiding the risk of having random processes running as your user eavesdrop on your input devices as well as allowing access to be revoked when switching VT.
Initial support for NetBSD merged, but we have no consumers yet.
You are probably still running (a)getty on that TTY, leading to agetty and agreety fighting to be the one to read a keyboard press. Disable (a)getty and try again.