Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56747 - [kio-extras] unable to connect an android smartphone

Attached to Project: Arch Linux
Opened by patrick (potomac) - Sunday, 17 December 2017, 01:00 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 28 October 2018, 08:51 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

I use plasma 5, when I try to mount an android smartphone via usb on dolphin I get this error message from kio-client :

The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4/ does not exist.

the workaround I found is to mount manually my smartphone with jmtfs :

jmtpfs ~/mnt/android/

it seems that something is broken in kio-extras related to mtp mount,
several month ago I was able to mount my smartphone with kio in dolphin without problems

Additional info:
* package version(s) extra/kio-extras 17.08.3-1
* config and/or log files etc.


Steps to reproduce:
- connect an android smartphone via USB
- select "mount with dolphin"
- the operation will fail with the error message : "The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-4/ does not exist."
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 28 October 2018, 08:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  libmtp 1.1.16
Comment by glavin lewis (Glavin) - Sunday, 17 December 2017, 03:20 GMT
There is already a bug report posted upstream.
Bug Report
https://bugs.kde.org/show_bug.cgi?id=387454
Comment by glavin lewis (Glavin) - Saturday, 13 January 2018, 15:07 GMT
This issue has been resolved with KDE Frameworks 5.42 update.
Comment by Antonio Rojas (arojas) - Saturday, 13 January 2018, 15:11 GMT
What's the source for that? 5.42 is not out yet and there's no info in the upstream report
Comment by Antonio Rojas (arojas) - Saturday, 29 September 2018, 09:43 GMT
Not much we can do about this at the packaging level. See the upstream report, particularly https://bugs.kde.org/show_bug.cgi?id=387454#c25, for some workarounds.

Loading...