Bug 963797

Summary:	Inital setup cannot change no password to password required set from anaconda; user not shown and cannot log in
Product:	[Fedora] Fedora	Reporter:	satellitgo
Component:	initial-setup	Assignee:	Vratislav Podzimek <vpodzime>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	19	CC:	satellitgo, vpodzime
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	anaconda-19.30.9-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-18 11:11:39 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description satellitgo 2013-05-16 14:51:31 UTC

Description of problem:
I just found a bug in initial-setup  : I installed live Mate-compiz x86_64 with root password and user with [ ]user requires password unchecked. After reboot to installed system in I-S i added a password and then tried to log in my user was not able to in other and was not listed...It does not work correctly.

mate does not have a users available to change in root which worked....catch 22

reinstalled mate-compiz live with root and user with passwords then on reboot just clicked on continue  in I-S and user appeared and password worked

Version-Release number of selected component (if applicable):
Mate-compiz live x86-64 Beta RC1

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info: installed from root terminal with liveinst command

Note this will not work on first try with anaconda 19.27-1 but start on second try in terminal  - BZ 963503

Comment 1 Vratislav Podzimek 2013-06-12 12:23:31 UTC

As described in bug #968915, the first problem is that the user created by the Anaconda was created as locked instead of with no password. 

The other problem is what i-s does or doesn't do. It is meant to be used only for creating users and not modifying existing ones, thus the change is not reflected. This will be resolved by the User Creation screen being hidden in the i-s if the user is created in the installation process.

Comment 2 Fedora End Of Life 2015-01-09 22:33:49 UTC

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-18 11:11:39 UTC

Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.