I am on KDE Neon 5.14. Using latest versions of KDE connect on Neon and Android.
I am trying to browse my phone file system but getting this error:

Code: Select all

The process for the kdeconnect://92e92185f23aaf5b protocol died unexpectedly

I have made sure KDE connect on android has all permissions and plugin is enabled on both sides.

Here is the output of ~/.xsession-errors when trying this.

Code: Select all

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
KCrash: Application Name =  path =  pid = 13797
KCrash: Arguments: kdeinit5: PID 13797 terminated.
Could not find service for job "Job 13" with app name "org.kde.kdeconnectd"
Could not find service for job "Job 13" with app name "org.kde.kdeconnectd"
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60266, resource id: 100663303, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60267, resource id: 83886155, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60271, resource id: 83886155, major code: 142 (Unknown), minor code: 3
trying to show an empty dialog
trying to show an empty dialog
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60701, resource id: 83886155, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60702, resource id: 83886161, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60703, resource id: 83886173, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60704, resource id: 83886155, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60705, resource id: 83886161, major code: 142 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 2 (BadValue), sequence: 60706, resource id: 83886173, major code: 142 (Unknown), minor code: 3


Thanks. I am new to KDE, if you need any more information please let me know....

I have the very same problem. I was able to browse my android phone from my KDE Neon till the system updates. I have decided to try with a fresh installation (neon-useredition-20181011-0542-amd64.iso) and just after the installation the connection worked regularly. Then I applied the updates (plasma 5.14.0 to plasma 5.14.1) and the browsing became impossible again with the message "The process for the kdeconnect://xxxxxxxxxxxxxx protocol died unexpectedly"

With my update to Kubuntu 18.04 I cannot browse also:


https://www.dropbox.com/s/ae1z8oggrb7yzop/kdeconnect.png?dl=0

This bug nailed me too. It's infuriating. It worked for a while and then it didn't. It works on other YABU distros, just not Neon. Since I only brought a Windows laptop and a Neon desktop with me when traveling to this client location I have a really tough time sending pictures home via email because the desktop is where I do almost everything. At the bottom of this post: https://forum.xda-developers.com/verizon-htc-10/help/file-transfer-linux-t3728269 one can find a lead to the culprit.

Sorry to neglect this thread that I started, but actually the problem turned out to be the mtp version that came with Leap 42.3. Updating this (libmtp9) from version 1.1.13 to 1.1.14 fixed the problem. I can now access internal storage as "read/write".

At least that is what fixed it for SuSE. It "should" fix it for us as well, assuming it can get into the repos.


According to Synaptic we are sitting at a 1.1.13-1 release. Problem should go away once they push 1.1.14-something.