https://bugs.kde.org/show_bug.cgi?id=513101
--- Comment #2 from [email protected] --- (In reply to Nate Graham from comment #1) > Can you clarify what the problem is, exactly? Cause The kio-admin worker declares its plugin metadata as: IID: org.kde.kio.worker.admin Protocols: QList("admin") Discover expects an extension of org.kde.kio with IID org.kde.kio.admin. This mismatch prevents Discover from binding the plugin. Effect Dolphin: works correctly with admin:// because it directly invokes the protocol. Discover: fails to integrate the plugin, logging an error instead of recognizing kio-admin. Error observed Code " couldn't find QList("org.kde.kio") which is supposedly extended by "org.kde.kio.admin" " Diagnostic steps Ran Discover with full debug logging: bash QT_LOGGING_RULES="*.debug=true" plasma-discover | grep -E "kio|admin" Confirmed that admin.so was loaded and recognized, supporting protocol admin. Inspected plugin metadata: IID = org.kde.kio.worker.admin. Compared against Discover’s expectation (org.kde.kio.admin) and identified the mismatch as the root cause. Conclusion The issue is not with the functionality of the worker itself (Dolphin proves it works), but with Discover’s binding logic. The inconsistent naming between the plugin’s declared IID and Discover’s expected IID causes the integration failure. Consistency across KDE apps Dolphin already supports admin:// via kio‑admin, but Discover fails due to the IID mismatch. Fixing this ensures consistent behavior across KDE applications that rely on KIO workers. User experience Without the fix, users see confusing error logs and Discover cannot leverage kio‑admin. This creates a fragmented experience: one KDE app works, another does not, even though both rely on the same worker. -- You are receiving this mail because: You are watching all bug changes.
