Bug 502197

Summary: kio-admin: acting as an administrator in dolphin doesn't work anymore in NixOS
Product: [Frameworks and Libraries] frameworks-kio Reporter: ilay-JBR <ilya.jeibar>
Component: generalAssignee: KIO Bugs <kio-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: normal CC: ilya.jeibar, john.kizer, kdelibs-bugs-null, sitter
Priority: NOR    
Version First Reported In: 6.12.0   
Target Milestone: ---   
Platform: NixOS   
OS: Linux   
URL: https://github.com/NixOS/nixpkgs/issues/394540
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description ilay-JBR 2025-03-30 08:28:22 UTC 
SUMMARY
I initially created a issue for this in nixpkgs repo, but as far i know it required a patch which not ideal so i thought i would be better if this issue was fixed from the KDE side.
Here is the issue:
https://github.com/NixOS/nixpkgs/issues/394540

-----------------------

When trying to act as administrator in dolphin the following error pops up

Unable to create KIO worker. The KIO worker for protocol “admin” in /nix/store/gjgfsijgsy59gmrb0hgmhwmg33rfqvw4-kio-admin-24.12.3/lib/qt-6/plugins/kf6/kio/admin.so was not loaded because all KIO workers which are located outside of /nix/store/qqcv46w2fyz31zcy4c5gwsxsnhqwvdvq-kio-6.12.0/lib/qt-6/plugins/kf6/kio/ and ask for elevated privileges are considered insecure

STEPS TO REPRODUCE
1. open dolphin
2. click on "view" in the menu bar
3. click on "act as administrator"

SOFTWARE/OS VERSIONS
Operating System: NixOS 25.05
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.12.20 (64-bit)
Graphics Platform: Wayland
Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1650 Ti
Manufacturer: LENOVO
Product Name: 82AU
System Version: Lenovo Legion 5 15IMH05
Comment 1 Harald Sitter 2025-03-31 03:54:21 UTC 
I don't think that is going to change. This constraint was put in place for security hardening.

Moving bug to KIO, that's where the relevant code lives.
Comment 2 John Kizer 2025-04-10 17:33:55 UTC 
Someone else can feel free to correct me if I'm wrong, but this appears to be:

* A NixOS-specific issue
* With a NixOS-specific patch applied downstream...
* ...that override what the Nix folks agree is a reasonable policy on the KDE side

Marking as resolved downstream. Thanks!