Description of problem: With fresh OS installation, instead of creating local users I want to use domain user (from FreeIPA in my example). It all goes well and loads new users desktop, but after restart fedora is starting with 'gnome-initial-setup'. Same thing would happen if I would create local user then login as domain user and remove local user - i will be rolled back to 'gnome-initial-setup' Version-Release number of selected component (if applicable): 29 How reproducible: Always Steps to Reproduce: 1.install fresh system 2.instead of creating local users, log into domain user 3. Actual results: 'gnome-initial-setup'all over again Expected results: login with user list from domain Additional info: Tried to get answer on 'ask fedora' (https://ask.fedoraproject.org/en/question/133793/fresh-fedora-with-domain-only-users/)but no luck, assuming that it might be a bug.
Hi, on my system I have a file ~/.config/gnome-initial-setup-done with the content 'yes'. Is this file created for your FreeIPA user? If not, is 'gnome-initial-setup' still running if you create it manually? What are the ownership and the permissions of the .config directory in the home directory of the FreeIPA user? bye, Sumit
$ cat ~/.config/gnome-initial-setup-done yes Ownership of .config file is to the ipa user. So far I have tested 2 fresh installs and got same result so guess it should be easy to test it out on your side as well
In order to not to fall into infinite 'gnome-initial-setup', i have to create local user. Once that local user is removed, after restart i am being greet with fresh 'gnome-initial-setup' again
even if I create local user and log into domain user, every sudo authorization requests comes from local user. So if local localuserA is created and domain ipauserB. If I am logged as ipauserB and for eg. turn on gparted, I am being asked to provide localuserA password. Even if ipauserB is added to wheel group.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.