Describe the bug
ReGreet starts even when [initial_session] is defined in /etc/greetd/config.toml. The expected behavior is that greetd skips the greeter entirely and logs directly into the session. But ReGreet still appears.
To Reproduce
Configure greetd with both [initial_session] and [default_session]
Use ReGreet as the default greeter
Boot system
[terminal]
vt = 1
[initial_session]
command = "Hyprland"
user = "vbm"
[default_session]
command = "regreet"
user = "greeter"
On reboot I simply end up in Regreet.
Expected behavior
greetd should skip the greeter and launch Hyprland as user vbm, as defined in initial_session.
Actual behavior
ReGreet still runs and prompts for login, even though greetd config is valid and initial_session should bypass the greeter entirely.
System information:
Distribution: Arch Linux
greetd version: 0.10.3
ReGreet version: 0.2.0
Describe the bug
ReGreet starts even when
[initial_session]is defined in/etc/greetd/config.toml. The expected behavior is that greetd skips the greeter entirely and logs directly into the session. But ReGreet still appears.To Reproduce
Configure greetd with both
[initial_session]and[default_session]Use ReGreet as the default greeter
Boot system
On reboot I simply end up in Regreet.
Expected behavior
greetd should skip the greeter and launch Hyprland as user
vbm, as defined ininitial_session.Actual behavior
ReGreet still runs and prompts for login, even though greetd config is valid and
initial_sessionshould bypass the greeter entirely.System information:
Distribution: Arch Linux
greetd version: 0.10.3
ReGreet version: 0.2.0