The --remember-user-session flag stopped remembering the session in v0.9.1

[alerque]

Possibly as an unexpected side effect of #141, the current version has stopped remembering the last session used. My systems are now booting up into the first session in the alphabetical list, not the one I last used.

[default_session]
command = "tuigreet --issue --time --user-menu --remember --remember-user-session --asterisks"

Given that it does remember the last user, not also remembering the last session is ridiculous. I would expect not only the user but also the last session used to be already selected on boot and just waiting for my password.

[apognu]

I cannot seem to be able to reproduce this. Can you list the files in the tuigreet cache directory (/var/cache/tuigreet), and more specifically the content of lastsession-path-$USER?

[andyrtr]

 ls /var/cache/tuigreet/
.rw-r--r--  4 greeter greeter 30 Dez  2023  lastsession
.rw-r--r-- 40 greeter greeter  3 Jun 16:05  lastsession-path-andyrtr
.rw-r--r--  7 greeter greeter  3 Jun 16:05  lastuser
.rw-r--r-- 13 greeter greeter  3 Jun 16:05  lastuser-name

[andyrtr]

The lastsession file has the proper "sway" entry for me saved but starts here "Hyprland" - the 1st entry now.

[alerque]

Similar to @andyrtr:

$ ls -al /var/cache/tuigreet/
.rw-r--r-- 44 greeter  4 Jun 11:36 lastsession-path-caleb
.rw-r--r--  5 greeter  4 Jun 11:36 lastuser
.rw-r--r-- 15 greeter  4 Jun 11:36 lastuser-name
$ cat /var/cache/tuigreet/lastsession-path-caleb
/usr/share/wayland-sessions/hyprland.desktop

This is correct for me as Hyprland is what I log into most, but Gnome is installed and shows up first in the list and that is what session is selected when I boot up.

[LargePrime]

Not sure if this belongs here, but...

i set command = tuigreet --remember-user-session

upon boot system crashes with a screen that says "--remember-user-session must be used with --remember"

1. can one have tuigreet remember last used session, without supplying and filling user?

2. perhaps mis configured options should allow login with error as warning?

[teto]

doesnt seem to be the case here but a similar event can appear due to https://github.com/apognu/tuigreet/issues/162