[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Configuration error running su in unstable



Harv Nelson wrote:

Hi Chris,

Just did a Google on "QUOTAS_ENAB" error and ran into your post of 03 October 2005 on the Debian users list.

I just ran into exactly the same problem this morning. Have you found a solution yet?

My solution is as follows:

Open a root terminal session and

apt-get --purge remove gksu

On my system (Debian "etch"/testing) that also took out "foomatic-gui" and "gdm". No loss on the "gdm" since I run KDE and use "kdm".

So far, "Synaptic" seems to be relying on "kdesu" to collect the root password. I've yet to discover how the system will react to the missing "foomatic-gui". Can't say as I remember ever using it for anything. The scanner and printer all seem to get along with out it.

Hello Harv.

Thanks for the message.  I am puting this back on the list.

The problem persisted even after I purged gksu as you suggested, ie:

$ su
Password:
configuration error - unknown item 'QUOTAS_ENAB' (notify administrator)
configuration error - unknown item 'NOLOGIN_STR' (notify administrator)
configuration error - unknown item 'ENV_HZ' (notify administrator)
configuration error - unknown item 'PASS_MAX_LEN' (notify administrator)
configuration error - unknown item 'CHFN_AUTH' (notify administrator)
configuration error - unknown item 'CLOSE_SESSIONS' (notify administrator)
#

I removed gdm first without purging since I use gdm as my graphical login and I wanted to keep the settings. Purging gksu removed gdm and gnome-netstatus-applet.

In any case, I don't think that the problem lies in X. Entering a username at any virtual terminal (eg ctrl-alt-F2) produces the same error messages. It seems that the login package is the culprit. Howard emailed me this link earlier:
http://www.linuxquestions.org/questions/showthread.php?s=&postid=1873845#post1873845
so someone else had the problem, but it went away on the next upgrade. Not so in my case. Obviously, removing the login package is not an option. I might try forcing a reinstallation with dpkg.

Regards,
Chris.



Reply to: