I noticed this one when installing 3.1.1 onto Suse 10.1
To get around it, I opened a second terminal window while the install was progressing and constantly changed the permissions of the sudoers file to what the installer wanted it to be.
I've no idea why it happens, but it should be a simple enough fix. |