"su Cannot Start Error By Launching Yast From Kde"

Hi all,

I have a problem, as it seems to be related to local security / system security I thought it most go here.

I'll describe what happened in order to give more insight to the problem.

Yesterday everything was working correctly, but I decided to install a VM software from Sun called xVM Virtual Box. OK I downloaded the rpm for suse 10.3 and install it from yast with no problems.

After that I decided to create a virtual drive file in my partititon /usr/ but my normal user didnt have the correct permits so I did from console as root chmod 777 -R /usr. Then I created a new folder as my normal user with no problems. I ran the VM software to create a new machine and to create the virtual drive file in the new folder. everything was going smoothly.

When I tried to run for the first time that VM the software threw an error telling me that my normal user cant access certain location, it said to add my user to a new group the software created. So I launched Yast form the KDE menu with no problem. I entered Security and Users > User Management I selected my user, then Edit, Details tab and I added a check to the vrgroup then I clicked accept and thats all.

After that I still couldnt start my VM and also I noticed my Autoupdate icon changed to a yellow triangle with a ! sign. I mouse over it and it said it wasn't able to open autoupdate, and suggested to go to security settings and change in the security and users > Local security an option File Permisions to EASY, so I tried to launch Yast and I couln't It said something like " Su cannot start".

So what I did is to launch yast2 from the console and that worked, I checked those local security settings and the File permissions were actually in EASY so I don't know what to do to fix this. Could anyone help me please??

I appreciate your help.


---------UPDATE ----------------

I could solve the issue yesterday thanks to some advice I got from this site. The problem was that I changed the permissions to the /usr/ folder. I returned it's proper permissions and everything is workyng again as it should.

Thank you guys.