KDE not recognizing su password?

m_lp_ql_m · 10-21-2006, 07:45 PM

When I try to run synaptic or just konqueror in su mode, it claims I have an incorrect password. I know I'm typing it right- I'm able to use this password in konsole to log in as su or sudo. This was working just a few days ago, how can I fix this?

I'm running Debian Etch, kernel 2.6.17.

aus9 · 10-21-2006, 07:50 PM

when you open a terminal and have (normally) a prompt with the $ sign you are a normal user

then type su and if passwd is correct prompt changes to #

now issue command konqueror or synaptic

m_lp_ql_m · 10-21-2006, 11:18 PM

I didn't have to do that workaround before, I'd really like to not have to do it now. Why the sudden change?
The real reason is because I suspect this inability to recognise my root password is contributing to a printer problem. KDE isn't able to connect to the CUPS server; I suspect this is why.

XavierP · 10-22-2006, 03:31 AM

This seems to be a bug in KDE 3.5.5 on Debian Etch (I have the same problem). I did some limited searching last night and the only woraround right now is to downgrade KDE to 3.5.4.

sleekmason · 10-22-2006, 11:19 AM

I've had the same problem. Fortunately I use Fluxbox, which allowed me to set up root permissions real easy in my menus.

Myself, and others have had success in upgrading to sid. (soon to be the new testing)

All I upgraded were those parts of kde that seemed important to this problem. Worked just fine.

m_lp_ql_m · 10-22-2006, 11:36 AM

Ah, OK, a bug I can deal with; I can get on with my life.

Am I somewhat right in assuming that this permission problem may be associated with my inability to print?

XavierP · 10-22-2006, 12:14 PM

Looking through some of the bug reports, yes I'm afraid so. Two workarounds I have seen reports of success are to upgrade to Sid or to downgrade parts of KDE. Your best bet is to check the Debian bug reports to see what people are trying and to see when it's fixed.

m_lp_ql_m · 10-22-2006, 05:02 PM

Awright then, thanks!

XavierP · 10-22-2006, 06:54 PM

Incidentally, I upgraded to Sid and it broke a lot of things. Which is why I'm back to Slack. Be far more careful than I was if you upgrade!