Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--remember* options is not working. /var/cache/tuigreet is empty #123

Closed
SDD701 opened this issue Jan 27, 2024 · 4 comments
Closed

--remember* options is not working. /var/cache/tuigreet is empty #123

SDD701 opened this issue Jan 27, 2024 · 4 comments

Comments

@SDD701
Copy link

SDD701 commented Jan 27, 2024

Hello. Looks like tuigreet does not create any files is /var/cache/tuigreet even if I set some --remember* options (so it doesn't remember anything).

OS: Gentoo

Greetd config:

# The VT to run the greeter on. Can be "next", "current" or a number
# designating the VT.
vt = 7

# The default session, also known as the greeter.
[default_session]

# `agreety` is the bundled agetty/login-lookalike. You can replace `$SHELL`
# with whatever you want started, such as `sway`.
command = "tuigreet --width 100 --time --remember --remember-session --asterisks --asterisks-char X --power-shutdown 'doas poweroff' --power-reboot 'doas reboot'"

# The user to run the command as. The privileges this user must have depends
# on the greeter. A graphical greeter may for example require the user to be
# in the `video` group.
user = "SDD"
@apognu
Copy link
Owner

apognu commented Feb 19, 2024

What are the permissions for /var/cache/tuigreet? It should be readable and writable by the user greetd runs as (in your case, as I can see, your own user?).

@SDD701
Copy link
Author

SDD701 commented Feb 21, 2024

Here you are. I guess maybe I should be in the greetd group?
20240221_23h32m39s_grim

@apognu
Copy link
Owner

apognu commented Feb 22, 2024

Usually, at least how it's recommended by greetd, it (and therefore its greeters) should run as the greetd user and not your own (security-wise, it does defeat the purpose of authentication if the thing that authenticates you already runs as you).

So it is expected that packagers set /var/cache/tuigreet as owned by greetd.

You could add your user in that group, but I would kindly recommend that you run greetd as its own user instead. Basically, change to user = "greetd" in the configuration.

@SDD701
Copy link
Author

SDD701 commented Feb 24, 2024

Usually, at least how it's recommended by greetd, it (and therefore its greeters) should run as the greetd user and not your own (security-wise, it does defeat the purpose of authentication if the thing that authenticates you already runs as you).

So it is expected that packagers set /var/cache/tuigreet as owned by greetd.

You could add your user in that group, but I would kindly recommend that you run greetd as its own user instead. Basically, change to user = "greetd" in the configuration.

Changing user to greetd fixed the issue. Thank you

@SDD701 SDD701 closed this as completed Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@apognu @SDD701 and others