I have experienced similar issues with two different F29->F30 upgrades via dnf. Although what happened wasn't identical on both upgrades, the results were the same: After upgrade/reboot, the GDM login screen does not show the primary (previously existing) user name (UID 1000).
In the first upgrade, I was forced to create a new user after the upgrade on first boot, as if this was a new install, despite the existing userid. The previously existing user name does not show up on the GDM login screen. Instead, only the *newly* created username (UID 1001) shows.
In the second upgrade, the firstboot-create-a-new-user didn't occur, but the previously existing primary user name (also UID 1000) does not show on the GDM login screen. Instead, only secondary username (UID 1001) shows.
In both cases, the primary userid can be accessed by clicking the "not show" link on the GDM login screen and manually entering userid and password. Of course, this is a fairly simple workaround, but is nevertheless an inconvenience.
Where does the GDM login screen pull the info for the primary userid?
/etc/passwd and /etc/group don't show anything that looks like a flag for this.
The files in /var/lib/AccountsService/users/ appear to contain some sort of flag, but they are apparently created on login, rather than being permanent. On both systems the primary userid (UID 1000) is shown as:
SystemAccount=true
While the file for UID 1002 is:
SystemAccount=false
Modification time on these files is same as the userid's last login, and manually changing the SystemAccount flag has no effect; it's set back on next login.
On 6/17/19 3:42 PM, Ulf Volmer wrote:
On 17.06.19 17:00, Tim Evans wrote:
of flag, but they are apparently created on login, rather than being permanent. On both systems the primary userid (UID 1000) is shown as:
SystemAccount=true
Have you checked /etc/login.defs?
Thank you, Ulf. Don't see anything here that would affect this. Normal user UID range is default 1000+; system users, default 201+. Modification date on this file (on both systems involved) is Feb 2, long before the upgrade date last month.
On 6/17/19 11:00 AM, Tim Evans wrote:
I have experienced similar issues with two different F29->F30 upgrades via dnf. Although what happened wasn't identical on both upgrades, the results were the same: After upgrade/reboot, the GDM login screen does not show the primary (previously existing) user name (UID 1000).
In the first upgrade, I was forced to create a new user after the upgrade on first boot, as if this was a new install, despite the existing userid. The previously existing user name does not show up on the GDM login screen. Instead, only the *newly* created username (UID 1001) shows.
In the second upgrade, the firstboot-create-a-new-user didn't occur, but the previously existing primary user name (also UID 1000) does not show on the GDM login screen. Instead, only secondary username (UID 1001) shows.
In both cases, the primary userid can be accessed by clicking the "not show" link on the GDM login screen and manually entering userid and password. Of course, this is a fairly simple workaround, but is nevertheless an inconvenience.
Where does the GDM login screen pull the info for the primary userid?
/etc/passwd and /etc/group don't show anything that looks like a flag for this.
The files in /var/lib/AccountsService/users/ appear to contain some sort of flag, but they are apparently created on login, rather than being permanent. On both systems the primary userid (UID 1000) is shown as:
SystemAccount=true
While the file for UID 1002 is:
SystemAccount=false
Modification time on these files is same as the userid's last login, and manually changing the SystemAccount flag has no effect; it's set back on next login.
Bumping this, as no solutions have turned up.
-
Tim Evans -
Ulf Volmer