[kde] [Bug 488235] New: Authentication is required to auto-mount LUKS drive Plasma Desktop
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Sun Jun 9 03:40:40 BST 2024
https://bugs.kde.org/show_bug.cgi?id=488235
Bug ID: 488235
Summary: Authentication is required to auto-mount LUKS drive
Plasma Desktop
Classification: I don't know
Product: kde
Version: unspecified
Platform: NixOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: m1vri31c at duck.com
Target Milestone: ---
Created attachment 170283
--> https://bugs.kde.org/attachment.cgi?id=170283&action=edit
Authentication Pop-up
SUMMARY
Whenever a luks encrypted drive is plugged in – the ones I've tested have been
btrfs – the window pops up to enter your password, the drive is mounted, and
then a second window pops up asking for authentication. I always just press
cancel because it's already mounted.
STEPS TO REPRODUCE
1. Format external drive with btrfs and luks
2. Make sure auto-mount settings in Plasma are set to auto-mount that drive
3. Unmount the drive then plug it in
OBSERVED RESULT
Window opens to enter password, the drive is mounted. Then another window pops
up asking for authentication to mount the drive – SCREENSHOT ATTACHED.
Whether this is registered as mounted is inconsistent – sometimes it will
appear unmounted in the Disks and Devices system tray widget, sometimes it will
appear mounted, and Dolphin is similarly inconsistent. Sometimes you will need
to click the device in dolphin to "mount" it and no authentication is required.
But the drive is mounted and files can be accessed.
EXPECTED RESULT
Window opens to enter password, then drive is mounted, like mounting the drive
manually.
SOFTWARE/OS VERSIONS
NixOS 24.11 (unstable channel)
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
ADDITIONAL INFORMATION
Has happened since I started using Plasma 5 on Debian 12 earlier this year (now
am using NixOS and still having the issue).
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list