Revert change to always source from /etc/bashrc
/etc/bashrc is now again sourced from user's ~/.bashrc
sudo dnf upgrade --advisory=FEDORA-2017-5bf6183242
This update has been submitted for testing by svashisht.
This update has been pushed to testing.
works for me
Works great! LGTM! =)
This update has been submitted for batched by bodhi.
This update breaks command line (host + user name) of mate- or gnome-terminal in f27 qemu-kvm VM.
Command line looks like this.
Of course i restarted the whole VM.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
@raveit65 You should manually modify user's ~/.bashrc to source /etc/bashrc. Please see http://pkgs.fedoraproject.org/cgit/rpms/bash.git/tree/dot-bashrc
Thx, this fixes the problem, but doesn't break this update with a point zero update users installation from released isos?
This update has been submitted for stable by svashisht.
I have proposed this bug as a blocker for F27 release.
i got the same problem as raveit65 , so just downgraded to previous
@raveit65 @greg18 yes, unfortunately, if you installed Fedora 27 and created users with the previous bash package then update to this one, all those user accounts won't source /etc/bashrc for shells any more. There is just no good way around this, though - we rather painted ourselves into a corner by making the change the way we did, and prematurely. So we had no choice but to just do that, say 'sorry' to affected folks, and document the problem :/ I'll write it up on the F27 Common Bugs page soon.
The only alternatives were to leave the change in place permanently (even though we know now that it causes various problems we didn't foresee), or revert the change after F27 came out, which would cause the same problem for far more people - at least this way it only affects folks who installed a pre-release, it'd be much worse to ship F27 with the change and then revert it soon after in an update, causing thousands of people who install early to have the same problem when they update.
Sorry again :/
BTW, the way to deal with it is just to add this block to the top of the ~/.bashrc of affected accounts:
# Source global definitions
if [ -f /etc/bashrc ]; then
that's the block that always used to be included in ~/.bashrc , and with the reversion will now be included again for all accounts created with this build of bash or later, but which was left out of user accounts created with the bash that made the change. If you just add it back for each affected user account, things should go back to normal.
This update has been pushed to stable.
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2019 Red Hat, Inc. and
bodhi is Free Software.
if you have any problems. Read the documentation.