Bug 468899 - no theme background during encrypted partition password dialog
no theme background during encrypted partition password dialog
Product: Fedora
Classification: Fedora
Component: plymouth (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-10-28 14:13 EDT by Eric Paris
Modified: 2009-12-18 01:40 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:40:58 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 Eric Paris 2008-10-28 14:13:48 EDT

When plymouth starts I get a cool themed background where stuff moves and I'm in awe just watching my computer boot.  When it asks me the password for my encrypted /home directory (my / is NOT encrypted) the background goes solid blue and is quite boring.

I want the background to stay consistent and awesome!
Comment 1 Charlie Brej 2008-10-28 17:47:55 EDT
Glad you enjoyed it. I deliberately left the password entry un-themed as I was afraid of bug reports from colour-blind, partially sighted and people who did not want fancy graphics getting in the way of functionality. If the consensus is that it would be a good thing then it would be trivial to replace the call to gradient shade with a draw image.
Comment 2 Charlie Brej 2008-10-30 14:51:28 EDT
Committed and now looks like this:
Comment 3 Ray Strode [halfline] 2008-10-30 16:27:33 EDT
black text looks bad on it though

(for e.g. "/home is password protected")

I'll see if I can do a black-on-white beveled look for the text so that it shows up on all backgrounds.
Comment 4 Ray Strode [halfline] 2008-10-30 17:44:01 EDT
i built this with the aforementioned change in comment 3 and requested it get pulled in by rel-eng
Comment 5 Bug Zapper 2008-11-25 23:23:03 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 6 Bug Zapper 2009-11-18 03:41:03 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 7 Bug Zapper 2009-12-18 01:40:58 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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