Bug 5021

Summary:	No user login list/icons in KDM when security set to server
Product:	Mageia	Reporter:	Jeff Robins <jeffrobinsSAE>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	minor
Priority:	Normal	CC:	davidwhodgins
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Jeff Robins 2012-03-19 08:36:18 CET

Description of problem:
When I set the security level at install to server, then there are no user login icons or a list of users in KDM after install.  Both Beta 1 and Beta 2 have the same problem.  Installing with security not set to server, then user login icons are present in KDM.  

Version-Release number of selected component (if applicable):
Mageia 2 Beta 1 and Beta 2

How reproducible:
Every time I install and/or boot

Steps to Reproduce:
1. Begin install of Beta 1 or Beta 2
2. Set security level to server during the install process
3. Finish install
4. Boot

Comment 1 Dave Hodgins 2012-03-19 19:28:54 CET

I haven't tested it, but that should be changeable by running
msecgui (as root), selecting the Security settings tab, then
the system security tab, and double click on the ALLOW_USER_LIST
option, and change it to yes.

CC: (none) => davidwhodgins

Comment 2 Jeff Robins 2012-03-21 05:01:31 CET

Thank you, changing the value in msecgui worked.  

BTW, if it security is setup as befitting a server, with a hidden user list, why is the guest account enabled by default?

Comment 3 Dave Hodgins 2012-03-21 07:42:05 CET

(In reply to comment #2)
> Thank you, changing the value in msecgui worked.  

You're welcome.

> BTW, if it security is setup as befitting a server, with a hidden user list,
> why is the guest account enabled by default?

That has been discussed a lot, and while I haven't checked how msec settings
affect it, my understanding, is that it will not be for Mageia 2.

I'll close this bug as invalid, since it's just about a configuration
choice.

Feel free to reopen this bug report, if you disagree.

Status: NEW => RESOLVED
Resolution: (none) => INVALID