Quote:
My research suggests that the problem may stem from Alt+F2 not using a login shell,
so therefore is not reading ~/.bashrc. Is this correct
|
I don't know, but it sounds a perfectly reasonable explanation.
You could check this out by trying a simple command like this:
Code:
env > /home/yourusername/ALTF2-env
Execute it from your Alt+F2 thing.
Then see what the file
/home/yourusername/ALTF2-env looks like
and compare it to the output of
env in a normal terminal window (or whatever it is that you
can start
audacity from).
Please note that as a general security measure, I do not like to have anything under
/home/ to be in my
PATH
If you had done the
make install step as root, audacity would probably now be in
/usr/bin/ and you probably wouldn't have this problem. But it's in the nature of linux to encounter problems, and then maybe learn something by solving them.
Typing commands can become tedious. Why don't you just create an icon to launch
audacity with a click?