Bug 452824 - Successfully mounting LUKS storage gives "You are not authorized to mount" message
Summary: Successfully mounting LUKS storage gives "You are not authorized to mount" me...
Status: RESOLVED WORKSFORME
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 21.12.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-21 11:25 UTC by joey.joey586
Modified: 2022-04-24 13:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
video of bug (2.81 MB, video/mp4)
2022-04-21 11:25 UTC, joey.joey586
Details

Note You need to log in before you can comment on or make changes to this bug.
Description joey.joey586 2022-04-21 11:25:58 UTC
Created attachment 148281 [details]
video of bug

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Insert a LUKS encrypted usb drive
2. Type in password and mount as usual
3. 

OBSERVED RESULT
Drive mounts successfully, but gives false "You are not authorized to mount" message

EXPECTED RESULT
Drive should be shown as properly mounted

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.93.0
Qt Version: 5.15.3
Kernel Version: 5.17.2-arch3-1 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz
Memory: 11.5 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-04-22 15:27:34 UTC
This works for me with my LUKS-encrypted disk. I suspect there are some weird polkit rules at play here, but don't have the expertise to offer anything more than that.

Any chance you can ask folks for help in an Arch-specific forum?
Comment 2 joey.joey586 2022-04-24 04:30:46 UTC
Sorry, my bad. Turns out it was something wrong with my KDE configs. I created a new home folder and with it new configs and I don't get that error anymore. Sorry for wasting your time.
Comment 3 Nate Graham 2022-04-24 13:17:28 UTC
I had a feeling. :) Glad it's fixed now.