[opensuse-factory] kio-gdrive - Google Drive KIO slave for KDE applications not working any more
hi, since latest update to KDE frameworks 5.60.0 and KDE applications 19.07.80 kio-gdrive (Google Drive KIO slave for KDE applications) does not work anymore. dolphin reports error loading /usr/lib64/qt5/plugins/kf5/kio/gdrive.so when i do kioclient5 exec gdrive:/ in commandline, i receive the following error: kf5.kio.core: couldn't create slave: "klauncher said: Fehler beim Laden von „/usr/lib64/qt5/plugins/kf5/kio/gdrive.so“" kf5.kio.widgets: KRun(0x55be0aa4ca50) ERROR 173 "Unable to create io-slave. klauncher said: Fehler beim Laden von „/usr/lib64/qt5/plugins/kf5/kio/gdrive.so“" as root in commandline, i receive the following error: kdeinit5: (gdrive.so ) Pipe closed unexpectedlykdeinit5: Pipe closed unexpectedly: Resource temporarily unavailable kf5.kio.core: couldn't create slave: "klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/gdrive.so'." kf5.kio.widgets: KRun(0x563b8a349610) ERROR 173 "Unable to create io-slave. klauncher said: Error loading '/usr/lib64/qt5/plugins/kf5/kio/gdrive.so'." i use kio-gdrive, version 1.2.6-44.1, from KDE:Extra repo, and kio, version 5.60.0-261.4, from KDE:Frameworks5 repo. i already tried downgrading to the versions from default tumbleweed repo, but that didn't solve it. i didn't find any bug-report in https://bugzilla.opensuse.org about it. does anyone experience the same, or knows a solution? -- Best Regards Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Develop -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Dienstag, 6. August 2019, 14:46:46 schrieb Rainer Klier:
since latest update to KDE frameworks 5.60.0 and KDE applications 19.07.80 kio-gdrive (Google Drive KIO slave for KDE applications) does not work anymore.
The reason is simple: KDE Applications 19.07.80 (which is 19.08 beta) is a new feature version, and libkgapi had some incompatible changes. kio-gdrive would need to be rebuilt against the latest version, but the one from Tumbleweed (and also KDE:Extra) is built against the version from Tumbleweed which is the last stable release, 19.04.3.
i already tried downgrading to the versions from default tumbleweed repo, but that didn't solve it.
You'd need to downgrade the libKPimGAPI* packages to the versions from the main Tumbleweed repo, and kio-gdrive should work again. And actually I'd recommend to remove KDE:Applications and KDE:Frameworks5 completely. The main point of Tumbleweed is that you get the latest (stable) versions in the standard repos, and do *not* have to add devel repos for newer packages (which are even untested). Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hallo, Am 06.08.19 um 20:02 schrieb Wolfgang Bauer:
Am Dienstag, 6. August 2019, 14:46:46 schrieb Rainer Klier:
since latest update to KDE frameworks 5.60.0 and KDE applications 19.07.80 kio-gdrive (Google Drive KIO slave for KDE applications) does not work anymore. The reason is simple: KDE Applications 19.07.80 (which is 19.08 beta) is a new feature version, and libkgapi had some incompatible changes.
kio-gdrive would need to be rebuilt against the latest version, but the one from Tumbleweed (and also KDE:Extra) is built against the version from Tumbleweed which is the last stable release, 19.04.3.
ah, ok, this explains everything. thank you very much.
i already tried downgrading to the versions from default tumbleweed repo, but that didn't solve it. You'd need to downgrade the libKPimGAPI* packages to the versions from the main Tumbleweed repo, and kio-gdrive should work again.
danke! that worked!
And actually I'd recommend to remove KDE:Applications and KDE:Frameworks5 completely. The main point of Tumbleweed is that you get the latest (stable) versions in the standard repos, and do *not* have to add devel repos for newer packages (which are even untested).
yes, you are right. i already thought about disabling KDE:/Applications, KDE:/Extra, KDE:/Frameworks5, KDE:/Qt5 and KDE:/Distro.... -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mittwoch, 7. August 2019, 13:36:56 schrieb Rainer Klier:
i already thought about disabling KDE:/Applications, KDE:/Extra, KDE:/Frameworks5, KDE:/Qt5 and KDE:/Distro.... I think I should add some things here:
KDE:Extra by itself actually should be rather safe to use, as it is built against standard Tumbleweed (that actually caused the problem you had). The updates there are also submitted to Factory/Tumbleweed (it is a devel project after all), so you'll get them in the standard repos too after some time. But, it does also contain packages that are not in Factory/Tumbleweed (yet?) for whatever reason. If you use some of those, you better don't remove the repo of course... ;-) The most "problematic" here are KDE:Qt5, KDE:Frameworks5, and KDE:Applications. The latter two also get beta versions (mainly to increase the chance to catch bugs before the release, and also formal issues to have the releases be accepted to Tumbleweed as soon as possible). And updating Qt5 before all the rest can cause dependency problems by itself. KDE:Distro:Factory is being faded out anyway, because it was/is the devel project for KDE4 stuff (that's being dropped). BTW, we added a strict dependency to kio-gdrive now, to avoid the exact same problem you had in the future (there also actually was no guarantee that it would actually get rebuilt in Factory when necessary, so this could have happened in Tumbleweed alone too). https://build.opensuse.org/request/show/724816 Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hi, Am 22.08.19 um 19:27 schrieb Wolfgang Bauer:
Am Mittwoch, 7. August 2019, 13:36:56 schrieb Rainer Klier:
i already thought about disabling KDE:/Applications, KDE:/Extra, KDE:/Frameworks5, KDE:/Qt5 and KDE:/Distro.... I think I should add some things here:
KDE:Extra by itself actually should be rather safe to use, as it is built against standard Tumbleweed (that actually caused the problem you had).
ok, great.
The most "problematic" here are KDE:Qt5, KDE:Frameworks5, and KDE:Applications. The latter two also get beta versions (mainly to increase the chance to catch bugs before the release, and also formal issues to have the releases be accepted to Tumbleweed as soon as possible). And updating Qt5 before all the rest can cause dependency problems by itself.
BTW, we added a strict dependency to kio-gdrive now, to avoid the exact same problem you had in the future (there also actually was no guarantee that it
ok. understood. but if i have those repos (qt, frameworks5, applications) enabled, i am able to easily see, there are new KDE packages, and update ONLY KDE stuff, without anything else. i can see, if new KDE stuff is available, and update to it. and i also can downgrade only KDE stuff, if necessary. if i would use all KDE packages only from main tumbleweed repo, where the KDE packages are spread all over the repo, next to all the other tumbleweed packages, i can't easily pick all the KDE packages. in this case i am forced to do a "zypper dup", or "zypper up", and this would update all packages from tumbleweed repo, even those, where nothing really new is available, but packages have a higher build number. it would then update many many packages, without something new, only because they have higher build number. but with the KDE repos available, i can see, that a new KDE version (of applications or frameworks) is availbale, and can decide to update to it, and only update KDE packages. similar to the other repos, where some packages like libreoffice, firefox, thunderbird are maintained. here, i am also able to see, that, for example, a new thunderbird version is available, and i am able to ONLY update the thunderbird packages. for that reason, i use those extra repos, next to the main tumbleweed repo. i don't want to do a "zypper dup" every second day, only to get latest firefox, KDE, thunderbird,... thank you very much! -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Sonntag, 25. August 2019, 21:48:43 CEST schrieb Rainer Klier:
hi,
Am 22.08.19 um 19:27 schrieb Wolfgang Bauer:
Am Mittwoch, 7. August 2019, 13:36:56 schrieb Rainer Klier:
i already thought about disabling KDE:/Applications, KDE:/Extra, KDE:/Frameworks5, KDE:/Qt5 and KDE:/Distro....
I think I should add some things here:
KDE:Extra by itself actually should be rather safe to use, as it is built against standard Tumbleweed (that actually caused the problem you had).
ok, great.
The most "problematic" here are KDE:Qt5, KDE:Frameworks5, and KDE:Applications. The latter two also get beta versions (mainly to increase the chance to catch bugs before the release, and also formal issues to have the releases be accepted to Tumbleweed as soon as possible). And updating Qt5 before all the rest can cause dependency problems by itself. ok. understood.
but if i have those repos (qt, frameworks5, applications) enabled, i am able to easily see, there are new KDE packages, and update ONLY KDE stuff, without anything else.
i can see, if new KDE stuff is available, and update to it. and i also can downgrade only KDE stuff, if necessary.
if i would use all KDE packages only from main tumbleweed repo, where the KDE packages are spread all over the repo, next to all the other tumbleweed packages, i can't easily pick all the KDE packages. in this case i am forced to do a "zypper dup", or "zypper up", and this would update all packages from tumbleweed repo, even those, where nothing really new is available, but packages have a higher build number.
it would then update many many packages, without something new, only because they have higher build number.
but with the KDE repos available, i can see, that a new KDE version (of applications or frameworks) is availbale, and can decide to update to it, and only update KDE packages.
similar to the other repos, where some packages like libreoffice, firefox, thunderbird are maintained.
here, i am also able to see, that, for example, a new thunderbird version is available, and i am able to ONLY update the thunderbird packages.
for that reason, i use those extra repos, next to the main tumbleweed repo.
BTW, we added a strict dependency to kio-gdrive now, to avoid the exact same problem you had in the future (there also actually was no guarantee that it
i don't want to do a "zypper dup" every second day, only to get latest firefox, KDE, thunderbird,... thank you very much!
Well, Rainer, with all due respect, but you're misusing Tumbleweed that way. By using the packages from devel projects, you might get some, that aren't fully stabilized and tested. The idea of Tumbleweed is to keep current with *tested* packages, that are also *coherent* to each other. The way, you seem to using it, is selectively choosing packages, that you're interested in. May be, you think, that the other updated packages are just spurious builds without any addition value, or whatever.. Tumbleweed makes great effort to reduce spurious builds (reproducible build initiative), and while you might be able to replace just the elements, that you care about, you're completely on your own, and touch unsafe grounds, because nobody ever tested your combination of packages, and that's the point, where my rule of thumb comes in: Untested things do NOT work! Additionally, the builds are improved continuously (build tools, parameter, e.g. LTO), so the net result of any new TW build is mostly different. Here's, where openQA chimes in: it allows the developers to detect regressions, which mostly saves our asses, and makes Tumbleweed different to other rolling releases. I'm just a humble Tumbleweed user, and please somebody correct me, if I'm wrong, but you ought to "zypper dup" every now and then, and add packages from additional sources very carefully, only. If you mix different sources, you should study their inter-dependencies thoroughly. If you're interested in a single package (or a few), I would recommend to branch and build it in your OBS home, and use current Tumbleweed for the rest. That way, you and others are able to reproduce your setup. Cheers, Pete -- Doing funny thing with SuSE since about 25 years... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hi, Am 22.08.19 um 19:27 schrieb Wolfgang Bauer:
Am Mittwoch, 7. August 2019, 13:36:56 schrieb Rainer Klier:
i already thought about disabling KDE:/Applications, KDE:/Extra, KDE:/Frameworks5, KDE:/Qt5 and KDE:/Distro.... I think I should add some things here:
BTW, we added a strict dependency to kio-gdrive now, to avoid the exact same problem you had in the future (there also actually was no guarantee that it would actually get rebuilt in Factory when necessary, so this could have happened in Tumbleweed alone too). https://build.opensuse.org/request/show/724816
today i updated to kio-gdrive version 1.2.7-48.1 from KDE:extra and it does not work again. and today there are only 19.08.0 versions from libKPimGAPI* packages available, in tumbleweed repo as well as in KDE:applications repo. so there is no downgrading of libKPimGAPI packages possible any more. and also downgrading kio-gdrive to version 1.2.6-3.1 from tumbleweed repo does not work. so currently no combination of kio-gdrive and the libKPimGAPI packages works. did i miss something? -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hi, Am 22.08.19 um 19:27 schrieb Wolfgang Bauer:
Am Mittwoch, 7. August 2019, 13:36:56 schrieb Rainer Klier:
i already thought about disabling KDE:/Applications, KDE:/Extra, KDE:/Frameworks5, KDE:/Qt5 and KDE:/Distro.... I think I should add some things here:
BTW, we added a strict dependency to kio-gdrive now, to avoid the exact same problem you had in the future (there also actually was no guarantee that it would actually get rebuilt in Factory when necessary, so this could have happened in Tumbleweed alone too). https://build.opensuse.org/request/show/724816
more info on todays crash. i found the following in dmesg output: [ 127.231849] gdrive.so[18477]: segfault at 0 ip 00007fabfe1b1890 sp 00007fffa014b228 error 4 in libKPimGAPIDrive.so.5.12.0[7fabfe179000+3e000] -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag, 26. August 2019, 10:41:56 schrieb Rainer Klier:
more info on todays crash.
i found the following in dmesg output:
[ 127.231849] gdrive.so[18477]: segfault at 0 ip 00007fabfe1b1890 sp 00007fffa014b228 error 4 in libKPimGAPIDrive.so.5.12.0[7fabfe179000+3e000]
Hm, that seems to be a different problem though, apparently in libkgapi. Did you fully update your system? Did you reboot since updating? Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 26.08.19 um 11:11 schrieb Wolfgang Bauer:
Am Montag, 26. August 2019, 10:41:56 schrieb Rainer Klier:
more info on todays crash.
i found the following in dmesg output:
[ 127.231849] gdrive.so[18477]: segfault at 0 ip 00007fabfe1b1890 sp 00007fffa014b228 error 4 in libKPimGAPIDrive.so.5.12.0[7fabfe179000+3e000] Hm, that seems to be a different problem though, apparently in libkgapi.
Did you fully update your system?
i did not a zypper dup/up. i installed packages from KDE:extra and tried the libKPimGAPI packages from KDE:Applications repo and from default tumbleweed repo. and i installed all packages from KDE:/Applications and KDE:/Frameworks5 (yes, i know this is not recommended, but this way i was able to update only the KDE packages)
Did you reboot since updating?
yes, i did this as well. -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag, 26. August 2019, 11:36:30 schrieb Rainer Klier:
Am 26.08.19 um 11:11 schrieb Wolfgang Bauer:
Did you fully update your system?
i did not a zypper dup/up.
i installed packages from KDE:extra and tried the libKPimGAPI packages from KDE:Applications repo and from default tumbleweed repo.
and i installed all packages from KDE:/Applications and KDE:/Frameworks5
(yes, i know this is not recommended, but this way i was able to update only the KDE packages)
Well, doing partial updates is not/cannot be supported really, and might cause strange problems indeed. So I would recommend to do a full update (i.e. zypper dup) to rule out some incompatibility caused by that. Ideally without extra repos, but KDE:Applications and KDE:Frameworks5 (and also KDE:Qt5) should be basically the same as standard Tumbleweed at the moment, so they are likely not causing the problem I think. Another thing I would try is to run dolphin in a terminal window (konsole e.g.), maybe there's some helpful output. Also, is the crash backtrace listed by coredumpctl? That would at least show where it is crashing exactly. FWIW, I gave kio-gdrive a quick test here (Leap 15.1 plus the additional KDE repos). It showed an error message that no account is configured (which is true), but didn't crash. Might not necessarily mean much though, as the crash could be later... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mon, 26 Aug 2019 12:09:27 +0200, schrieb Wolfgang Bauer <wbauer@tmo.at>:
FWIW, I gave kio-gdrive a quick test here (Leap 15.1 plus the additional KDE repos). It showed an error message that no account is configured (which is true), but didn't crash. Might not necessarily mean much though, as the crash could be later...
As I do have a Google Account (just never used Google Drive so far), I downloaded the latest Tumbleweed KDE LiveCD and gave it a try. It does crash here as well, while kio-gdrive-1.2.7 (the package from KDE:Extra, self-built against libkgapi-19.08.0 from KDE:Applications) works fine on my Leap 15.1 system. I'll try to find out what the problem is. (kio-gdrive is built against libkgapi-19.08.0 according to the build log...) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Mon, 26 Aug 2019 12:41:17 +0000 schrieb Wolfgang Bauer <wbauer@tmo.at>:
I'll try to find out what the problem is. (kio-gdrive is built against libkgapi-19.08.0 according to the build log...)
The crash seems to be triggered by LTO (Link Time Optimization) that got globally enabled in Tumbleweed recently. I rebuilt libkgapi without LTO, and the problem was fixed (a rebuild alone did not help). If you need it urgently, try to install libKPimGAPICore5 and libKPimGAPIDrive5 from here: https://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Ex... Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 26.08.19 um 15:58 schrieb Wolfgang Bauer:
Am Mon, 26 Aug 2019 12:41:17 +0000 schrieb Wolfgang Bauer <wbauer@tmo.at>:
I'll try to find out what the problem is. (kio-gdrive is built against libkgapi-19.08.0 according to the build log...) The crash seems to be triggered by LTO (Link Time Optimization) that got globally enabled in Tumbleweed recently. I rebuilt libkgapi without LTO, and the problem was fixed (a rebuild alone did not help).
If you need it urgently, try to install libKPimGAPICore5 and libKPimGAPIDrive5 from here: https://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Ex...
this immediatelly worked! thank you very much! :-D will those new packages appear in kde:applications and/or in tumbleweed repo as well? i was sure, it had something to do with libKPimGAPICore5 and libKPimGAPIDrive5 and not because my system was not "zypper dup"ed... ;-) thanks again! p.s.: wolfgang, from your email adress i can derive that you are from austria. am i right? -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag, 26. August 2019, 16:47:18 schrieb Rainer Klier:
will those new packages appear in kde:applications and/or in tumbleweed repo as well?
Well, disabling LTO is rather a workaround most of the time, it would be better to actually find and fix the real problem. In this case it turned out to be quite hard to debug though: http://bugzilla.opensuse.org/show_bug.cgi?id=1148217 So the "fix" with LTO disabled is in KDE:Applications already meanwhile, and has been forwarded to Factory: https://build.opensuse.org/request/show/726785 Should be in one of the next snapshots, I think.
p.s.: wolfgang, from your email adress i can derive that you are from austria.
am i right?
Yes. ;-) Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
hi, Am 29.08.19 um 19:28 schrieb Wolfgang Bauer:
Am Montag, 26. August 2019, 16:47:18 schrieb Rainer Klier:
will those new packages appear in kde:applications and/or in tumbleweed repo as well?
In this case it turned out to be quite hard to debug though: http://bugzilla.opensuse.org/show_bug.cgi?id=1148217
whow! (bist du deppert? ;-) what an immense amount of working/debugging... thanks for the hard work. and i am glad, it was not an issue from me, because of not having updated the full system.....
So the "fix" with LTO disabled is in KDE:Applications already meanwhile, and has been forwarded to Factory: https://build.opensuse.org/request/show/726785
Should be in one of the next snapshots, I think.
thanks again.
p.s.: wolfgang, from your email adress i can derive that you are from austria.
am i right? Yes. ;-)
hahaha, von wo? -- Best Regards | Freundliche Grüße | Cordialement | Cordiali Saluti | Atenciosamente | Saludos Cordiales *DI Rainer Klier* DevOps, Research & Development -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Donnerstag, 29. August 2019, 22:21:17 schrieb Rainer Klier:
whow! (bist du deppert? ;-)
what an immense amount of working/debugging...
Yeah, but at least there has been some clue on what's going wrong in the end. ;-) Btw, the workaround (with disabling LTO) is finally in Tumbleweed now, together with 19.08.1: ==== libkgapi ==== Version update (19.08.0 -> 19.08.1) Subpackages: libKPimGAPICalendar5 libKPimGAPIContacts5 libKPimGAPICore5 libKPimGAPITasks5 libkgapi-lang sasl2-kdexoauth2 - Update to 19.08.1 * New bugfix release * For more details please see: * https://www.kde.org/announcements/announce-applications-19.08.1.php - Changes since 19.08.0: * Include KDE* cmake macros before any others - Temporarily disable LTO to avoid crash when using gdrive (boo#1148217)
p.s.: wolfgang, from your email adress i can derive that you are from austria.
am i right?
Yes. ;-)
hahaha, von wo?
Eisenstadt. Kind Regards, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Hans-Peter Jansen -
Rainer Klier -
Wolfgang Bauer