Description of problem: I've been using Cauldron for some time (on several machines) - and recently noticed that plugging in an Android mobile phone (in my case a OnePlus 7T and Galaxy Note 10+) into USB - I can't get MTP to work -only PTP - which still allows me to browse the full file structure on the device . . . With the Galaxy Note 10+ I get the following error: "The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8.2/ does not exist." Version-Release number of selected component (if applicable): How reproducible: Every time - Steps to Reproduce: 1. Plug in USB cable to Android phone 2. Try to mount it as MTP - Fails 3. PTP Works
Xiaomi Mi 9 T Pro, Android 10, MIUI 12. Plug USB cable between computer and phone. See "journalctl -f" log message kernel: usb 1-2: new high-speed USB device number 7 using xhci_hcd kernel: usb 1-2: New USB device found, idVendor=2717, idProduct=ff40, bcdDevice= 4.14 kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 kernel: usb 1-2: Product: Mi 9T Pro kernel: usb 1-2: Manufacturer: Xiaomi kernel: usb 1-2: SerialNumber: df9cc43e systemd[2224]: Started kioclient5. dbus-daemon[2244]: [session uid=1000 pid=2244] Activating service name='org.kde.kiod5' requested by ':1.130' (uid=1000 pid=16540 comm="mtp.so [kdeinit5] mtp local:/run/user/1000/klaunch") dbus-daemon[2244]: [session uid=1000 pid=2244] Successfully activated service 'org.kde.kiod5' kiod5[16543]: kf.kio.kiod: Couldn't register name "kmtpd" with DBUS - another process owns it already! systemd[2224]: Started Dolphin - Gestionnaire de fichiers. systemd[2224]: app-kioclient5-996ca3e845f84a3eafe9e1b1a9aa4cf2.scope: Succeeded. dolphin[16547]: kf.kio.core: Invalid URL: QUrl("") dolphin[16547]: kf.kio.core: Invalid URL: QUrl("") systemd[2224]: app-org.kde.dolphin-14325d096cc145caa285322f624620ad.scope: Succeeded. Note that your Android device must set USB connection as "File transfert MTP" or "PTP". By default, several Android phones set USB connection as "Charge-only".
On my Galaxy Note 10+ I see this. # journalctl -f Jan 25 10:13:50 dellirium kernel: usb 2-1.7: new high-speed USB device number 24 using ehci-pci Jan 25 10:13:50 dellirium kernel: usb 2-1.7: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= c.00 Jan 25 10:13:50 dellirium kernel: usb 2-1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 25 10:13:50 dellirium kernel: usb 2-1.7: Product: SAMSUNG_Android Jan 25 10:13:50 dellirium kernel: usb 2-1.7: Manufacturer: SAMSUNG Jan 25 10:13:50 dellirium kernel: usb 2-1.7: SerialNumber: XXXXXXXXXXXXX Jan 25 10:13:50 dellirium kiod5[1274124]: kf5.kiod.kmtpd: Unknown connection error Jan 25 10:13:50 dellirium colord-sane[1213216]: io/hpmud/pp.c 627: unable to read device-id ret=-1 And in Dolphin I get this message "The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7 does not exist." In pcmanfm I see "No MTP devices found" If I set my phone to "Transfer images" I am able to browse in pcmanfm, but not in Dolphin.
Hi. If you use "android-file-transfer" instead of dolphin does it work? And with "gmtp"? Does it have enabled the "USB debug mode"? USB debug mode is what you obtain when usually you go in the About Phone -> Software Information -> Build Number and you tap a certain number of times on it -> then go into "{ } Developer options" -> "USB Debugging". I noticed that when in debug mode, often many android devices change the USB id, and thus can't (or can) be recognized further. I think it's also related to libmtp, of which we have the latest. You might check the also the libmtp history to see if there are newer device added beyond the tagged release, in case of yours, see: https://sourceforge.net/p/libmtp/code/ci/2c01812092366e6e51fecb925e0bb66d5ecb472a/log/?path= Also, what if you boot with an older kernel? BTW, speaking of libmtp, maybe it's worthwhile to add the newer "Hero 9 Black" sigs, which seems jadded (at least comparing the commit date) beyond the 1.1.18 release (2020-10-11): https://sourceforge.net/p/libmtp/code/ci/b2e144519353602742585492aff84ea9562ae5a6/ there is also this patch: https://sourceforge.net/p/libmtp/code/ci/faaa32999d56fd8253453d7e307cb6932b00145a/
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=7638CC: (none) => fri
Thank you for reporting this; and the abundant evidence. Before assigning this bug, have you any idea whether the problem is due to Dolphin or Plasma? For example, if you have (install) another file manager, does it still not work? More radically, on a non-Plasma desktop (we would not expect you install another one, but you may have one)? > and recently noticed that plugging in an Android mobile phone > (in my case a OnePlus 7T and Galaxy Note 10+) into USB - > I can't get MTP to work It would have been nice to know the exact date when this started not working, to relate it to updates done at the time. I guess too late now. I am puzzled by comment 3 where you seem to be talking to yourself! But are more likely reporting advice from another source like a forum. Did you try any of it? And if so, with what result?
CC: (none) => lewyssmith, ouaurelien
(In reply to Lewis Smith from comment #4) > Thank you for reporting this; and the abundant evidence. > > Before assigning this bug, have you any idea whether the problem is due to > Dolphin or Plasma? For example, if you have (install) another file manager, > does it still not work? More radically, on a non-Plasma desktop (we would > not expect you install another one, but you may have one)? > > > and recently noticed that plugging in an Android mobile phone > > (in my case a OnePlus 7T and Galaxy Note 10+) into USB - > > I can't get MTP to work > It would have been nice to know the exact date when this started not > working, to relate it to updates done at the time. I guess too late now. > > I am puzzled by comment 3 where you seem to be talking to yourself! But are > more likely reporting advice from another source like a forum. Did you try > any of it? And if so, with what result? Comment 1 is mine reproduced as is here by reporter. This landed in dev ml early this morning. Incompatibilities are with some Android implementation of the MTP protocol. Plasma is not culprit here as it runs fine with my phone in Comment 1. Samsung ones are "en cause".
Here is an upstream BR. https://bugs.kde.org/show_bug.cgi?id=430606 Can someone test under XFCE/GNOME/Cinnamon/MATE to make sure it is only KDE/Plasma related? I don't have such "culprit" Android devices, mine is a Xiaomo Mi 9T Pro that can be connected smoothly on my system... Also, as workaround, under Plasma, you can use KDEConnect to browse files on your Android device...
URL: (none) => https://bugs.kde.org/show_bug.cgi?id=430606
An other one here: https://bugs.kde.org/show_bug.cgi?id=411489 With a workaround: > if I close *all* Dolphin windows before plugging the USB cable in the smartphone > and then plug it in and allow access *before* opening the next Dolphin window, > access works fine and I can browse the SD card and the internal memory of the > phone.
(In reply to Aurelien Oudelet from comment #7) > An other one here: https://bugs.kde.org/show_bug.cgi?id=411489 > With a workaround: > > > if I close *all* Dolphin windows before plugging the USB cable in the smartphone > > and then plug it in and allow access *before* opening the next Dolphin window, > > access works fine and I can browse the SD card and the internal memory of the > > phone. That doesn't work for me - when I plug in the OnePlus 7T I get the device popup which offers to mount the device for file browsing - when I try to mount it - Dolphin starts and gives the error as stated above :-(
(In reply to Robert Fox from comment #8) > (In reply to Aurelien Oudelet from comment #7) > > An other one here: https://bugs.kde.org/show_bug.cgi?id=411489 > > With a workaround: > > > > > if I close *all* Dolphin windows before plugging the USB cable in the smartphone > > > and then plug it in and allow access *before* opening the next Dolphin window, > > > access works fine and I can browse the SD card and the internal memory of the > > > phone. > > That doesn't work for me - when I plug in the OnePlus 7T I get the device > popup which offers to mount the device for file browsing - when I try to > mount it - Dolphin starts and gives the error as stated above :-( Have you restarted Dolphin after getting first error?
(In reply to Aurelien Oudelet from comment #9) > (In reply to Robert Fox from comment #8) > > (In reply to Aurelien Oudelet from comment #7) > > > An other one here: https://bugs.kde.org/show_bug.cgi?id=411489 > > > With a workaround: > > > > > > > if I close *all* Dolphin windows before plugging the USB cable in the smartphone > > > > and then plug it in and allow access *before* opening the next Dolphin window, > > > > access works fine and I can browse the SD card and the internal memory of the > > > > phone. > > > > That doesn't work for me - when I plug in the OnePlus 7T I get the device > > popup which offers to mount the device for file browsing - when I try to > > mount it - Dolphin starts and gives the error as stated above :-( > > Have you restarted Dolphin after getting first error? YES - no change
I can add nothing useful. Leaving with A.
CC: lewyssmith => (none)
This is sadly an upstream issue. Whether the issue is in Dolphin / kio-mtp or even on the Android device, I would let you please kdeconnect software for file transfert, as this is more reliable on all Android devices, in the meantime.
Keywords: (none) => UPSTREAM
Whether the issue is in Dolphin / kio-mtp or even on the Android device, I would let you please try kdeconnect software for file transfert, as this is more reliable on all Android devices, in the meantime. But this is rather a duplicate one of Bug 7638. *** This bug has been marked as a duplicate of bug 7638 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
I can't connect my samsung S5 with mageia 8 With 2 computers since a few months. Yes, I know, it's a old phone. But, it's my. I use xfce. You can see this here in French : https://www.mageialinux-online.org/forum/topic-28194-1+regle-liaison-smartphone-vers-pc-en-usb.php
CC: (none) => liste
More than phone model, i think it is more about Android version, and possibly phone manufacturers customisation.
Since mageia 8, I cannot connect anymore my phone in MTP mode; the device is no more seen with lsusb. In PTP mode it still works. I use XFCE. Same device worked fine under mga7.
CC: (none) => choucroot
Oleg Bosis says this bug is caused by a bug in libusb with a fix available here: https://github.com/libusb/libusb/commit/f6d2cb561402c3b6d3627c0eb89e009b503d9067 Thierry already added that patch in Cauldron, along with two others. Backporting here. libusb-tests-examples-1.0.24-2.1.mga8 libusb1.0-devel-1.0.24-2.1.mga8 libusb1.0_0-1.0.24-2.1.mga8 libusb-devel-doc-1.0.24-2.1.mga8 from libusb-1.0.24-2.1.mga8.src.rpm
Assignee: bugsquad => qa-bugsSource RPM: (none) => libusb-1.0.24-2.mga8.src.rpmResolution: DUPLICATE => (none)Status: RESOLVED => REOPENEDCC: (none) => olelukoie
Version is Mageia 8 ;)
Version: Cauldron => 8Keywords: UPSTREAM => (none)Status: REOPENED => NEW
CC: (none) => rolfpedersen
Tested with MGA8 GNOME kernel 5.10.20-desktop-2 updated with qa-repo: libusb-tests-examples-1.0.24-2.1.mga8 libusb1.0-devel-1.0.24-2.1.mga8 libusb1.0_0-1.0.24-2.1.mga8 libusb-devel-doc-1.0.24-2.1.mga8 installation de lib64usb1.0_0-1.0.24-2.1.mga8.x86_64.rpm depuis //home/user/qa-testing/x86_64 Préparation... ############################################# 1/1: lib64usb1.0_0 ############################################# 1/1: désinstallation de lib64usb1.0_0-1.0.24-2.mga8.x86_64 ############################################# Installed without problem Connection of Samsung S7 Edge Android by /e/ 7.1.2, mounted with MTP protocol correctly. File transfer in two ways ok
CC: (none) => guillaume.royer
Created attachment 12477 [details] Excerpt of systemd journal Installed packages android-file-transfer-4.2-1.mga8 kdeconnect-kde-20.12.0-1.mga8 lib64kdeconnectcore20-20.12.0-1.mga8 lib64kdeconnectinterfaces20-20.12.0-1.mga8 lib64kdeconnectpluginkcm20-20.12.0-1.mga8 lib64usb1.0_0-1.0.24-2.1.mga8 lib64usb-compat0.1_4-0.1.5-10.mga8 lib64usbmuxd2.0_6-2.0.2-1.mga8 lib64usbredirhost1-0.8.0-3.mga8 lib64usbredirparser1-0.8.0-3.mga8 Error before upgrade The file or folder udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/ does not exist. After upgrade No storage media found. Make sure your device is unlocked and has MTP enabled in its USB connection settings. File transfer still does not work, there is only a different error message. PTP works as stated in the head line. Hardware Sony Vaio E series notebook with KDE Plasma Galaxy J5 (2016) Android 7.1.1
CC: (none) => bequimao.de
(In reply to Ulrich Beckmann from comment #20) > Error before upgrade > The file or folder > udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:14.0/usb3/3-1/ does > not exist. > > After upgrade > No storage media found. Make sure your device is unlocked and has MTP > enabled in its USB connection settings. > > File transfer still does not work, there is only a different error message. > PTP works as stated in the head line. > > Hardware > Sony Vaio E series notebook with KDE Plasma > Galaxy J5 (2016) > Android 7.1.1 It's strange. I've just retested my three Android devices (Lenovo A8 Tab with Android 4.4.4, Samsung Galaxy Tab S3 with Android 9 and Samsung A71 with Android 11) and all of them do work with MTP under KDE with patched libusb package. The only problem with old Lenovo device is that is is very slow to perform any file operations over MTP. BTW the patch to libusb fixes a regression affecting Android 10 & 11 (according both my own experience and comments on libusb discussions). I had no problems with older devices without this patch...
Created attachment 12478 [details] trials of Androaid File Transfer and KDE connect Thanks for the mention of [Android File Transfer]. This works (mageia 8-no problem with older versions of Mageia-, recent Samsung tablette). If you store material (PDF files etc.) on an SD card make sure that you changle "tablette" to "card". The other suggestion [KDE connect] did not work; see attached. So many thanks, for I had never head of these applications and I never would have guessed at what type of application to look for in the repository. See the following: ****************************** The present situation illustrates a weakness of the Bugzilla system, namely that multiple users have the same problem, but not necessarly with the same description (the "PLasma freezes" problem is a prime example of this]. Further, in this case, we had two suggested solutions via applications which are in the Mageia repository. What is needed, in my humble opinion, is a section for general and often reported problems either on top of Bugzilla or on a separate Mageia page. Thus: PROBLEMS?, LOOK HE FIRST FOR A SOLUTION 1. Android Connections. Many people have had this problem. Download Android File Transfer and KDE transfer in the Mageia Repository. 2. PLASMA problems. These manifest themselves in many ways. This is a KDE problem, not a MAGEIA problem. The KDE people are working on it and hopefully the problem will disappear with MAGEIA 8 (p.s. no longer real freezes, but still pauses) Just think how much time these two little comments would have saved the fine people trying to make MAGEIA work
CC: (none) => roger
Whiteboard: (none) => MGA8-64-OK
I don't know if MTP file transfer ever worked on my hardware. Thanks for your comments! Ok'ing the bug report, as it is definitely an improvement. Ulrich
It's not an improvement for everybody, Ulrich. Phone: Samsung Galaxy J3 Orbit, running Android 9, fully updated as of today. I just tried this phone with a mga7 Plasma install, and the phone was mountable using MTP with Dolphin, no errors. File transfers, no problems. Same desktop PC hardware, only with a mga8 Plasma install before the libusb update, no joy. I see the errors shown in Comment 20. After the update, no change, same messages. Android File Transfer won't work, either. An older Android tablet, using Android 4.3, does work with mga8 and Dolphin, both before and after the update. So, the phone works with mga7 Plasma, but not mga8 Plasma, making this a definite regression. And while the update may let a few more phones work with mga8, it by no means fixes that regression. Removing the OK and sending it back to the bugsquad.
CC: (none) => andrewsfarmAssignee: qa-bugs => bugsquadWhiteboard: MGA8-64-OK => (none)
It's good in Cauldron (mag9 and my Samsung S5). If you want, I can try mga8. It's was not good when I used mga8.
It seems like there're several (definitely more than one) bugs/regressions with MTP support in MGA8. The one already found and fixed is a regression in libusb. To determine if the rest ones are related to libusb (or some other low-level system componet) you need to install libmtp-utils and run mtp-detect with your device connected. If mtp-detect correctly shows your device then the bug is not related to low-level components and related to KDE itself. In my case mtp-detect coudn't detect my phone and reported there are no MTP devices. Also check the system log after connecting device - it may contain some important error messages (the easiest way to do this in KDE is to install and run ksystemlog, filter messages by "usb" keyword, then connect device to PC and see what's going on in log, then stop updating the log, remove filter and check the log for possible additional messages about connected device).
Sum up: Multiples Android versions / Multiples phone manufactured involved. MTP is a protocol. https://en.wikipedia.org/wiki/Media_Transfer_Protocol It is a file+metadatas involved protocol (invented by Microsoft for Winddows Media Devices) rather than an USB-mass storage layer. It does not expose the filesystem from the portable device. Despite identifiability by the PTP/MTP USB device class, libmtp documentation indicates that the vendor and product ID combination plays a functional role in identifying an MTP device. Libmtp includes vast listings of vendor and product ID numbers of devices that it supports, along with workarounds for bugs. This non-generic methodology hinders MTP drivers' forward compatibility with new devices. Note also that mtp protocol can be "shutdown" by lockscreen on Android OS, permissions enforcement and confidentiality options For KDE/Plasma: Suggestion on Android is to use KDEConnect application to share files. Or Bluetooth. Or share sdcard from the device to a reader on the computer. Difficult to assign correctly: Kernel? udev rules? libmtp/ jmtpfs? kio-mtp? Android file Transfer? Assigning globally. Adding KDE and Kernel maintainers in CC.
Whiteboard: (none) => MGA8TOO regressionSummary: Under KDE and recently Cauldron - MTP mounting a Android phone doesn't work (only PTP mode) => Under KDE - MTP mounting SOME Android phones doesn't work (only PTP mode)Assignee: bugsquad => pkg-bugsVersion: 8 => CauldronCC: (none) => kde, kernel
I'm not arguing any of the points of Comment 27 - it is far from any area where I have any expertise. That said... I can understand having problems with new phones and Android versions, but beyond that it seems to me from a user's perspective that at the very least Android devices that currently work with Mageia 7 ought to also work with Mageia 8. Until this bug is vanquished, my workaround will be to use Mageia 7 on those rare occasions when I need to communicate with my phone's internal storage.
Unfortunately too many components are updated in MGA8 compared to MGA7. libusb updated from 1.0.22 to 1.0.24 (two versions jump), libmtp updated from 1.1.16 to 1.1.18 (also two versions jump) and I won't even mention the number of versions skipped on KDE side. The only common part is the kernel 5.10, so we can say that kernel side works properly. Thus trying to find all bugs in MTP stack in MGA8 compared to MGA7 is like trying to solve a single equation with several unknown variables. Currently we can only relatively easy test libmtp. It seems like both 1.1.16 and 1.1.18 provide the same binary library version libmtp.so.9.4.0. This gives an ability to ("unofficially") backport libmtp 1.1.18 to MGA7 and test if Android devices would still work. This would allow us to exclude libmtp from potential reasons (if devices would work) or blame it (if devices won't work). As for libusb I'd like to ask you to promote current version to official updates as it definitely fixes at least 3 regressions with different USB devices and doesn't introduce any new one.
"As for libusb I'd like to ask you to promote current version to official updates as it definitely fixes at least 3 regressions with different USB devices and doesn't introduce any new one." I suppose we could do that, but since it doesn't fully fix the issue raised in this bug, I would think it would need a new bug report of its own that could then be sent to QA for approval (as long as a clean install would be sufficient), while leaving this bug still under investigation. But, decisions like that are above my pay grade. Anybody want to take over?
(In reply to Thomas Andrews from comment #30) > > But, decisions like that are above my pay grade. Anybody want to take over? I guess not. OK, assigning it back to QA, OKing it as far as it goes on a clean install and on a report that it helps some but doesn't seem to have any new regressions. Changing to Version 8, as the package that was tested was for Mageia 8. If the problem still exists in Cauldron, it will need a new bug. I will file a new Mageia 8 bug for the phones that still don't work with it.. Validating. Still needs an advisory.
Whiteboard: MGA8TOO regression => MGA8-64-OKAssignee: pkg-bugs => qa-bugsKeywords: (none) => validated_updateVersion: Cauldron => 8CC: (none) => sysadmin-bugs
(In reply to Thomas Andrews from comment #31) > > I will file a new Mageia 8 bug for the phones that still don't work with it.. > Bug 28646.
My mistake. This update DOES allow my 32-bit Xfce system to communicate with my Samsung phone. To me, that means the remaining problem is probably Plasma-related.
Added to errata together with the issue about iPhones https://wiki.mageia.org/en/Mageia_8_Errata#Phone_USB_connection
Keywords: (none) => IN_ERRATA8
Advisory: ======================== Updated libusb packages improve Android phones USB connections The libusb packages has been updated to include backported upstream fixes to improve Android phones USB connectivity. References: https://github.com/libusb/libusb/commit/f6d2cb561402c3b6d3627c0eb89e009b503d9067 ======================== Updated packages in 8/core/updates_testing: ======================== libusb-tests-examples-1.0.24-2.1.mga8 libusb1.0-devel-1.0.24-2.1.mga8 libusb1.0_0-1.0.24-2.1.mga8 libusb-devel-doc-1.0.24-2.1.mga8 from libusb-1.0.24-2.1.mga8.src.rpm
Keywords: (none) => advisory
Tested with MGA8 XFCE kernel 5.10.25-desktop updated with qa-repo: libusb-tests-examples-1.0.24-2.1.mga8 lib64usb1.0-devel-1.0.24-2.1.mga8 lib64usb1.0_0-1.0.24-2.1.mga8 libusb-devel-doc-1.0.24-2.1.mga8 installation de lib64usb1.0_0-1.0.24-2.1.mga8.x86_64.rpm depuis //home/user/qa-testing/x86_64 Préparation... ############################################# 1/1: lib64usb1.0_0 ############################################# 1/1: désinstallation de lib64usb1.0_0-1.0.24-2.mga8.x86_64 ############################################# Installed without problem Connection of Samsung S7 Edge Android by /e/ 7.1.2, mounted with MTP protocol correctly. File transfer in two ways ok but I have some random problems. When I click in the phone directories to enter them, the browser sends me back to /home. I don't have this problem with Nautilus in GNOME. Is it a problem with Thunar ?
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2021-0053.html
Status: NEW => RESOLVEDResolution: (none) => FIXED
Fixed with Samsung Galaxy S5 and Galaxy tab S2. Thanks!