[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
That was absolute bull. Ubuntu obviously ships with /etc/profile, which is a version of bash_profile, so #8 was a specious argument. And placing profiley stuff into bashrc slows down the shell (as if it's not slow enough already!) Some .xsessionrc file (or whatever is read by the *dm's) must make sure to read /etc/profile. If that is not done at the system level it must be recommended to users as the preferred workaround for this utter nonsense. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17962 Title: newly opened gnome-terminal windows don't have .bash_profile sourced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/17962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
No argument of any sort was made in #8, specious or otherwise; only an observation. And placing profiley stuff into bashrc slows down the shell (as if it's not slow enough already!) Adding things to PATH that you want access to in all your interactive shells, belongs in the file sourced by interactive shells, not merely login ones. There's nothing profiley about that. And it would be entirely inappropriate for GDM or ~/.xsession or the like to source a bash-specific profile script file (as ~/.bash_profile surely is) without the user configuring it to do so, most particularly when bash isn't the usual system shell under which those things would be running (and it's certainly not interactive). Interactive shell stuff goes in the ~/.foorc (~/.bashrc, ~/.kshrc, what have you); MOTD and other once-only, truly profilish-type setup stuff goes in the profile source files, and none of those should be sourced by non-interactive X shell scripts (such as ~/.Xsession) running under /bin/sh (= dash). There's a reason why the default ~/.profile sources ~/.bashrc, and does nothing else by default (though, if it's going to source ~/.bashrc, it ought to have been a ~/.bash_profile, and not ~/.profile, but that's an entirely separate issue). It has been the case for _decades_ that terminal emulators by default spawn interactive, non-login shells. Changing this to satisfy a few people who failed to configure their interactive shells correctly, would surely cause more harm to those who expect things to work the way they always have, than benefit to those who are confused about how to properly set up their source files. Bottom line, you want your profile sourced, configure your emulator to spawn login shells. Not hard: /bin/bash -l versus /bin/bash. And if you want certain items to be in your PATH across all interactive shells, put it in the correct file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17962 Title: newly opened gnome-terminal windows don't have .bash_profile sourced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/17962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
So this has been reported a number of times in different guises .. for example: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/72714 which links us back to: http://bugzilla.gnome.org/show_bug.cgi?id=150521 Which shows that the gnome folk are not interested in fixing this. So as a distribution, Ubuntu includes a .bash_profile which will not be sourced if you're a local user. Seems odd. And all the possible points of fixing it are marking bugs invalid: - gdm bug? nope, gnome don't care. - terminal bug? nope, see gdm bug - ... As an end user I just want my ~/bin/ to work, I don't much care how we get there. ** Bug watch added: GNOME Bug Tracker #150521 http://bugzilla.gnome.org/show_bug.cgi?id=150521 -- newly opened gnome-terminal windows don't have .bash_profile sourced https://bugs.launchpad.net/bugs/17962 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
(I'll just add here that FWIW Ubuntu does not in fact ship with .bash_profile at all, just the .bashrc) -- newly opened gnome-terminal windows don't have .bash_profile sourced https://bugs.launchpad.net/bugs/17962 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
As an end user, then, you should add ~/bin/ to your path from within .bashrc, rather than .bash_profile. It has long been historical practice for xterms and the like not to spawn login shells by default. For this reason, people have for many years followed the practice of placing anything important in the rc file, and sourcing the rc file from within their profile. The only other things that should go in a profile are things specific to login shells... things that ought to be followed for _every_ interactive shell, belong in the rc file (that's the rc file's purpose). These bugs are nothing more than a matter of confusion on the user's part for what purposes are served by the *rc and *profile files that a typical shell program supports. -- newly opened gnome-terminal windows don't have .bash_profile sourced https://bugs.launchpad.net/bugs/17962 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
This is not a bug; newly started terminal emulators should not start login shells, since they are already part of a login session. They are correct in running sh/bash as a non-login shell, which is the same behavior as would be observed when, for example, starting an escape shell from the ftp/telnet program or similar. Rather, ~/.bash_profile (or probably, rather, ~/.profile) should be sourced when logging in via GDM, so that all environmental changes it causes also affects all X programs (including, but not limited to, xterm and gnome-terminal themselves). -- newly opened gnome-terminal windows don't have .bash_profile sourced https://bugs.launchpad.net/bugs/17962 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
