RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 612665 - Plymouth password icon could use some indication it's for a hard drive password
Summary: Plymouth password icon could use some indication it's for a hard drive password
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: plymouth
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-08 18:13 UTC by Subhendu Ghosh
Modified: 2016-10-04 04:30 UTC (History)
6 users (show)

Fixed In Version: plymouth-0.8.3-20.el6
Doc Type: Bug Fix
Doc Text:
Previously, the system prompted for a password on boot but provided no hint as to what the password was for. That caused unnecessary confusion for some users, who didn't know which of their passwords to enter. With this update, a hard drive icon has been added to prompts associated with encrypted disk volumes and the password prompts for encrypted disks are now easy to recognize.
Clone Of:
Environment:
Last Closed: 2011-05-19 14:02:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
encrypted drive icon suitable for the purpose (94.93 KB, application/octet-stream)
2010-12-14 22:53 UTC, Jakub Steiner 		no flags Details
old vs. new icon comparison (5.59 KB, image/png)
2011-03-11 12:24 UTC, Jiri Koten 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0686 0 normal SHIPPED_LIVE plymouth bug fix update 2011-05-18 18:10:27 UTC

Description Subhendu Ghosh 2010-07-08 18:13:15 UTC 
Description of problem:

Install RHEL6 B2 on encrypted volume.

On boot the systems prompts for a password - but provides no hint what the password is for. 


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


How reproducible:
Always


Steps to Reproduce:
1. Install on encrypted volume
2. reboot
3. prompted for password
  
Actual results:

no hints on what the password is for.

Expected results:

hints on what the passowrd is for.

Useful if different volumes have different passwords.
Additional info:
Comment 2 Ray Strode [halfline] 2010-07-08 19:05:02 UTC 
So the issue here is we don't have access to fonts, translations, etc until the root filesystem is mounted.

It's not a problem in practice, though, because in most circumstanced we only need to know one thing before mounting the root filesystem. Namely, we need to know the password to mount the root filesystem with.

Since it's only one thing, and the user already knows he/she will need to enter it to continue, conveying "nows the time to type your password" is all we need to do.  We accomplish this with a "lock icon" and a text entry field on screen.

We could potentially change the lock icon to a hard drive icon with a lock emblem or some such.  That would make it even clearer it's a "hard drive password" and not just a password.
Comment 5 Ray Strode [halfline] 2010-07-16 20:15:00 UTC 
This missed the non-blocker deadline, proposing for 6.1
Comment 7 Ray Strode [halfline] 2010-11-30 18:56:12 UTC 
ack if I can get suitable artwork
Comment 9 Jakub Steiner 2010-12-14 22:53:13 UTC 
Created attachment 468724 [details]
encrypted drive icon suitable for the purpose

SVG included as source,  not intended for installation
Comment 13 Jiri Koten 2011-03-11 12:24:09 UTC 
Created attachment 483701 [details]
old vs. new icon comparison

New drive icon from comment 9 is present in plymouth-0.8.3-22.el6.
Comment 15 Tomas Capek 2011-04-28 15:09:56 UTC 
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, the system prompted for a password on boot but provided no hint as to what the password was for. That caused unnecessary confusion for some users, who didn't know which of their passwords to enter. With this update, a hard drive icon has been added to prompts associated with encrypted disk volumes and the password prompts for encrypted disks are now easy to recognize.
Comment 16 errata-xmlrpc 2011-05-19 14:02:46 UTC 
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 therefore 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-2011-0686.html
Note You need to log in before you can comment on or make changes to this bug.