Bug 147869

Summary:	Administrator mode willl not work, generates a 'conversation with su failed' every time. Correct password IS used.
Product:	[Applications] systemsettings	Reporter:	Jane Colman <Janecolman>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	finex
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jane Colman 2007-07-14 14:57:34 UTC

Version:           0.2 (using KDE 3.5.5, Kubuntu (edgy) 4:3.5.5-0ubuntu3)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.17-10-generic

I am the only user of this system (Kubuntu).  I can logon to the system fine.  However, attempting to use the Administrator Mode in System Settings will not  allow  me to make  any administrative changes as every time I get an error message that 'conversation with su failed'.  The only administrative change that I have been able to successfully use is changing the time via the system tray applet.  The su box does accept my one and only password there.

Comment 1 Bruce Mayo 2007-12-05 16:51:40 UTC

Using KDE 3.5.8, Kubuntu Gutsy (7.10).
I have the same problem, but only AFTER performing a general package upgrade with apt-get on 04.12.2007. Systemsettings on the kubuntu 7.10 distribution CD seems to be ok. 
To try to isolate the problem, I reinstalled Kubuntu from the original CD and saved the directories etc, tmp, var, lib. Systemsettings is ok. Again, I updated with apt-get upgrade, to get all updates as of 04.12.2007. Again, systemsettings would not go into admin mode, although I had no problem with sudo or su in a terminal. Restoring etc, tmp, var and lib from the backups did not fix the problem. 
I am only user of the system. The problem appears immediately after upgrade.

Comment 2 Fabio Correa 2008-01-22 16:59:39 UTC

This is a duplicate of Bug #115417.

Comment 3 FiNeX 2008-11-13 23:12:08 UTC


*** This bug has been marked as a duplicate of bug 115417 ***