Registered Member
|
It was possible to browse android devices via kdeconnect till KDE Neon updates. After the update, trying to open the folders on android, dolphin does not start and it is shown a message that say the the process for the kdeconnect protocol died unexpectedly. All the others kdeconnect functions seems to work correctly. I re-installed KDE Neon with the latest iso; the connection worked with plasma 5.14.0 till I applied the system updates to plasma 5.14.1. I installed Kubuntu 18.10 and via backports repository I updated it to plasma 5.14.1 and with Kubuntu the android browsing is still working.
Thank you in advance for any eventual advice. |
Registered Member
|
Did you do anything with on the phone side of things? Have you tried unparing the two, from the phone as well as the computer?
I have see this happen on occasion over the years after a kdeconnect update, and usually doing this has fixed it for me.
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
Registered Member
|
Yes of course I did several attempts. Unpairing did not solve the problem. I made a few of fresh installation of KDE Neon pairing with the phone just after the installation (ok till updates) and pairing only after applying the updates; same result, when KDE Neon is updated browsing android is not possible. Thank you for your reply. |
Registered Member
|
after update to 5.14.1
------------------ .xsesson-errors kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_kdeconnect.so' QCoreApplication::arguments: Please instantiate the QApplication object first QCoreApplication::applicationDirPath: Please instantiate the QApplication object first QCoreApplication::applicationFilePath: Please instantiate the QApplication object first QCoreApplication::arguments: Please instantiate the QApplication object first KCrash: crashing... crashRecursionCounter = 2 ---------------- krusider turning open archive ------------- kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_krarc.so' from launcher. kdeinit5: preparing to launch '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_krarc.so' QCoreApplication::arguments: Please instantiate the QApplication object first QCoreApplication::applicationDirPath: Please instantiate the QApplication object first QCoreApplication::applicationFilePath: Please instantiate the QApplication object first QCoreApplication::arguments: Please instantiate the QApplication object first KCrash: crashing... crashRecursionCounter = 2 ------------ |
Registered Member
|
Having exactly the same issue as OP.
And this guy has it too: https://unix.stackexchange.com/questions/476843/unable-to-browse-my-android-phone-via-kde-connect-in-kde-neon This is a bit annoying because I do my phone backup routine via KDEconnect I'm using KDE Neon 5.14.1 KDE Frameworks 5.51.0 My phone (Huawei Mate 9) has Android 8.0.0. (didnt change the past months) |
Registered Member
|
I can recreate the problem. I'm a bit mystified by it as it seems to work fine on developer stable edition so it is an issue with the kdeconnect kioslave interacting with some other package. I'll keep investigating.
|
Registered Member
|
On a related note, there has been a recent update of the KDE Connect app from Google Play. Now I can no longer browse the files on my phone on Ubuntu 16.04.5 AND Kubuntu 18.04.1 (not KDE Neon), either. Keeps complaining about the file doesn't exist whenever I double click on the directory. I don't think KDE Connect was actually updated on the PC side. Is there any bug report/solution for this?
|
Registered Member
|
What I can tell is that using the dev edition solved the problems I mentioned here : viewtopic.php?f=309&t=155624 Thanks for the interest. SM |
Registered Member
|
A new release of kdeconnect has been made which is now in KDE neon which should fix browsing with the kdeconnect:/ ioslave
|
Registered Member
|
A KDEconnect update on the computer, a reinstallation of the phone app and repairing fixed it and I can now backup files again
Thank you |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell, Yahoo [Bot]