After recent slackware64-current updates, when I connect my Android phone (set to MTP mode) via USB, I get a desktop icon in Xfce, but trying to open or mount it fails with: "No MTP devices found". This is with kernel 5.10.4 and Xfce-4.16. I went back to the kernels I used before, first 5.10.2, and then 5.4.84, but it fails the same way under those too.

Same phone and cable continue to work on another PC which has Slackware-14.2. If I switch the phone to PTP mode, it works under Slackware64-current (but of course most of the filesystem is inaccessible).

Any ideas? I don't even know what to try next.

I think I'll post a random link to a file. I won't say what it is, or why it's good to download, or why I posted a reply.

1 members found this post helpful.

I figured libusb-1.0.24 not working with usbmuxd in another thread, revert back to previous version maybe a choice.

I still not familiar with the forum spam rules, sorry for that.

Same hapened to me also.
Before upgrading to kernel 5.10.X i had the occasional mount error; only had to do was disconnect the cable and reconnect it and it worked. Now, my Samsung S6 just won't mount.

Oh well, i am used to get up and perform the "new-kernel-ritual-dance" praying that all these issues will be fixed

That's OK. Just posting a link might bother some people, but you did provide me some help: That libusb might be the cause of the problem, so it is something to look into. No, I'm not going to just download and install something, but at least I have something to look into. Thanks.

Reverting to the libusb-1.0.23-x86_64-1.txz package file I saved before updating : Fixed the problem.

(Lesson previously learned: saved those Slackware -current packages; I just use rsync without --delete to a flash drive)

Not sure I have enough information to open a bug report at https://github.com/libusb/libusb/issues but will see.

Thanks for the help.

how about another link that worked for me?

Found the libusb bug reports on this issue:

[Regression 1.0.24] Device is not enumerated on Linux #831

[regression 1.0.24] can't communicate with iPhone/iPad on Linux #825

Both of these are marked Closed and Fixed post-1.0.24. So we just need to wait for the next release.

If you are using -current and Plasma5, it comes with KDE_Connect which is a snazzy tool for transferring files into and out of your Android device. The Android side app is available at:
About kdeconnect:
https://f-droid.org/en/packages/org.kde.kdeconnect_tp/
Link to the apk file:
https://f-droid.org/repo/org.kde.kde...t_tp_11510.apk

It will find your Android device if it is on the same network, even if your linux box is a wired connect and your phone is wifi.

It has some other toys with it as well besides the file copy widget.

1 members found this post helpful.

If you don't want to take up all the space locally, the Slackware Cumulative mirror, where zhl used to link to the older libusb package, rsyncs without a delete. Almost any package from Slackware64 during any point in development can be found there.

Now for a history lesson, if you're interested...

This mirror was kickstarted from the slackmirror.cbpf.br mirror (which has sadly seemed to go offline), but according to Alien Bob, it's been keeping track of 64bit -current packages since the inception of Slackware64 and the 13.0 release. Alien Bob mirrored that site when he found it and started keeping all additional packages added to -current. He had already been keeping all the multilib packages. Eventually, both of those repos were moved to the slackware.uk mirror provided by tadgy. At that time, they also set up a cumulative mirror for 32bit Slackware, but they had no ability to grab older packages, so it only has about 1.5 years worth of 32bit -current history.

2 members found this post helpful.

Update: I reverted to libusb-1.0.23 and blocked future upgrades so it it won't install 1.0.24. Everything worked, and then it didn't work. The reason it broke is that there was a new aaa_elflibs package released on Jan 9 and it contains the 1.0.24 version of libusb. This overwrote the library version link from libusb-1.0.23 so even though libusb-1.0.23 was still installed, libusb-1.0.24 from aaa_elflibs was active, breaking access to the phone.

I fixed it by deleting libusb-1.0.so.0.3.0 and pointing the link libusb-1.0.so.0 back to libusb-1.0.so.0.2.0

Maybe re-installing libusb-1.0.23 again would have fixed it but I'm not sure.

Meanwhile, the libusb project "roadmap" says 1.0.25 is due out "by July 31, 2021" which is not good.

1 members found this post helpful.

It works for me. Not easy or intuitive for sure.

Pay attention to the drop down at the top. One is for sending files and one is for receiving files.

A patch for libusb-1.0.24, is available here:

https://github.com/archlinux/svntogi..._parsing.patch

2 members found this post helpful.

It works, thanks.