08:02 <Guest45> Alguem aqui fala português?

09:09 <talismanick> Anyone care to share their greetd display manager setup?

09:10 <talismanick> Not sure why tuigreet is broken for me (won't let me type in text)

09:17 <kennylevinsen> talismanick: make sure you stopped agetty in that tty

09:18 <kennylevinsen> otherwise agetty and agreety fight over stdin

17:17 <talismanick> kennylevinsen: I disabled agetty-tty1. Good news is, it lets me log in via tuigreet now. Bad news, my envvars in .bash_profile aren't being loaded.

17:18 <talismanick> should config.toml not have user = "_greetd"?

17:19 <talismanick> err, user = "_greeter" is what it says

17:29 <kennylevinsen> talismanick: the user for the default session is what you or your package created. The default is "greeter", but the user needs to exist

17:30 <talismanick> yeah, it made _greeter

17:30 <talismanick> that's what I get from getent passwd | grep greet

17:31 <talismanick> https://0x0.st/oAxR.txt

17:32 <kennylevinsen> As for envvars, .bash_profile is only read if you make tuigreet start bash as a login shell (-l), not if you start something else. You want either .profile or a wrapper script around the thing you start.

17:33 <kennylevinsen> My preference is a wrapper script as it is the most flexible

17:33 <kennylevinsen> (e.g. make a river-run that exports things and ends in exec river - then you can set river specific things and such without interfering with other things)

17:34 <talismanick> Okay, let me try again with "tuigreet -l bash --cmd river"

17:35 <talismanick> Although, I don't see -l listed in the manpage

17:36 <ifreund> talismanick: -l is an argument to bash, not tuigreet

17:37 <talismanick> oh, oops

17:37 <talismanick> Also, I don't think Void installed the greetd manpage

18:55 <ifreund> added the bare minimum of configuration options and a man page for waylock by the way, anyone know of anything that should block a 0.4.0 release?

19:01 <ifreund> oh, I guess I could fix that zig-wayland forward compatibility issue

19:41 <novakane> that's a good idea

20:12 <leon-p> nope, I think there is nothing blocking 0.4.0. Depending on how many features you'd like to have, this may even be close to a 1.0 I think.

20:19 <ifreund> leon-p: yeah, I don't personally feel the need for any features beyond what I've currently implemented

20:20 <ifreund> I'd figure I'd give it one more release cycle for people to complain before tagging 1.0 though

20:27 <novakane> could wait till ext-session-lock-v1 is part of a stable release

20:27 <novakane> for 1.0 I mean, looks good for 0.4.0