Cannot run bash scripts since 8.10 upgrade

Asked by Andy Hodgson

Here are the particulars...
I had three boxes running 8.04. I upgraded them to 8.10 (using the 'sudo do-release-upgrade' command). Since the upgrade, I now must sudo a bash script to get it to run (even though the permissions are set to 777). This requires me to give sudo privileges to every user who would run the script.

To narrow down the problem:
1) I did a full, from scratch install of 8.10 on a 4th box...and it does not exhibit this behavior.
2) In case there was a corruption in the /etc/passwd file - or something similar, I created a new user, made it an admin, and still get the behavior.
3) As the problem is on all three boxes, I know it isn't a machine-specific problem.

So, if anyone has any suggestions, I'm deeply grateful.

Andy

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu bash Edit question
Assignee:
No assignee Edit question
Solved by:
Guillermo Belli
Solved:
Last query:
Last reply:
Revision history for this message
W. Prins (wprins) said :
#1

What happens exactly when you run it without sudo? Any error messages?

Revision history for this message
Andy Hodgson (andy-nd-scientific) said :
#2

interestingly...

The system will hang at the command prompt. It cannot be interrupted with CTL+C...and, ultimately, requires a separate root-privilege login to kill the process. Using 'top', there does not appear to be any unusual processes running - only the bash connection from the user.

Revision history for this message
Best Guillermo Belli (glock24) said :
#3

You can try copying the bash settings from the "clean" installation into the upgraded machines.

Copy these files (systemwide configuration):

/etc/profile
/etc/bash.bashrc

and the user files (if exist):

~/.profile
~/.bashrc

Hope it helps.

Revision history for this message
Andy Hodgson (andy-nd-scientific) said :
#4

Your proposal seems to have solved the problem for the most part. I'm still somewhat perplexed why even newly-created users require the copying over of the bash profile files. It seems an odd corruption.

Thanks very much for your help.

Revision history for this message
Guillermo Belli (glock24) said :
#5

I'm glad that fixed it for you.

If you can reproduce the error, you should fill an error report too, so it gets fixed.

- Guille