"bad interpreter: Input/output error"

[Jeff]

On 1/13/24 14:57, Jim Byrnes wrote:

 > I'm sure you did maybe I missed you saying it, but did you check what
 > was installed during the update that messed up Python for you.

Unfortunately, no. I'm pretty sure there was a kernel update, which is 
why I had to reboot.

And it turns out that while Python troubles were the first thing that 
bit me, it's shebang lines in general that are broken. I can't 
effortlessly execute shell scripts, either (same error message).

Ian is clearly onto something when he suggests it's NAS-related, but I'm 
just stumped why it's never happened until now and why a different 
computer running an up to date Ubuntu Server isn't suffering from the 
same issue.

On 1/13/24 15:31, Karl Auer wrote:

 > Grasping at straws, but could something like AppArmor or SELinux be at
 > work here?

I've never configured either one, so I'm assuming I don't use them.

 > might it be worth asking your question in a suitable python forum as
 > well?

It certainly couldn't hurt, though as I said above, the problem appears 
to be more fundamental. But you got me thinking that I should also try a 
Perl script and...same problem. So it really looks like whatever is 
going on is at a lower level than anything related to a particular language.