In the Fedora-Rawhide-20170830.n.1 compose, when we run an install where we create a regular user then boot and log in as that user, the bash prompt shows up as the default 'bash-4.4 $' prompt, meaning that sourcing of the Fedora bash config didn't work correctly. There were two obviously related changes which landed in that compose, one to setup: https://pagure.io/setup/c/be2c86a2fc92d18cfa326225a9d5c59a3b03a8b2?branch=master and one to bash: http://pkgs.fedoraproject.org/rpms/bash/c/a37e6bcc6c04bb78af3ac704f4ecce323406809d?branch=master It seems likely that one or both of these is the source of the problem. To reproduce, grab https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20170830.n.1/compose/Server/x86_64/iso/Fedora-Server-dvd-x86_64-Rawhide-20170830.n.1.iso , run an install (creating a user account along the way), then boot the system and try to log in as the user you created. You should see the bug there. It may well show up any time a regular user logs in with that bash package, of course, I just know that specific case definitely triggers the bug.
This regression was introduced by fix for bug 1193590. /etc/bashrc is not sourced by login shells.
This is a design decision taken by upstream to not source bashrc files for login shells. We need to find a workaround for it. Before bash-4.4.12-11 /etc/bashrc was sourced by ~/.bashrc and ~/.bashrc was sourced in ~/.bash_profile. So sourcing for /etc/bashrc worked that way.
We can workaround this bug by sourcing /etc/bashrc in /etc/profile. However since /etc/profile is used by different shells, we should put a check for sourcing /etc/bashrc for bash only.
This was already done in Rawhide, will do an update for F27 once the fix is confirmed.
Thanks, just waiting on a successful Rawhide compose to see.
setup-2.10.10-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-9e0caa3222
setup-2.10.10-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9e0caa3222
Welp, with recent Rawhide this indeed looks OK: https://openqa.fedoraproject.org/tests/138632#step/_console_wait_login/6 and the bug never actually hit F27 due to the freeze, so I don't think we need to associate this bug with the F27 update. We can just close it. I'll edit the association out of the update.