Bug 438981

Summary: kio-gdrive no longer works (Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so)
Product: [Frameworks and Libraries] kio-gdrive Reporter: Justin <kdebugs.cmrck>
Component: generalAssignee: Elvis Angelaccio <elvis.angelaccio>
Status: RESOLVED FIXED    
Severity: normal CC: alex_jame_mick, kinofhek, omeritzicschwartz, rikmills, rjvbertin
Priority: NOR    
Version First Reported In: 21.04.2   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: crash

Description Justin 2021-06-21 07:41:16 UTC
SUMMARY
gdrive no longer works (after upgrade to 21..04 backports?)


STEPS TO REPRODUCE
1. Open Google Drive in Dolphin
2. Get message: Unable to create io-slave. klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so'.


OBSERVED RESULT
Paste in Konsole:
/usr/lib64/qt5/plugins/kf5/kio/gdrive.so \
bash: /usr/lib64/qt5/plugins/kf5/kio/gdrive.so: No such file or directory

EXPECTED RESULT
Go to Google Drive in Dolphin
See files


SOFTWARE/OS VERSIONS
Operating System: Kubuntu 21.04

KDE Plasma Version: 5.22.1

KDE Frameworks Version: 5.83.0

Qt Version: 5.15.2

Kernel Version: 5.11.0-18-generic (64-bit)

Graphics Platform: X11

Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz

Memory: 15.5 GiB of RAM

Graphics Processor: Mesa Intel® UHD Graphics 620 

ADDITIONAL INFORMATION
Re-installing Kio-gdrive does not solve the issue.
Purging and re-installing Kio-gdrive does not solve the issue.
Comment 1 Felipe Kinoshita 2021-06-22 06:04:16 UTC
Cannot reproduce.
Comment 2 Justin 2021-06-22 12:33:13 UTC
More info for what it is worth!

sudo kioclient5 exec gdrive:/            [sudo] password for justin:  \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/libexec/kf5/klauncher' \
kdeinit5: Launched KLauncher, pid = 5707, result = 0 \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) \
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' \
kdeinit5: opened connection to :0 \
kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so' from launcher. \
kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/gdrive.so' \
kdeinit5: (gdrive.so ) Pipe closed unexpectedlykdeinit5: Pipe closed unexpectedly: Resource temporarily unavail\
able \
kdeinit5: PID 5711 terminated. \
kf.kio.core: couldn't create slave: "klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/k\
io/gdrive.so'." \
kf.notifications: Failed to play sound with canberra: Not available\
Comment 3 RJVB 2021-07-08 10:18:47 UTC
I think you'll need to restart kdeinit5.

> pkill -f kdeinit5

should be enough, but after an update that involves the KF5 frameworks and/or Plasma components, or just a kioslave it is not a bad idea to log off and back in again (or even reboot the machine).

Did you do that?



I'm more curious to know if you were still allowed access to your gdrive before the update!?
Comment 4 Omeritzics 2021-07-08 14:09:25 UTC
(In reply to RJVB from comment #3)
> I think you'll need to restart kdeinit5.
> 
> > pkill -f kdeinit5
> 
> should be enough, but after an update that involves the KF5 frameworks
> and/or Plasma components, or just a kioslave it is not a bad idea to log off
> and back in again (or even reboot the machine).
> 
> Did you do that?
> 
> 
> 
> I'm more curious to know if you were still allowed access to your gdrive
> before the update!?

Restarting kioslave nor logging off and back in again do not solve the problem.
gdrive does not work correctly only since the update to version 21.04.
Comment 5 Justin 2021-07-17 10:32:36 UTC
I recently borked the OS and had to re-install.
On a fresh unadulterated install of Kubuntu 21.04 the problem still persists.
Comment 6 Rik Mills 2021-08-02 11:41:19 UTC
*** Bug 424630 has been marked as a duplicate of this bug. ***
Comment 7 Rik Mills 2021-08-02 11:46:03 UTC
Created attachment 140463 [details]
crash

Seeing this in 21.10 with a crash in libKPimGAPIDrive.so.5.17.80
Comment 8 Rik Mills 2021-08-02 17:21:48 UTC
At least in Ubuntu, as per bug #411425 this seems to be a result of building with LTO enabled.
Comment 9 Rik Mills 2021-08-02 19:38:20 UTC
Should now be fixed in backports
Comment 10 Omeritzics 2021-08-03 15:57:44 UTC
(In reply to Rik Mills from comment #9)
> Should now be fixed in backports

Now it is fixed. Thank you!
Comment 11 Omeritzics 2021-08-03 15:57:56 UTC
(In reply to Rik Mills from comment #9)
> Should now be fixed in backports

Now it is fixed. Thank you!