I have installed RH 6.2 on 6 i386 and on all them I have
problem with linuxconf while creating new users (in non graphic mode and
in gnome ). After creating all the account, linuxconf freeze (but it
creates the account). In console mode I get the freeze while executing
chage. In gnome, I can still play with the button of linuxconf but with no
This problem is not on console sparc but in gnome mode it also freeze.
Thanks and bye
(this is my first posting I hope this is ok :))
Pretty much the same happens to me when I create and/or change accounts.
Starting "gnome-linuxconf &" in a gnome-terminal gives me the following error
GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified
are supported and host-based authentication failed."
"linuxconf &" seems to start fine but freezes when accepting changes to the
I had two versions of this bug. The first time it occured the account and
password were created. The other time the account was createt but the password
changes were not applied.
"ps ax" showed me that linuxconf was still running but I was not able to kill
the procedure (both kill and killall failed).
I too had same problem. A quick fix is highly appreciated
*** Bug 13092 has been marked as a duplicate of this bug. ***
*** Bug 17041 has been marked as a duplicate of this bug. ***
I only use linuxconf from the command line. My i386 running fine on 6.1 (cartman) with linuxconf-1.16r10-2 until I upgraded to kernel version
kernel-2.2.16-3. Then this problem began.
I as well running into the same problem as the guy @ email@example.com. Same
configuration and same symptoms both in gnome and in text mode.
I also have tried to add a user in both gnome and command line and also using a
terminal in gnome, in each case when creating the new user and then typing in
the password at this point linuxconf hangs, however it seems to create the user.
Upgrading linuxconf to 1.25 fixes this problem.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.