| Summary: | Discover fails to integrate kio-admin (binding mismatch) | ||
|---|---|---|---|
| Product: | [Applications] Discover | Reporter: | proteus5 |
| Component: | discover | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | aleixpol, kdedev, nate |
| Priority: | NOR | ||
| Version First Reported In: | 6.5.3 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Can you clarify what the problem is, exactly? (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. (In reply to Nate Graham from comment #1) > Can you clarify what the problem is, exactly? By "binding the plugin", it's meant the process where Discover matches the plugin’s declared IID against its expected IID to integrate it. Because the plugin declares org.kde.kio.worker.admin while Discover expects org.kde.kio.admin, the binding fails. Technical References
Plugin file: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/admin.so
Declares IID: org.kde.kio.worker.admin
Discover expectation (from debug logs): org.kde.kio.admin
Error message observed: couldn't find QList("org.kde.kio") which is supposedly extended by "org.kde.kio.admin"
Summary
The plugin admin.so is installed and functional, but Discover fails to bind it because of an IID mismatch:
Declared: org.kde.kio.worker.admin (Plugin file: /usr/lib/x86_64-linux-gnu/qt6/plugins/kf6/kio/admin.so)
Expected: org.kde.kio.admin
This discrepancy prevents Discover from integrating kio-admin.
Yeah but what's the user-facing bug? What's not working that you expected to be working? Are you just reporting that there's a warning in the log? Are you using AI to write bug reports or identify bugs? (In reply to Nate Graham from comment #5) > Yeah but what's the user-facing bug? What's not working that you expected to > be working? > > Are you just reporting that there's a warning in the log? > > Are you using AI to write bug reports or identify bugs? Why Discover cannot integrate kio. admin? Of course, I get huge amount of warnings. The system is not clean. Discover doesn't support kio-admin; it doesn't make sense to use it with Discover. So the user-facing problem is that you get warnings in your log, correct? (In reply to Nate Graham from comment #7) > Discover doesn't support kio-admin; it doesn't make sense to use it with > Discover. > > So the user-facing problem is that you get warnings in your log, correct? So, what is the reason Discover interacts with Kio-admin, issuing the warnings? In this case, the warnings are false positive. They aren't warnings, they're debug messages. You've intentionally turned them on. The message is basically saying what I told you: that kio-admin won't be used. There isn't a bug here; everything is working as designed, and there are no user-facing problems. Debug-level logging is intended for use by developers to diagnose problems while programming or troubleshooting. Debug log messages are often not written to be understood by users, and can be terse or confusing. So I wouldn't recommend turning on debug logging and then trawling through the log looking for things that look suspicious. You'll find 500,000 things and go mad! |
The kio-admin plugin is installed and works in Dolphin (admin://). However, Discover fails to integrate it and logs: couldn't find QList("org.kde.kio") which is supposedly extended by "org.kde.kio.admin" Debug output shows: admin.so is loaded and recognized (supports protocols QList("admin")). Plugin metadata: IID: org.kde.kio.worker.admin. Discover expects: org.kde.kio.admin. This mismatch prevents Discover from binding the plugin. Steps to Reproduce: Steps to Reproduce: QT_LOGGING_RULES="*.debug=true" plasma-discover | grep -E "kio|admin" Observe error message above. Expected Result Discover should recognize and integrate kio-admin. Actual Result Discover fails with binding mismatch error.