Bug 677999 - change of user's password fails when user has no password set
Summary: change of user's password fails when user has no password set
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-users
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 677385
TreeView+ depends on / blocked
 
Reported: 2011-02-16 13:22 UTC by Nils Philippsen
Modified: 2016-08-11 11:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 677385
Environment:
Last Closed: 2016-08-11 11:59:10 UTC
Type: ---


Attachments (Terms of Use)

Description Nils Philippsen 2011-02-16 13:22:01 UTC
+++ This bug was initially created as a clone of Bug #677385 +++

Description of problem:
It's not possible to change password of user that has been created via useradd with no password set. Password fields are disabled.

Version-Release number of selected component (if applicable):
system-config-users-1.2.104-1.el6_0.3.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a user with no password: useradd -m mytestuser
2. Start system-config-users and try to change his password.
  
Actual results:
Impossible to change user's password (via s-c-u)

Expected results:
It should be possible to change password of user even thought it wasn't set before.

Additional info:

--- Additional comment from nphilipp on 2011-02-16 08:19:45 EST ---

This issue exists on the current git HEAD as well.

Comment 1 Nils Philippsen 2011-02-16 13:36:02 UTC
This is not actually a bug, as the account is locked and can be unlocked in the "Account Info" tab.

Comment 2 Nils Philippsen 2016-08-11 11:59:10 UTC
Thanks for taking the time to submit this bug. Unfortunately, I haven't gotten
around to fix this issue, sorry for that.

Because I don't actively develop system-config-users anymore, I won't likely
find the time to work on this ticket, so I'll close it now.


Note You need to log in before you can comment on or make changes to this bug.