Bug 373967 - Android File System not Mounted and Pairing is no longer persistent.
Summary: Android File System not Mounted and Pairing is no longer persistent.
Status: RESOLVED FIXED
Alias: None
Product: kdeconnect
Classification: Applications
Component: android-application (show other bugs)
Version: 1.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-20 17:53 UTC by Michael Tunnell
Modified: 2017-11-03 08:53 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Tunnell 2016-12-20 17:53:57 UTC
My Devices Setup:

Motorola Nexus 6
Android: 6.0.1
KDE Neon: with Plasma 5.8.4

KDE Connect (Linux): 1.0.1
KDE Connect (Android): 1.5

------------------

I have been having many issues with my KDE Connect Android app since the recent update a few days ago.


1. The Android app loses the pairing and everything stops working very quickly, whether I move away from the app in the foreground or not.

2. During the short time period of being paired, I can send files, remote input, and multimedia control.

3. I am unable able mount the Android filesystem at any time.

4. I am unable to sync the clipboard at any time.

5. During the short paired time, the android filesystem is never available in Dolphin.

6. During the short paired time, when attempting to launch the android filesystem from the system tray widget I receive the following error. "A folder named /home/michael/.cache/kioexec/krun/4394_0/ already exists."

------

I have been using KDE Connect for well over a year now and I freaking love it but since December 17, it just stopped working.
5.
Comment 1 Michael Tunnell 2016-12-24 18:43:06 UTC
I solved the problem. This was a permissions issue with ~/.local/share/user-places.xbel having ownership to root somehow instead of my user. I don't know how that happened but once I switched it to my user it started working again.
Comment 2 Rasmus B 2017-01-05 20:29:14 UTC
I'm experiencing the same thing with the filesystem - however, my permissions are correctly set. Trying to mount the filesystem i get an "Error - Kioexec" dialog with the text: "A folder named /home/user/.cache/kioexec/krun/9363_0/ already exists."

Hade stable version first and changed to kdeconnect-git r1551.82ca0b4-1 to try if that helped, but no change. Using Arch Linux and running the mobile app version 1.5 on a Samsung Galaxy S7. 

Any ideas?
Regards,

Rasmus
Comment 3 NginUS 2017-02-13 00:48:02 UTC
I'm using kdeconnect 1.0.3-0ubuntu1~ubuntu16.04~ppa1 with an LG Stylo2 running KDE Connect version 1.5. When I click the 'Browse this device' button in the plasma widget I get the following error:

"A folder named /home/user/.cache/kioexec/krun/15934_0/ already exists."

The user-places.xbel file's permissions are user's.

AFAIK pairing doesn't fail after awhile.
Comment 4 Albert Vaca Cintora 2017-02-13 20:45:11 UTC
That's likely because you ran dolphin as root and it created files on your .cache directory, that you don't have permissions to change now. Delete .cache and it should get fixed. It's better if you first make sure all files under your home dir belong to you.
Comment 5 Michael Tunnell 2017-02-14 01:47:11 UTC
> That's likely because you ran dolphin as root and it created files on your .cache directory

I did totally open it as root previously. It wasn't .cache that had weird permissions but rather it was "~/.config/kdeconnect/config". I renamed the folder for regenerating the folder and it seems to have worked. I then deleted the other older folder and will provide updates to whether this solved it or not. (so far it seems fixed)
Comment 6 Rasmus B 2017-02-14 08:28:36 UTC
Tried everything suggested in this thread. All permissions mentioned are mine. Tried deleteing both .config/kdeconnect and .cache and re-pairing. However, the error still persists: "A folder named .cache/kioexec/krun/[random numbers] already exists".

More ideas? :)
Thanks / Raz
Comment 7 NginUS 2017-02-15 00:52:58 UTC
(In reply to Albert Vaca from comment #4)
> That's likely because you ran dolphin as root and it created files on your
> .cache directory, that you don't have permissions to change now. Delete
> .cache and it should get fixed. It's better if you first make sure all files
> under your home dir belong to you.

Ran #chown -R username:username /home/username/, then deleted /home/username/.cache but the issue persists.

Please advise.
Comment 8 NginUS 2017-02-15 00:53:27 UTC
(In reply to Michael Tunnell from comment #5)
> > That's likely because you ran dolphin as root and it created files on your .cache directory
> 
> I did totally open it as root previously. It wasn't .cache that had weird
> permissions but rather it was "~/.config/kdeconnect/config". I renamed the
> folder for regenerating the folder and it seems to have worked. I then
> deleted the other older folder and will provide updates to whether this
> solved it or not. (so far it seems fixed)

Tried this, no effect. Same problem.
Comment 9 Rasmus B 2017-05-16 13:57:29 UTC
As previously mentioned, this bug seems to still be relevant on some system, including mine. It still doesn't work.

Can it be opened again or should I file a new bug?
Comment 10 Luzius Auer 2017-06-14 15:12:46 UTC
Still same problem though I tried all methods described here.
I'm using Krusader (instead of Dolphin) as default file manager and a Huawei P9 phone under Android 6.0
Very sad for an otherwise promising solution to access the Android file system from KDE. Why is the status marked RESOLVED FIXED. I strongly disagree.
Still hoping....
regards Luzius
Comment 11 Daniel Plaenitz 2017-06-29 12:01:30 UTC
I have the same issue here, right now. This problem is not new, I have seen it many times, actually since the very start of kde connect.

Rebooting the box usually solved it (for a while).
Today not so.
Checked ownership of files and folders under /home/user/.cache/kioexec (all owned by user), removed kioexec/, deleted the config, rebooted the box, paired the devices again, still the problem persists.

Since the bug was set to RESOLVED FIXED I suggest you add the steps to solution here or else reopen the bug..

KDE connect is a very cool software and it is disappointing that the key feature is so unreliable.

KDE Plasma 5.10.2
KDE framework 5.35.0
Kernel 4.11.6-1-ARCH

Device: Oneplus One (A0001)
LineageOS 14.1-20170612-NIGHTLY-bacon
Android 7.1.2
Comment 12 dE 2017-08-20 07:26:59 UTC
This's not a problem with kdeconnect, it's a problem with kio.
Comment 13 Bruno Pagani 2017-11-03 08:53:32 UTC
I’ve also been affected for some months now… Is there an open bug report against kio for this?