Bug 398989 - No access to mobile phone, Error - KIO Client, The file or folder does not exist
Summary: No access to mobile phone, Error - KIO Client, The file or folder does not exist
Status: RESOLVED DUPLICATE of bug 396527
Alias: None
Product: kio-extras
Classification: Frameworks and Libraries
Component: MTP (show other bugs)
Version: 18.04.3
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: ---
Assignee: Elvis Angelaccio
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-23 14:24 UTC by Attila
Modified: 2018-09-30 16:08 UTC (History)
0 users

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 Attila 2018-09-23 14:24:12 UTC
SUMMARY
When I connect my phone via USB to my PC and click on the first option "Open with File Manager", I get an error like:

Error - KIO Client

The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:13.2/usb2/2-1/ does not exist.

STEPS TO REPRODUCE
1. Connect the phone via USB to the PC.
2. Select in the device notifier the first option "Open with File Manager"

EXPECTED RESULT
I should be able to access the content of the phone in Dolphin.

ACTUAL RESULT
Error - KIO Client


SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.4
KDE Frameworks Version: 5.48.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION

When I click on the second option "Open with File Manager", Dolphin appears and I see one directory "store_00010001" and two files "about.txt", "summary.txt".
Non of them are accessible (readable).
Permissions for the directory are: drwxrwxrwx
Permissions for the files are: -r--r--r--

Click on the directory shows an error like:
Could not read. Reason: Unspecified error
camera:/Xiaomi%2520Mi-2s%2520(id2)%2520(MTP)@usb:002,004/store_00010001/

Click on the file shows an error like:
Could not read. Reason: Directory not found
camera:/Xiaomi%2520Mi-2s%2520(id2)%2520(MTP)@usb:002,004/about.txt/
Comment 1 Elvis Angelaccio 2018-09-30 16:08:31 UTC

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