| Summary: | .bash_profile not executed anymore | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Remi Collet <rcollet> |
| Component: | wayland | Assignee: | Adam Jackson <ajax> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | ajax, berend.de.schouwer, carwyn, drfudgeboy, fedora, feng.haibo, lars, luto, nyh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:48:16 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Remi Collet
2016-10-26 07:49:42 UTC
The same issue is ever reported for Fedora 23, see Bug 1301515. I installed fedora 23 from new, didn't meet this issue, dnf upgrade to Fedora 24 it is also fine. This time I hit it after dnf upgrade to Fedora beta. So it seems there is some bug in the dnf upgrade, it changed the user's gnome terminal setting. (In reply to FENG Haibo from comment #1) > The same issue is ever reported for Fedora 23, see Bug 1301515. > > I installed fedora 23 from new, didn't meet this issue, dnf upgrade to > Fedora 24 it is also fine. This time I hit it after dnf upgrade to Fedora > beta. So it seems there is some bug in the dnf upgrade, it changed the > user's gnome terminal setting. Should be "upgrade to Fedora 25 beta" I can confirm this issue, under Xorg .bash_profile is applied, under wayland it is not. This is on Fedora 25 updated as of Nov 9th, .profile isn't read in lieu of .bash_profile either under wayland. Workaround is to force gnome-terminal to "Run command as a login shell." I'm seeing this too. My workaround is to "source ~/.bash_profile" whenever I open a terminal, but it's not much fun. The problem with just forcing terminals to be login shells or sourcing .bash_profile is that graphical applications launched from gnome-shell don't inherit the environment. In my case atom editor and having $GOPATH in scope means that none of the Go add-ons work, this will likely be similar for other applications too. I tried to figure out what's going on and I got lost. /usr/share/xsessions/gnome.desktop and gnome-xorg.desktop appear to be identical except for their "Name" entries. That makes debugging *real* fun. Is anything happening with this? Fedora 25 has now been released, and this will be causing trouble. The upstream GNOME bug (linked in comment 9) has existed for more than two years (!!) and clearly they don't want to fix it. The GNOME developers, perhaps unsurprisingly, only care about GNOME and its GUI applications, none of which use environment variables, so they couldn't care less, apparently, that ~/.profile (et al.) suddenly stopped working. Fedora doesn't need to take this abuse from GNOME, and can fix it for Fedora users who use *both* GUI applications and "old school" shells and command line tools. I outlined an easy fix in the upstream bug: in the script /usr/bin/gnome-session, where we currently have the line: exec /usr/libexec/gnome-session-binary "$@" replace it by something like: exec -l $SHELL -c "exec /usr/libexec/gnome-session-binary $*" Or more safely (checking $SHELL for sanity), $SHELL -c "exec /usr/bin/true" && exec -l $SHELL -c exec "/usr/libexec/gnome-session-binary $*" || exec /usr/libexec/gnome-session-binary "$@" Fedora made this "GNOME on Wayland" the default on Fedora 25, so it can't wait another two years for GNOME to make this fix (if they ever do), and needs to patch this script on its own. See also bug #1149905 which appears to be the same bug, and 2 year old (!). This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |