Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1381136 - Unable to clean restart/shutdown when enter the wrong luks password.
Summary: Unable to clean restart/shutdown when enter the wrong luks password.
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 08:37 UTC by Frank Büttner
Modified: 2021-04-30 10:00 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github systemd systemd issues 13757 0 None open Don't hang in the boot process if the password agent failed or crashed 2021-02-02 12:00:52 UTC
Red Hat Bugzilla 1324026 0 unspecified CLOSED Failed to start Cryptography Setup for luks 2022-05-16 11:32:56 UTC

Internal Links: 1244404 1324026

Description Frank Büttner 2016-10-03 08:37:50 UTC 
Description of problem:
When using an luks encrypted disk for the root system and you enter the password 3 times wrong, then the system seem to be frozen. Not reboot (Ctrl+Alt+Del) work and no shutdown option are presented to the user.

Version-Release number of selected component (if applicable):
systemd-229-13.fc24.x86_64

How reproducible:
Every time when you enter 3 times the wrong password.

Steps to Reproduce:
1. boot the system
2. enter 3 times an wrong password
3.

Actual results:
The system seems to be frozen.

Expected results:
That an messages is shown, or can clean reboot/power off will be possible.
Comment 1 Fedora End Of Life 2017-07-25 23:20:06 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 EOL if it remains open with a Fedora  'version'
of '24'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.
Comment 2 Frank Büttner 2017-07-26 14:33:02 UTC 
Same on F25
Comment 3 Fedora End Of Life 2017-11-16 19:19:56 UTC 
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 EOL if it remains open with a Fedora  'version'
of '25'.

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.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 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, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

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.
Comment 4 Christian Stadelmann 2017-11-16 23:33:14 UTC 
Still present on Fedora 27.
Comment 5 Christian Stadelmann 2018-10-08 13:09:32 UTC 
Still present on Fedora 29 beta.
Comment 6 Ben Cotton 2018-11-27 14:07:45 UTC 
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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
EOL if it remains open with a Fedora  'version' of '27'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 27 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 7 Ben Cotton 2019-10-31 19:14:56 UTC 
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 EOL if it remains open with a
Fedora 'version' of '29'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 8 Frank Büttner 2019-11-01 16:32:06 UTC 
Same on f30
Comment 9 Christian Stadelmann 2019-12-05 20:52:40 UTC 
(In reply to Frank Büttner from comment #8)
> Same on f30

I *think* this issue is fixed on Fedora 31. Can you confirm that?
Comment 10 Frank Büttner 2019-12-06 14:57:21 UTC 
I can't update to F31, because an 3rd party python app don't support the python version of f30.
So I can't test it on F31.
Comment 11 James 2020-02-16 19:01:52 UTC 
(In reply to Christian Stadelmann from comment #9)
> (In reply to Frank Büttner from comment #8)
> > Same on f30
> 
> I *think* this issue is fixed on Fedora 31. Can you confirm that?

On Fedora 31, attempting to enter the wrong password 5 times results in the boot screen just stuck at the spinner. At the moment the user has to hit Esc to see that cryptsetup failed. If simply left, the process times out and one is left with a stream of messages about dracut-initqueue timeout, before being dumped to an emergency root prompt. This doesn't seem an appropriate way to handle the incorrect LUKS password being entered -- which is a normal possible condition that should be handled gracefully.

It is possible to Ctrl+Alt+Del and reboot, but this is still poor user experience. There is too little user feedback. Ideally it should show:

1. Indication that the password entered is wrong.
2. The number of attempts remaining.
3. After all attempts are exhausted, say the machine will shut down in e.g. 30 seconds, then do so.
Comment 12 Ben Cotton 2020-04-30 20:25:31 UTC 
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
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 EOL if it remains open with a
Fedora 'version' of '30'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 13 Frank Büttner 2020-05-01 06:44:09 UTC 
Same on F31
Comment 14 Christian Stadelmann 2020-05-01 11:38:50 UTC 
Also with 32.
Comment 15 Christian Stadelmann 2020-05-01 14:07:05 UTC 
How about this:

Edit systemd-ask-password-console.service¹, add the following line:
OnFailure=systemd-poweroff.service

(alternative: OnFailure=systemd-reboot.service)

Would this give the expected behavior?

¹ and probably also systemd-ask-password-wall.service and systemd-ask-password-plymouth.service. I don't use these though.
Comment 16 Fedora Program Management 2021-04-29 15:52:42 UTC 
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 EOL if it remains open with a
Fedora 'version' of '32'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 17 Frank Büttner 2021-04-30 10:00:00 UTC 
same for f33
Note You need to log in before you can comment on or make changes to this bug.