I am getting this error when trying to mount my Samsung phone (Android 10) on Solus. I don't do that very often, but in the past it always worked. It also works with Windows like it did in the past. What could be the cause of this? I use Budgie, tried on both current and lts kernels, same error on both.

7 days later

I've got the same problem with my Samsung Galaxy S7 on Android 8 and current Solus with Budgie. Can't access the Phone to backup my pictures.
Solution from sunnyflunk two years ago doesn't work since I don't have this file: /usr/lib64/udev/rules.d/69-libmtp.rules (https://dev.getsol.us/T6123)

Aren't there phone setting options (in settings on the phone) like usb charge, file transfer, picture tranfer, etc etc that you manually set when plugging into computer?
Works for me that way but I know models vary.

    When plugging it into a win10 laptop it is triggered if the phone should be accessible from this laptop, when saying yes, you can access it.
    But on solus nothing of this sort is triggered. It just stays quiet, only the charging indicator comes up (solus also shows it in the left side of the file manager). Tested also with 3 different cables in order to rule out any problems there might be.

      • [deleted]

      • Post #5
      • Edited

      brent That's how my phone works. It charges by default and I have to choose File Transfer manually. Though some phones want their own (Windows) software to be installed and mount as a CD-ROM.

          Ah I totally misread that, thanks for stalebrim for making it clear again for me. Just tried and yes it works if I change the setting on android manually to 'only picture transfer'. Strangely enough I can then access all of the memory xD
          Thanks a lot!

          hunzel When plugging it into a win10 laptop it is triggered if the phone should be accessible from this laptop, when saying yes, you can access it.
          But on solus nothing of this sort is triggered. It just stays quiet, only the charging indicator comes up (solus also shows it in the left side of the file manager). Tested also with 3 different cables in order to rule out any problems there might be.

          Maybe that's because Solus doesn't know how to see it. That's where specifying settings come in. But [deleted] has a good point that maybe an proprietary incompatibly exists. I think eventually you will win this battle---there's a few ways to skin a cat here, as they say.

              brent Yes, there are, by default it is file transfer and charging for me. And usually the phone would appear right away i would just need to mount it. Now i only get this error. Photo transfer mode does show folder structure on my phone, but there are no files anywhere. I mean it did work some time before flawlessly, so something happened. Maybe on Android side of things, i wouldn't know.

                  • [deleted]

                  • Post #10

                  What does your dmesg tell you when you connect your phone?

                    DNI_R Went to dev tracker to see if there were other cases of this to give you a better steer.
                    Results:
                    1) a search of 'mount phone' came up basically NIL but I noticed you filed a ticket already so good.
                    2) A search of 'MTP', however, was interesting and worth reading if you have not already.
                    Good luck.

                      Heya, I noticed a few days ago that i have the same problem, while it worked fine before. My android didn't get any updates, unlike yours. However there's a difference, Solus doesn't display MTP errors anymore, but the URL which is displayed in the error starts with UDI. Does it do the same on your side ? Maybe there's something to be investigated here ? It used to be MTP, that I'm sure of.

                      To illustrate I'll paste my error here :

                      udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/ doesn't exist

                      Edited for better clarity

                      I have the same error

                      [deleted]

                      [10835.162467] usb 3-1: New USB device strings: Mfr=7, Product=8, SerialNumber=9
[10835.162470] usb 3-1: Product: SAMSUNG_Android
[10835.162471] usb 3-1: Manufacturer: SAMSUNG
[10835.162473] usb 3-1: SerialNumber: {removed}
[10918.783865] usb usb3-port1: disabled by hub (EMI?), re-enabling...
[10918.783872] usb 3-1: USB disconnect, device number 12
[10919.019255] usb 3-1: new high-speed USB device number 13 using xhci_hcd
[10919.152371] usb 3-1: New USB device found, idVendor=04e8, idProduct=6860, bcdDevice= c.00
[10919.152375] usb 3-1: New USB device strings: Mfr=7, Product=8, SerialNumber=9
[10919.152377] usb 3-1: Product: SAMSUNG_Android
[10919.152379] usb 3-1: Manufacturer: SAMSUNG
[10919.152381] usb 3-1: SerialNumber: {removed}

                        EDIT: Not a Plasma issue. Happens on Budgie too.

                        From journalctl

                        Dec 31 12:28:17 arthur-dent-beta plasmashell[1142]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:314: TypeError: Cannot read property 'width' of null
Dec 31 12:28:22 arthur-dent-beta plasmashell[1142]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:195: TypeError: Value is undefined and could not be converted to an object
Dec 31 12:28:22 arthur-dent-beta plasmashell[1142]: file:///usr/share/plasma/plasmoids/org.kde.plasma.devicenotifier/contents/ui/DeviceItem.qml:202: TypeError: Value is undefined and could not be converted to an object
Dec 31 12:28:23 arthur-dent-beta kiod5[32906]: kf5.kiod.kmtpd: New device attached with udi= "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3" . Checking if PortableMediaPlayer...
Dec 31 12:28:23 arthur-dent-beta kiod5[32906]: kf5.kiod.kmtpd: SOLID: New Device with udi= "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3"
Dec 31 12:28:23 arthur-dent-beta kiod5[32906]: kf5.kiod.kmtpd: new device, getting raw devices
Dec 31 12:28:23 arthur-dent-beta kiod5[32906]: kf5.kiod.kmtpd: Unknown connection error
Dec 31 12:28:23 arthur-dent-beta plasmashell[1142]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:314: TypeError: Cannot read property 'width' of null
Dec 31 12:29:02 arthur-dent-beta kdeinit5[32903]: kde.kio-mtp: fileSystemFreeSpace: QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3")
Dec 31 12:29:02 arthur-dent-beta kdeinit5[32903]: kde.kio-mtp: udi =  "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3"
Dec 31 12:30:02 arthur-dent-beta kdeinit5[32903]: kde.kio-mtp: fileSystemFreeSpace: QUrl("mtp:udi=/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3")
Dec 31 12:30:02 arthur-dent-beta kdeinit5[32903]: kde.kio-mtp: udi =  "/org/kde/solid/udev/sys/devices/pci0000:00/0000:00:01.3/0000:03:00.0/usb1/1-3"

                          [deleted] dmesg is the same, nothing on journalctl. Just a pop-up error saying "Unable to access "SAMSUNG Android" No MTP devices found"

                            Resolved now in unstable. If you are on stable i'd probably recommend downgrading libusb to resolve the issue until Friday's sync.

                            eopkg it https://mirrors.rit.edu/solus/packages/shannon/libu/libusb/libusb-1.0.23-10-1-x86_64.eopkg

                            Or you can manually grab the newest 12 release from the unstable repo, whichever way that floats your boat.

                            If downgrading causes issues you can always get the current stable version with eopkg it --reinstall libusb

                            Thank you very much, as always the team is insanely reactive !