slackware-current breakage of MTP after [Wed May 23 04:42:29 UTC 2018] update
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
slackware-current breakage of MTP after [Wed May 23 04:42:29 UTC 2018] update
I'm on slackware64 current. I've done the "Wed May 23 04:42:29 UTC 2018" update on current and I'm having problems with MTP: my android device is hard disconnected while copying.
I tried to rebuild libmtp from sources, but it didn't help
from /var/log/messages:
Code:
May 23 13:08:27 zion kernel: [ 46.290639] usb 1-7.2: new high-speed USB device number 5 using ehci-pci
May 23 13:08:27 zion kernel: [ 46.369821] usb 1-7.2: New USB device found, idVendor=05c6, idProduct=6764
May 23 13:08:27 zion kernel: [ 46.369824] usb 1-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 23 13:08:27 zion kernel: [ 46.369826] usb 1-7.2: Product: A0001
May 23 13:08:27 zion kernel: [ 46.369828] usb 1-7.2: Manufacturer: OnePlus
May 23 13:08:27 zion kernel: [ 46.369829] usb 1-7.2: SerialNumber: 6464d85d
May 23 13:08:37 zion kernel: [ 55.551829] usb 1-7.2: USB disconnect, device number 5
May 23 13:08:37 zion kernel: [ 55.813641] usb 1-7.2: new high-speed USB device number 6 using ehci-pci
May 23 13:08:37 zion kernel: [ 55.892826] usb 1-7.2: New USB device found, idVendor=05c6, idProduct=6764
May 23 13:08:37 zion kernel: [ 55.892829] usb 1-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 23 13:08:37 zion kernel: [ 55.892831] usb 1-7.2: Product: A0001
May 23 13:08:37 zion kernel: [ 55.892832] usb 1-7.2: Manufacturer: OnePlus
May 23 13:08:37 zion kernel: [ 55.892833] usb 1-7.2: SerialNumber: 6464d85d
May 23 13:09:21 zion kernel: [ 99.657137] usb 1-7: USB disconnect, device number 4
May 23 13:09:21 zion kernel: [ 99.657139] usb 1-7.2: USB disconnect, device number 6
May 23 13:09:21 zion kernel: [ 99.766832] pool[8352]: segfault at 198 ip 00007f5e0203e340 sp 00007f5dee7fbe00 error 4 in libgvfsdaemon.so[7f5e02026000+26000]
May 23 13:09:21 zion kernel: [ 99.891637] usb 1-7: new high-speed USB device number 7 using ehci-pci
May 23 13:09:21 zion kernel: [ 100.023976] usb 1-7: New USB device found, idVendor=05e3, idProduct=0608
May 23 13:09:21 zion kernel: [ 100.023979] usb 1-7: New USB device strings: Mfr=0, Product=1, SerialNumber=0
May 23 13:09:21 zion kernel: [ 100.023980] usb 1-7: Product: USB2.0 Hub
May 23 13:09:21 zion kernel: [ 100.024693] hub 1-7:1.0: USB hub found
May 23 13:09:21 zion kernel: [ 100.024965] hub 1-7:1.0: 4 ports detected
May 23 13:09:21 zion kernel: [ 100.298641] usb 1-7.2: new high-speed USB device number 8 using ehci-pci
May 23 13:09:21 zion kernel: [ 100.377965] usb 1-7.2: New USB device found, idVendor=05c6, idProduct=6764
May 23 13:09:21 zion kernel: [ 100.377967] usb 1-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 23 13:09:21 zion kernel: [ 100.377969] usb 1-7.2: Product: A0001
May 23 13:09:21 zion kernel: [ 100.377970] usb 1-7.2: Manufacturer: OnePlus
May 23 13:09:21 zion kernel: [ 100.377971] usb 1-7.2: SerialNumber: 6464d85d
from /var/log/syslog
Code:
May 23 13:09:21 zion kernel: [ 99.657130] usb usb1-port7: disabled by hub (EMI?), re-enabling...
I've given up on mtp. There have always been issues, and the last time I tried any program that supported it, none of them consistently worked. And I had crashes too.
I've given up on mtp. There have always been issues, and the last time I tried any program that supported it, none of them consistently worked. And I had crashes too.
OK, that's an option that I already use. But when I'm moving my TWRP backup (>8.5GB) I still prefer cable transferring. It has a decent speed and it doesn't flood my network. MTP is definitely NOT a jewel, but I always used to use it smoothly (I think through gvfs and libmtp: I find my device on Thunar and just used it!). These errors are occurring after the latest slackware current update, so I think it could be related.
Did mtp work for you after May 1st update?
On May 1st there was a "fix" added to eudev to fix MTP with Kernel >= 4.12 and KDE. Maybe that fix broke mtp for you?
The original mtp problem seem to reported upstream (means systemd) here. So there might really be an issue with bind/unbind actions.
Did mtp work for you after May 1st update?
On May 1st there was a "fix" added to eudev to fix MTP with Kernel >= 4.12 and KDE. Maybe that fix broke mtp for you?
The original mtp problem seem to reported upstream (means systemd) here. So there might really be an issue with bind/unbind actions.
Yes, last time I used it was May 14th, and it worked as usual.
But when I'm moving my TWRP backup (>8.5GB) I still prefer cable transferring. It has a decent speed and it doesn't flood my network.
I know I'm a bit late to responding with this, but as with others, I've gotten annoyed with the inconsistencies with mtp. Sometimes it works, sometimes it doesn't... As others, I'll usually transfer things wirelessly, but I do agree that it isn't always ideal.
When I do need to transfer things using wired, I've actually switched to adb (stands for Android Debugging Bridge). It is a development tool used by Android developers to test various things. While adb can do a ton of things, I mainly use it for "push" and "pull". The first will push files from your computer to the phone, and the other pulls from the phone and puts them on the computer. If you want to grab your TWRP files, you should be able to run:
Code:
adb pull /sdcard/TWRP/
(I think, I'm not hooked up to verify my command).
I know I'm a bit late to responding with this, but as with others, I've gotten annoyed with the inconsistencies with mtp. Sometimes it works, sometimes it doesn't... As others, I'll usually transfer things wirelessly, but I do agree that it isn't always ideal.
Well, it seems the MTP problem solved by itself: I think that it can be device related. I'm using LineageOS on my Oneplus One, and after a few updates (they release a nighly every week), it simply disappeared.
Quote:
When I do need to transfer things using wired, I've actually switched to adb (stands for Android Debugging Bridge). It is a development tool used by Android developers to test various things. While adb can do a ton of things, I mainly use it for "push" and "pull". The first will push files from your computer to the phone, and the other pulls from the phone and puts them on the computer. If you want to grab your TWRP files, you should be able to run:
Code:
adb pull /sdcard/TWRP/
(I think, I'm not hooked up to verify my command).
I know very well the android-tools: with a device like that, you'll better familiarize soon and good with adb & fastboot
But I'd like to avoid enabling and disabling adb all the time and the MTP simply did the jod (and do it again now).
I think the correct way to download a directory via ADB is
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.