Bug 125234
| Summary: | [PATCH] redhat-config-users does not set account expiration, and when fixed sets it incorrectly | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Josef Bacik <jbacik> | ||||
| Component: | redhat-config-users | Assignee: | Nils Philippsen <nphilipp> | ||||
| Status: | CLOSED ERRATA | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.0 | CC: | dhoward, jhibbets, okhayat, tao | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2004-12-20 21:25:54 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created attachment 100853 [details]
The patch that fixes both the invalid variable name and the wrong date problem
This will fix the variable name for in userProperties.py so you can at least
set the expiration date. This also has the workaround for the wrong date
problem, albiet it is not the greatest patch in the world, it works.
*** Bug 126347 has been marked as a duplicate of this bug. *** Patch applied and contained in system-config-users-1.2.14-1 in Rawhide. Please let me know if you need a formal errata created for this bug. Just a note, I applied the patch to a new system and noticed that I messed up with the date problem, and I'm working on fixing it now. You can still set the expiration date fine. I don't think this needs to be an errata, I only had one user with this problem and he was content with the patch I sent him. *** Bug 128429 has been marked as a duplicate of this bug. *** This is supposed to be fixed in redhat-config-users-1.1.18-2. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-557.html |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040301 Description of problem: When you try to set a user accounts expiration date, you will set it, hit ok, then open it back up and there will be no expiration date. This is fixable, the programmer simply made a typo. But when that is corrected the program still sets the wrong expiration date. Say for instance I set an account to expire June 3, 2004, it will enter it as expiring June 4, 2004. I do not beleive this to be a bug with redhat-config-user, but rather with the library libuser. I have patched it through redhat-config-user however, its ugly, but it works, and I'm going to attatch it to this bugzilla report. As soon as I figure out how to that is :) Version-Release number of selected component (if applicable): redhat-config-users-1.1.18-1 How reproducible: Always Steps to Reproduce: 1.Open redhat-config-users 2.Set the expiration date for the account 3.Press ok 4.Look at the user properties again, there will be no expiration date Actual Results: You didnt see and expiration date. After the variable name problem was fixed, I set the expiration date with usermod to June 1, 2004, and when I pulled it up on redhat-config-users, got an expiration date of May 31, 2004 Expected Results: I should have been able to set the expiration date to begin with. Also should have seen June 1, 2004 as the expiration date in redhat-config-users. Additional info: I beleive the second part of this problem to not actually be a problem with redhat-config-users, but rather with libuser and perhaps the time in the on_ok_button_clicked function.