Summary: | Android File System not Mounted and Pairing is no longer persistent. | ||
---|---|---|---|
Product: | [Applications] kdeconnect | Reporter: | Michael Tunnell <m> |
Component: | android-application | Assignee: | Albert Vaca Cintora <albertvaka> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bruno.n.pagani, de.techno, incoming, kdebug, luzius, rasmus |
Priority: | NOR | ||
Version: | 1.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Michael Tunnell
2016-12-20 17:53:57 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. 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 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. 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. > 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 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 (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. (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. 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? 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 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 This's not a problem with kdeconnect, it's a problem with kio. I’ve also been affected for some months now… Is there an open bug report against kio for this? |