Bug 356528 - Dolphin can not access android file system
Summary: Dolphin can not access android file system
Status: RESOLVED DUPLICATE of bug 341175
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-11 19:49 UTC by Harald Schugt
Modified: 2016-10-18 11:07 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Testing the bug (106.30 KB, image/png)
2016-06-01 22:54 UTC, Billy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Schugt 2015-12-11 19:49:59 UTC
All functions to interconnect my android device and KDE are working pretty well.
Just the file access from dolphin to the android device fails. I can see four folders of my Huawei smartphone (internal memory, SD card, ..). Klicking on all of those folders generates a error message like " the file or folder /home/username/.config/kdeconnect/f5d46edf9b192b9a/kdeconnect_sftp/f5d46edf9b192b9a/storage/emulated/0 does not exist"
I use OpenSuSE Leap 42.1 and run the latest rpm of kdeconnect (0.9f). The sftp rpm is installed.
Any idea? Thank You in advance ....

Reproducible: Always
Comment 1 Harald Stürmer 2015-12-12 18:34:40 UTC
Same problem here with different devices. One a Nexus Galaxy with Android 4.4, second an Elefone with Android 5.1 and last a tablet with Android 4.1. My system is also OpenSuSE Leap 42.1 with same version and sources.
Comment 2 Robert G. Siebeck 2015-12-30 23:09:56 UTC
Possible duplicate of #355015
Comment 3 Billy 2016-06-01 22:54:16 UTC
Created attachment 99320 [details]
Testing the bug

I just tested this on my Nexus 4 from openSUSE Tumbleweed, and it worked just fine. I'm guessing this has been fixed?
Comment 4 Harald Schugt 2016-06-17 20:16:08 UTC
I tested on my Honor 6. The problem still exists
Comment 5 pikkuporo 2016-10-13 12:28:58 UTC
This seems to be the same issue presented in bug 369495.
Comment 6 Albert Vaca Cintora 2016-10-18 11:07:43 UTC

*** This bug has been marked as a duplicate of bug 341175 ***