Bug 415667 - Dolphin can't display file with up to date KCI unstable: error loading file.so
Summary: Dolphin can't display file with up to date KCI unstable: error loading file.so
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-29 08:24 UTC by Oded Arbel
Modified: 2019-12-30 10:35 UTC (History)
1 user (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Oded Arbel 2019-12-29 08:24:06 UTC 
SUMMARY

Since I updated kio to KCI unstable package 5.65.0+p19.10+git20191227.1259-0, on 2019-12-28, file based views no longer work - for example when starting Dolphin, no files are shown instead a red error message appears on top with the text: 

Unable to create io-slave. klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'.

When opening a file open/save dialog, the same message appears in a pop up.

Looking at .xsession-errors, I have this:

---8<---
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so' from launcher.
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'
Could not open library '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so'.
Cannot load library /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so: (/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/file.so: undefined symbol: _ZN3KIO9SlaveBase25requestPrivilegeOperationERK7QString)
---8<---

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
KDE Plasma Version: 5.17.80
KDE Frameworks Version: 5.66.0
Qt Version: 5.12.4
Comment 1 Oded Arbel 2019-12-30 10:35:47 UTC 
The problem seems to have resolved itself. I'm not sure what happened - there were no additional software updates that seem relevant, but now it seems to be working just fine and there are no errors in .xsession-errors.