When a new user created the expectation of the OS user to see this new user popped up automatically on the boot menu so he can use it similarly to user session which comes by default. Otherwise how he can even use the new user?
The GRUB boot menu isn’t directly related which limited non-administrative account (not sysmaint account) will login.
By Kicksecue default, in user session, autologin is enabled for account user. This is probably causing confusion for multi-user use cases.
Additional confusion might be caused by calling a boot session “user session”, which does not refer to Linux login account user “user”.
By disabling autologin a lot confusion will be reduced. Because then the usual GUI or CLI login prompts can be used.
Related user documentation:
- User Management wiki page chapter Add a New User.
- (And maybe related chapters such as Allow New User to Login to Virtual Console.)
- Also Login Security wiki page chapter Configuring GUI Autologin.
Multi-user - in this context - multiple humans sharing the same operating system on the same computer and using different user accounts for login is probably pretty unpopular for end-users. I think I might have seen some data if this in the past.
Maybe still somewhat popular in some corporate contexts.
So this currently isn’t tested much and isn’t a priority for Kicksecure at the time of writing. At the time when terminology was coined and the word “user session” introduced, perhaps there would have been a better wording that doesn’t confuse it with “account user”.
That is why a feature to choose which Linux user account to login with at GRUB boot will very most likely not be implemented. It would also technically be challanging and make our already demanding (on usability and development effort) GRUB boot menu even more demanding.
related:
1 Like