Bug 1809934 - No password prompt in multi monitor setup with Intel GPU
Summary: No password prompt in multi monitor setup with Intel GPU
Keywords:
Status: CLOSED DUPLICATE of bug 1810070
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-04 08:55 UTC by Michal Konecny
Modified: 2020-03-09 10:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-09 10:45:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michal Konecny 2020-03-04 08:55:07 UTC
Description of problem:
I tried to rebase to Fedora 32 Silverblue on my Thinkpad X270 with Intel® HD Graphics 620 (Kaby Lake GT2) and my three monitor setup. After restart I choose the new entry in GRUB, but ended up with just a black screen on one of my monitors, other two were without input. Because I have LUKS encrypted disk I'm unable to get to GNOME without entering password.

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


How reproducible:
Have three monitors connected to Thinkpad X270 through dock station. Thinkpad should have LUKS encrypted disk.

Steps to Reproduce: (from running Fedora 31 Silverblue)
1. rpm-ostree rebase fedora:fedora/32/x86_64/silverblue
2. reboot
3. Choose first entry in GRUB

Actual results:
No LUKS password prompt

Expected results:
LUKS password prompt is shown

Additional info:
This is working in current Fedora 31 Silverblue.
Only thing possible to do in this situation is CTRL+ALT+DEL for reboot.

Comment 1 Michal Konecny 2020-03-04 10:16:31 UTC
Version of plymouth: plymouth-0.9.4-11.20191022git32c097c.fc32

Comment 2 Hans de Goede 2020-03-09 10:45:38 UTC
This is a known issue, a plymouth update fixing this is on its way.

I'm going to mark this bug as a duplicate of another bug for the same issue where this has been discussed in some more detail already.

*** This bug has been marked as a duplicate of bug 1810070 ***


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