Bug 466504 - no errors if failed to open encrypted partition
no errors if failed to open encrypted partition
Product: Fedora
Classification: Fedora
Component: mkinitrd (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Peter Jones
Fedora Extras Quality Assurance
Depends On:
Blocks: F10Target
  Show dependency treegraph
Reported: 2008-10-10 12:17 EDT by Jeff Bastian
Modified: 2009-12-18 01:32 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:32:56 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 Jeff Bastian 2008-10-10 12:17:16 EDT
Description of problem
Due to bug 464580, plymouth fails to open my LUKS encrypted /dev/sda2

I would expect an error message to appear, e.g., the cryptsetup error
    Command failed: can not access device
but, instead of showing an error, plymouth happily proceeds with the splash screen (spinfinity) as if everything were booting normally.  I can watch the white/light-blue/dark-blue progress bar move across the screen until the whole bar is white, and I expect to see gdm a few seconds later, but nothing happens.  It just sits there with a white bar forever.

Plymouth needs to inform the user if there was an error opening the encrypted drive.

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

How reproducible:
Every time

Steps to Reproduce:
1. Boot system
2. Enter LUKS password
Actual results:
The spinfinity progress bars indicate booting is working normally

Expected results:
An error message should appear

Additional info:
Comment 1 Ray Strode [halfline] 2008-10-10 13:36:18 EDT
i guess we could check the return code of ask-for-password and call plymouth --hide-splash if it fails.

Previously it would ask for the password indefinitely, but I recently changed it to give up after 3 times I think.
Comment 2 Jeff Bastian 2008-10-10 14:27:30 EDT
Can you check the return code in nash?  Maybe I'm doing something wrong, but it doesn't appear nash supports any kind of if-then-else logic.  I've tried a couple forms of bash syntax and nash just seems to ignore it.

if [ $? = 0 ]; then
        echo true
        echo false

if /bin/false
        echo true
        echo false

$ /sbin/nash t.sh
/bin/echo  'true'
/bin/echo  'false'
/bin/echo  'true'
/bin/echo  'false'
Comment 3 Ray Strode [halfline] 2008-10-10 15:08:26 EDT
not sure.  Do you know, Peter?
Comment 4 Bug Zapper 2008-11-25 22:45:05 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 5 Bug Zapper 2009-11-18 03:33:12 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 6 Bug Zapper 2009-12-18 01:32:56 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.