Registered Member
|
Here is the output:
In this session I couldn't perform mdrun. However after restarting, I can use it even thought I don't type ps aux. |
Administrator
|
Okay, that is the behaviour I was expecting. In a broken instance, if you source the script which sets up the variables manually, does it then work?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I don't fully understand what you said. Did you mean to create some scripts to test? If yes, then my scripts work.
Some more information: after booting, sometimes it works, sometimes doesn't. In the not working case, if you reopen Dolphin, it will work again.
Last edited by ooker on Sat May 31, 2014 11:27 pm, edited 1 time in total.
|
Administrator
|
Oops - i'll rephrase. When you get a instance of Konsole which has failed to load your script, does sourcing the script set everything up correctly?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Yes. In the breaking case, use source /usr/local/gromacs/bin/GMXRC will make it work again.
|
Administrator
|
Please post the contents of your ~/.bashrc file.
If the file is being sourced from ~/.bashrc, and you've placed the echo statement in ~/.bashrc, I can't see why this isn't working.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Here you go:
|
Registered Member
|
I'm not sure if helpful, but I noticed today that dolphin was showing a strange prompt today. I can't exactly remember, but something like
Anyway, it was totally different to what I normally use. I tried sourcing my .bashrc, and the prompt was fixed. What was odd was that it was fixed permanently, even if I quit and restart dolphin, or even restart my computer. I tried modifying .bashrc again, and these changes also propagated to the dolphin terminal (suggesting that it wasn't just cached). |
Registered Member
|
@SparHawk: Have you changed anything recently on bashrc? Maybe you should also post your bashrc so that Cooksley can help you.
|
Registered Member
|
I'm always fiddling with my bashrc. But I haven't done anything major. Anyway, as I said, Dolphin appears to be permanently fixed for me after a single sourcing of the bashrc, so I don't have any problems any more. I was just chiming in for another data point. |
Registered Member
|
Oh, this is random, but I just did a `sudo -i`, and I noticed that my default prompt is `[user@hostname path]#`. So perhaps I was logged in as root in Dolphin. That is very very strange, as I would never run Dolphin as root, nor would I Dolphin's terminals as root (I generally use terminator for anythin semi-involved).
It's a long shot, but I wonder if you are logged in as root, somehow, or at least sourcing root's profile? To check the former, you can try typing in `whoami`, although I'm not sure how to check the latter. ==EDIT== Actually, I just realised that this is the default PS1 for new accounts. So it's probably nothing to do with root. Still, it probably *was* a similar problem to yours, in that .bashrc wasn't being sourced. |
Administrator
|
Please comment the following lines:
Also, try adding a "echo $PATH" statement into the ~/.bashrc file as well (at the end).
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Who did you talk to? Me or SparHawk? By saying "comment" did you mean add it as comment to bashrc? I have wrote them to Konsole, it seems that the problem is solved. I will report you later if anything goes wrong. Thank you.
|
Administrator
|
By comment I meant editing ~/.bashrc and prefixing those lines with "#" - which will disable them.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
It comes back again. Nonetheless, I have found a temporary solution for this. Just close Dolphin and start it again. The error only occurs in the first open of Dolphin. After that, even you restart the computer, the bashrc still keeps working well. I just don't now how and when the error comes back.
The echo $PATH is:
|
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell