https://bugs.kde.org/show_bug.cgi?id=521583

Nate Graham <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=467098
     Ever confirmed|0                           |1
           Severity|normal                      |critical
           Priority|NOR                         |HI
           Platform|Other                       |Fedora RPMs
             Status|REPORTED                    |CONFIRMED
                 CC|                            |[email protected],
                   |                            |[email protected]

--- Comment #1 from Nate Graham <[email protected]> ---
Setting severity to critical since this could easily lead to data loss if you
aren't enough of a technical expert to know how to recover the system once it's
in this state (so I'm very glad you were!).

I can easily see how this could happen. And due to Bug 467098, if you tried to
bypass this by saving the password using KWallet, there would be still a
graphical prompt anyway (and of course even if that were fixed, we can't count
on all users using it).

So for the LUKS case, we need kded's auto-mounter module to run after the
graphical session is up and running, so the user can handle the LUKS case.

Trouble is, we also want it to run as early as possible so that disks are
auto-mounted by the time any apps are auto-started or session-restored; if they
try to access resources on disks that haven't auto-mounted yet, they'll be very
sad.

Perhaps we need to split the auto-mounter into two modules: one for unencrypted
disks that runs as early as possible, and one for LUKS-encrypted disks that
runs late, once the graphical session is up and running.

And we should also warn the user in some way if any of the non-boot disks they
have set up to auto-mount using Plasma's auto-mounter are LUKS-encrypted. They
should know that these disks will mount late, so nothing that auto-starts
should be set up to access data from those disks.

All of this could also benefit from making better use of systemd's features,
too. We're kind of re-inventing the wheel with all of our fancy KDE-specific
auto-mount code.

Raising priority both due to the above, and also because we'll need to resolve
this before we can move forward with turning auto-mount on by default as we
discussed during the 2026 Plasma sprint.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to