Bug 963968 - "Root password was set by kickstart" is unnecessarily jargon-ish
Summary: "Root password was set by kickstart" is unnecessarily jargon-ish
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: initial-setup
Version: 19
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
Assignee: Vratislav Podzimek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-16 22:18 UTC by Adam Williamson
Modified: 2013-06-12 03:37 UTC (History)
1 user (show)

Fixed In Version: anaconda-19.30.3-1.fc19
Clone Of:
Environment:
Last Closed: 2013-06-12 03:37:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2013-05-16 22:18:32 UTC
When the root password has been set (or even when it hasn't...but that's another bug) in anaconda, initial-setup displays:

"Root password was set by kickstart"

Even if you didn't do a kickstart install. That seems a bit jargon-y and unnecessarily confusing. It could just say "Root password is set" or "Root password was set during installation" or something more straightforward like that.

Comment 1 Fedora Update System 2013-06-06 18:37:01 UTC
anaconda-19.30.3-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/anaconda-19.30.3-1.fc19

Comment 2 Fedora Update System 2013-06-07 15:41:32 UTC
Package anaconda-19.30.3-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-19.30.3-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-10283/anaconda-19.30.3-1.fc19
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-06-12 03:37:55 UTC
anaconda-19.30.3-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


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