*** This bug is a duplicate of bug 17962 ***
https://bugs.launchpad.net/bugs/17962
Actually, I'm going to file these under the original .bash_profile bit,
.. Rather than dupe them.. Check out bug 64064 for more dialog on ~/bin
** This bug has been marked a duplicate of bug 17962
newly open
*** This bug is a duplicate of bug 17962 ***
https://bugs.launchpad.net/bugs/17962
This bug has two totally unrelated issues, .bash_profile not being run
with X, and ~/bin not easily added to your system. I have two options,
to close the report entirely or mark it as a dupe so I'm going with t
The problem is not about user assumptions, it's that a piece of
functionality, admittedly a small one, disappeared for users upgrading.
Ubuntu shipped with a .bash_profile that appended ~/bin to PATH if it
existed. When Ubuntu switched to Dash that functionality shouldn't have
just disappeared, it
I don't think that you can claim that it's "an assumption that Ubuntu
used to make". It's a practice Ubuntu used to follow, but that doesn't
mean it's safe for users to assume it's the practice that will always be
followed.
I'm not sure what you want to be done, though. As long as dash is being
us
To clarify: I didn't mean that .bash_profile was run on login to X, but
was definitely run at some point, so ~/bin was available when you opened
a shell through gnome-terminal. The move to dash meant it was no longer
run meaning that functionality broke for those using a ~/bin. Really the
functiona
But there is stuff in the .bash_profile shipped by older versions of
Ubuntu that never gets run. So certain functionality stopped working on
upgrade, which seems like a regression to me.
For example, my desktop which now runs feisty, but was upgraded from
older versions of Ubuntu has the following
Sorry, but this does not appear to be a bug. No distribution sources
~/.bash_profile when it starts X, though many source ~/.bashrc. Assuming
that all systems will source ~/.bashrc for X is not a generally portable
assumption, and depends on the default shell for the system. .xsession,
on the other
For gdm, at the top of /etc/X11/gdm/Xsession, there is
PROGNAME=Xsession, so another solution is to add this condition before
including ~/.bashrc in ~/.bash_profile :
# include .bashrc if it exists
if [ "$PROGNAME" != "Xsession" -a -f ~/.bashrc ]; then
. ~/.bashrc
fi
and create a link ~/.prof
I too was hit this problem (trying to get ~/bin in $PATH to work in
gnome-terminal) and I came up with following solution. Append this to
.bashrc or /etc/bash.bashrc, or perhaps even to /etc/profile:
# add $HOME/bin to path unless it is already there
case $PATH in
*$HOME/bin*)
For gdm the shell environment variables is sourced in
/etc/X11/gdm/Xsession. From this script .profile is sourced in Ubuntu.
Other distros often sources other shell spesific profile files like
.bash_profile. I proposed a solution to this in bug #69700.
--
.bash_profile is not sources when X sessi
Oh, I had no idea that Ubuntu didn't use bash as the default shell. That
explains a lot. How about ~/.profile: is it sourced? (I don't currently
have access to an Ubuntu system, so I cannot test myself)
--
.bash_profile is not sources when X session starts
https://launchpad.net/bugs/66004
--
ub
(Sorry, to clarify, .bashrc will be sourced both by shells started
within X and shells started from the console. In my experience it's
usually what you want.)
--
.bash_profile is not sources when X session starts
https://launchpad.net/bugs/66004
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Since the default /bin/sh is dash nowadays, note that our Xsession
cannot safely source .bash_profile. Since .bash_profile sources .bashrc,
you can put everything there instead, and that will be sourced by
terminals started within X.
.pam_environment is also useful for simple unconditional setting
Having just wasted half an hour of my life trying to work out the
reasons that ~/.bash_profile is not sourced .. I can't find one.
All I wanted was my bin directory working:
# set PATH so it includes user's private bin if it exists
if [ -d ~/bin ] ; then
PATH=~/bin:"${PATH}"
fi
Which seems s
I agree with Mr. Tolf that having to edit .xsession is completely
counterintuitive and error prone, forcing one to keep track of two files
(.bash_profile, .xsession) for something as simple as the value of PATH.
Even Microsoft Windows allows you to set environment variables that will
be used in th
While that is useful to know, all other Linux distros and Unix systems
that I have used do source ~/.bash_profile (or ~/.profile) upon X login.
If Ubuntu really wants to do this with ~/.xsession, I believe it should
at the very least ship with a default /etc/skel/.xsession that sources
~/.bash_prof
.bash_profile should be sourced only by terminal bash sessions. X
session is different. To make personalized X sessions use file
~/.xsession and put personal variables there. Last command in this file
should be X session manager, X window manager or some X client you want
to run. Usually maybe just
17 matches
Mail list logo
