You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... it seems to be that storage sessions are not saved before nody-greeter/web-greeter closes; they work until the program is closed by lightdm. I didn't find a right solution back then so this will have to wait unless someone else tries to fix it.
I think this should be tracked as an issue so attempts to fix it can be made.
My issue when writing a theme was that right before running lightdm.start_session(id) I try to cache the last logged in user this way:
try to retrieve cached user next time using the theme:
localStorage.getItem("LAST_USER")
Note: In some cases it seems like the storage works, but trying to setItem() right before starting the session, for me that's how it consistently fails.
Expected behavior
When rebooting, key "LAST_USER" is found on localStorage
The text was updated successfully, but these errors were encountered:
Environment
Bug description
Hello, I wanted to create an issue for this as it took me quite some time to find a Reddit thread that describes it:
https://www.reddit.com/r/linuxquestions/comments/12uhsyr/comment/jh8yi8o/?context=3
I think this should be tracked as an issue so attempts to fix it can be made.
My issue when writing a theme was that right before running
lightdm.start_session(id)
I try to cache the last logged in user this way:However, it doesn't appear to be cached on the next reboot. The reddit thread describes this same issue as far as I understand.
Steps to reproduce
In a web-greeter theme:
localStorage.setItem("LAST_USER", lightdm.authentication_user)
localStorage.getItem("LAST_USER")
Note: In some cases it seems like the storage works, but trying to
setItem()
right before starting the session, for me that's how it consistently fails.Expected behavior
When rebooting, key
"LAST_USER"
is found on localStorageThe text was updated successfully, but these errors were encountered: