Bug 177940 - Misleading System User screen in Firstboot
Misleading System User screen in Firstboot
Product: Fedora
Classification: Fedora
Component: firstboot (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
: FutureFeature
: 178627 (view as bug list)
Depends On:
Blocks: FC6Target
  Show dependency treegraph
Reported: 2006-01-16 13:17 EST by Clyde E. Kunkel
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-10 10:50:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Clyde E. Kunkel 2006-01-16 13:17:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20060103 Fedora/1.5-4 Firefox/1.5

Description of problem:
Clean install of FC5T2 from CDs. On firstboot the screen for System User caused me to pause a bit.  To me, a system user is one with privileges like root.  I think that substituting 'computer' for 'system' would make more sense.  The screen would be titled Computer User and the prompt would read:

    "It is recommended that you create a computer 'username' for     regular (non-administrative) use of your computer.  To create a computer username, please provide the information requested below."

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Clean install of FC5T2

Actual Results:  System User screen msg as described above.

Expected Results:  Suggest that computer vice system be used.

Additional info:
Comment 1 Chris Lumens 2006-01-22 20:07:55 EST
*** Bug 178627 has been marked as a duplicate of this bug. ***
Comment 2 Chris Lumens 2006-02-01 11:57:45 EST
I can't fix this for FC5 because we're already well past the freeze for
translations.  Adding to the FC6 tracker so I'll remember to do this right after
the release, though.

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