Bug 1311635 - Unable to create io slave: klauncher said: Error loading /usr/lib64/qt5/plugins/kf5/kio/desktop.so
Summary: Unable to create io slave: klauncher said: Error loading /usr/lib64/qt5/plugi...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: qt-5.6
TreeView+ depends on / blocked
 
Reported: 2016-02-24 16:16 UTC by Rex Dieter
Modified: 2016-09-22 06:11 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-16 12:34:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 360217 0 NOR RESOLVED Unable to create io-slave: klauncher said: Error loading .../desktop.so , since upgade to Qt-5.6.0-rc 2021-01-21 19:03:40 UTC

Description Rex Dieter 2016-02-24 16:16:00 UTC 
Testing current Qt (5.6.0-rc) copr,
https://copr.fedorainfracloud.org/coprs/g/kdesig/Qt5/

plasmashell desktop containment fails to load with error:
Unable to create io slave: klauncher said: Error loading /usr/lib64/qt5/plugins/kf5/kio/desktop.so

reproducible trying desktop:/ url in dolphin too.
Comment 1 Rex Dieter 2016-02-24 16:17:06 UTC 
Fwiw, this problem seems new since -rc landed, -beta builds were fine in this regard
Comment 2 Rex Dieter 2016-03-07 17:16:55 UTC 
Pushed upstream to:
https://bugs.kde.org/show_bug.cgi?id=360217

After confirming problem still happens with latest plasma/Qt-5.6 builds
Comment 3 Rex Dieter 2016-03-07 17:27:24 UTC 
Oh yay, seems problem solved after clearing
~/.cache/ 
content

Now I wish I'd been more careful, to see what exactly it was.
Comment 4 Michael Hofer 2016-09-22 06:11:06 UTC 
I have this issue since more than a month now. Can you please give a hint how to find the reason for this? Clearing ~/.cache/ did not help.
Note You need to log in before you can comment on or make changes to this bug.