https://bugs.kde.org/show_bug.cgi?id=521583
Bug ID: 521583
Summary: KDE Plasma Removable Devices automount causes
systemd-cryptsetup boot loop / emergency mode on
secondary internal encrypted SSD (LUKS)
Classification: Applications
Product: systemsettings
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: kcm_deviceautomounter
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Distribution: Fedora (KDE Spin)
Desktop Environment: KDE Plasma (System Settings -> Removable Devices)
Hardware Configuration:
The system has two physical internal SSDs. The secondary internal SSD is
permanently mounted inside the laptop (SATA/M.2 slot) and is fully encrypted
via LUKS, partitioned into "Zaszyfrowany napęd" and "Dysk 2".
Steps to reproduce:
1. Open System Settings -> Removable Devices (Samopodpinanie urządzeń).
2. Under "Attached Devices", find the secondary internal encrypted SSD.
3. Check the boxes for both "On Login" (Po zalogowaniu) and "On Attach" (Po
podłączeniu) for this internal drive.
4. Reboot the computer.
Actual result:
During early boot, systemd attempts to mount and activate the secondary
internal encrypted SSD before the graphical environment or the user's password
wallet (pam_kwallet) is initialized.
The boot process hangs on: "Starting systemd-cryptsetup@luks...".
Since it's a headless early-boot stage, no password prompt is provided to the
user. The job eventually times out and fails: "FAILED Failed to start
systemd-cryptsetup...".
Following this, Fedora drops into Emergency Mode. Because the root account is
locked by default on Fedora, the screen shows "Cannot open access to console,
the root account is locked", completely bricking the system boot for standard
users until rescued via "init=/bin/bash" in GRUB.
Expected result:
1. The "Removable Devices" (Samopodpinanie urządzeń) module should NOT treat
permanently connected internal secondary SSDs the same way it treats removable
USB drives, or at least it should warn the user about LUKS containers.
2. If an internal LUKS drive is selected, KDE should automatically apply safe
flags like "noauto,x-systemd.automount" to prevent systemd from blocking the
critical boot chain if the drive isn't unlocked yet.
--
You are receiving this mail because:
You are watching all bug changes.
