Not accepting root password

Hi.

I just installed "etch" from the latest network install cd.
I am trying to change some of the settings in the control centre(kde) but it will not accept my root password. I know I am typing it in correctly because i can change to root in konsole.

When i click on Administrator mode. A msg box appears "Run as root - KDE su". It asks me for my password. I type it in. and i get another msg box saying. Inccorect password; please try again.

I hope thats enough info. Does anyone have any ideas?

THanks in advance

Originally Posted by Mutch Hi. I just installed "etch" from the latest network install cd. I am trying to change some of the settings in the control centre(kde) but it will not accept my root password. I know I am typing it in correctly because i can change to root in konsole. When i click on Administrator mode. A msg box appears "Run as root - KDE su". It asks me for my password. I type it in. and i get another msg box saying. Inccorect password; please try again. I hope thats enough info. Does anyone have any ideas? THanks in advance

had same problem see here
http://www.linuxquestions.org/questi...d.php?t=492332
and here
http://www.linuxquestions.org/questi...d.php?t=492258
I upgraded to sid and it went away

Originally Posted by wrat I upgraded to sid and it went away

Ahhh thanks.

So upgrading to sid is the only option?

WOuldn't it be easier to just change the version of KDE being used?

Not that i know how to do that....

Yes, the problem was one of the kde packages upgraded and the others didn't

Sid is a better place. Things get fixed quicker there.

Isn't there a way to just upgrade the kde packages?

Im not sure if i trust my nooby self on an unstable distro.

Don't get fooled by the name. I had same problem, updated to sid and it's fine.

Solutions:

#1 You can upgrade to sid as has been stated.

- change your /etc/apt/sources.list to point to the sid repositories instead of the etch repositories.
- apt-get update
- apt-get dist-upgrade


#2 Start your super user file manager from the command line until the problem is resolved.

- open a terminal (as a normal user) and type: xhost +
- then type: su
- enter root password
- then type: konqueror --profile filemanagement

Originally Posted by jdog006 Solutions: #1 You can upgrade to sid as has been stated. - change your /etc/apt/sources.list to point to the sid repositories instead of the etch repositories. - apt-get update - apt-get dist-upgrade #2 Start your super user file manager from the command line until the problem is resolved. - open a terminal (as a normal user) and type: xhost + - then type: su - enter root password - then type: konqueror --profile filemanagement

Thanks so much! The apps from console wasn't working for me before but this does. Must be the xhost +. What does that do anyway?

Run in a terminal ls -l $(which su)

your output should look something like rwsr-xr-x 1 root root 27000 Sep 17 04:05 /bin/su
If its much different your permissions are messed up for su.
I can't remember the exact permission it needs, but pop in the Debian IRC someone there will know.
/server irc.debian.org
/join #debian

Upgrading to Sid isn't the only way to fix it. Nor is upgrading to Sid a good thing to do unless you know a) where to look to fix problems, or b) already know how to fix them without help.

Originally Posted by RedNovember Thanks so much! The apps from console wasn't working for me before but this does. Must be the xhost +. What does that do anyway?

"xhost +" allows other users to use you X-window-system. In this case we need to allow root to use it while you are logged in as a regular user.

There is a slight security risk but it is minimal and you will only be using it temporarily. "xhost +" is a temporary workaround and doesn't permanently change any settings. Everytime X is restarted it will revert to the original permissions because we haven't permanently changed anything.

You can type: "man xhost +" for more information. There are additional options to limit X authority. But like I said, the security risk is very minimal. If you are on a home network that is behind a router there is virtually no security risk at all.