On my tablet, kde and kdm have no touch keyboard working. So i use gdm and gnome .
Until last week, the gdm login sreen (greeter?) displayed a list of users and i just had to touch the user and then gdm would prompt me to type my password with a keyboard rising from the bottom of the screen.
And suddenly, maybe due to some update, the list of users has disappeared, and i have to type the name of the user i want to login each time i boot my tablet. That is a regression. How can i revert to the previous good situation ?
NB :I googled for hours to find a solution and it tells me to tweak/edit some /etc files ut it simply doesn’t work.
You could try the packages mentioned in the bug report, and/or add a comment there. (same username/password as here)
Other than that, reverting the complete GNOME update should help of course (I’m not sure which packages are involved in this problem in particular, probably gdm and accountservice should suffice).
You could do that by choosing to show “All patches” in YaST->Online Update, selecting the GNOME update, and switching all packages back to the previous versions. Cannot think of an easier way at the moment, sorry.
Ok, i had to roll back to previous version for accountservice package and i had to edit /var/lib/AccountsService/users/$USER to say: SystemAccount=false, and i get back my users displayed on gdm login screen.
Thank you for your help and i hope a new version will come soon to solve the problem…
Please, tell your experiences in the bug report.
Things like this don’t get fixed magically just by waiting…
Not everybody experiences this, as the the default user id is 1000 for a while now.
For example, I myself still am user 500, but I don’t really care (and haven’t noticed) as I don’t use neither gdm nor GNOME.
And kdm still shows my user fine…
On 2014-09-16 09:26, Christophe deR wrote:
>
> Yes you’re right : we, old linux users ( i use linux since year 2000 .
> 14 years ! ) have user numbers like 500 .
Not all. Many years ago I did a find and change all files with uid 500
something to 1000 something on all my disks and machines - except
backups on CD/DVD, obviously
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Yes, lightdm uses the same accountservice as gdm.
Please add a comment to the bug report, so they see that more users are affected.
And maybe try the packages mentioned there, to see whether they fix the problem.
If nobody tests them, they won’t be released as update either.
and yes, my user id is 503, but this system was only installed in May.
The default user id is definitely 1000 since years.
Was this a fresh installation?
If this is the first user, it should have 500 anyway, not 503.
There is a configuration option somewhere in YaST (it’s stored in /etc/login.defs) to change the default user id for freshly created users. Maybe you changed that?
There is a configuration file /etc/lightdm/users.conf, the default looks like this:
## User accounts configuration
#
# NOTE: If you have AccountsService installed on your system, then LightDM will
# use this instead and these settings will be ignored
#
# minimum-uid = Minimum UID required to be shown in greeter
# hidden-users = Users that are not shown to the user
# hidden-shells = Shells that indicate a user cannot login
#
[UserAccounts]
minimum-uid=1000
hidden-users=nobody
hidden-shells=/bin/false /sbin/nologin
Maybe you had a custom file that was overwritten by the update? But the best would be to change your user id’s, rather than changing that file, as that would be more future proof.
Yes, and if you read the comment at the top of this file, you can see that changing the values there will have no effect:
## User accounts configuration
#
# NOTE: If you have AccountsService installed on your system, then LightDM will
# use this instead and these settings will be ignored
#
# minimum-uid = Minimum UID required to be shown in greeter
# hidden-users = Users that are not shown to the user
# hidden-shells = Shells that indicate a user cannot login
#
[UserAccounts]
minimum-uid=1000
hidden-users=nobody
hidden-shells=/bin/false /sbin/nologin
Maybe you had a custom file that was overwritten by the update?
Probably not, as those values are ignored anyway.
The “bug” is that accountservice ignores user ids below 1000 since the latest GNOME update.
AFAIK there has not been an update yet, but testing packages are available.
And user accounts already changed to “SystemAccount=true” will probably never be “fixed” to be shown again by an update automatically, because it might have been set by the administrator on purpose.