Bug 411082 - Unable to create io-slave. klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so'.
Summary: Unable to create io-slave. klauncher said: Error loading '/usr/lib/x86_64-lin...
Status: RESOLVED FIXED
Alias: None
Product: kio-gdrive
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 1.2.6
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords:
: 411628 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-08-20 00:00 UTC by Lê Hoàng Phương
Modified: 2019-09-09 22:41 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 1.2.7
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lê Hoàng Phương 2019-08-20 00:00:08 UTC
SUMMARY

Latest kio-gdrive (1.2.6) in KDE Neon doesn't work unfortunately. 

STEPS TO REPRODUCE

1. Go to Network > Google Drive

OBSERVED RESULT

Dolphin shows following error:

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


EXPECTED RESULT

There should be no error. Everything works as it should.


SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.12.3
Kernel Version: 5.0.0-23-generic
OS Type: 64-bit


ADDITIONAL INFORMATION
Comment 1 Lê Hoàng Phương 2019-08-20 00:19:50 UTC
Several people seem to have the same problem.

https://forum.kde.org/viewtopic.php?f=309&t=160338&p=421271
Comment 2 Christoph Feck 2019-08-20 21:50:50 UTC
According to bug 410766, the "kio-gdrive" package needs to be rebuilt because of ABI changes in KDEPIM.
Comment 3 Elvis Angelaccio 2019-08-24 16:57:17 UTC
Actually, it's not just an ABI change. libkgapi 19.08 changed the API, which required a change in kio-gdrive as well: https://commits.kde.org/kio-gdrive/b11f84baadc3856b3855bc278035cf242f416396
Comment 4 Elvis Angelaccio 2019-09-09 22:41:26 UTC
*** Bug 411628 has been marked as a duplicate of this bug. ***