Bug 1577949

Summary:	Fedora will not prompt me for a LUKS password unless a monitor is plugged in
Product:	[Fedora] Fedora	Reporter:	Randy Barlow <rbarlow>
Component:	cryptsetup	Assignee:	Milan Broz <gmazyland>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	29	CC:	agk, gmazyland, okozina
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-27 19:20:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Randy Barlow 2018-05-14 13:44:31 UTC

Description of problem:
I noticed some months ago, perhaps around January or February, that I was not able to boot a LUKS-encrypted (with password) headless computer unless I had a monitor plugged in. Previously, it would boot without a monitor - I would wait a while to give it time to get to the LUKS password prompt, and then I would type the password, and I could tell it worked because the HD access light would go bonkers as it continued to boot.

I found that if I plug a monitor in after it is booted, it is booted into Fedora but it is not prompting me for a password. I believe something is detecting that there is no monitor and figuring that it would be pointless to prompt for a password, but I find purpose in password prompting still ☺

I'm not sure that cryptsetup is the right component, so please feel free to switch the component if you think it's something else.


Version-Release number of selected component (if applicable):
cryptsetup-2.0.3-3.fc29.x86_64


How reproducible:
Every time on my machine.


Steps to Reproduce:
1. Boot LUKS-encrypted computer with no monitor attached.


Actual results:
It will not prompt for password, and you will never be able to complete the boot.


Expected results:
It should prompt for password.

Comment 1 Randy Barlow 2018-05-14 13:46:02 UTC

Tom Hughes suggested that this ticket might make sense to file under systemd-cryptsetup-generator.

Comment 2 Jan Kurik 2018-08-14 10:56:24 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle.
Changing version to '29'.

Comment 3 Ben Cotton 2019-10-31 20:45:54 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 4 Ben Cotton 2019-11-27 19:20:45 UTC

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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