SUMMARY STEPS TO REPRODUCE 1. Plug a non player device into USB. 2. The notification drawer pops up. It shows "Open in files manager" 3. Click on "Open in files manager" OBSERVED RESULT Dolphin opens. The device is not shown in the storage list and cannot be browsed. EXPECTED RESULT Dolphin opens. The device is shown in the storage list. It can be browsed, files copied, and so on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.11.8 KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION The behaviour was correct until the latest update of libmtp9-1.1.22 or libmtp-dev-1.1.22, on November 14th. Rolling back to 1.1.21-5 fixes it. The USB device is a custome device, it is not player device but exposes the filesystem using mtp (umtpresponder precisely). it works fine on Windows 11 (with proper drivers) and on linux before libmtp 1.1.22.
Hi - are you able to check if any of the libmtp example CLI tools are able to access that device? (Thinking of a way to see if it's a libmtp upstream issue, or something in how KIO talks to it)
Hi, thanks for your comment. I did a small test, since I could not remove the working libmtp, I entered init3 to avoid interferences from other daemons, rebuilt libmtp all static and linked mtp-filetree statically. I used ./configure --enable-static --disable-shared CFLAGS="-static" and then built the examples with CFLAGS="-static". that seems to have worked: ``` $ldd mtp-filetree linux-vdso.so.1 (0x00007fb6db565000) libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x00007fb6db51c000) libc.so.6 => /lib64/libc.so.6 (0x00007fb6db200000) libudev.so.1 => /lib64/libudev.so.1 (0x00007fb6db4d7000) /lib64/ld-linux-x86-64.so.2 (0x00007fb6db567000) libcap.so.2 => /lib64/libcap.so.2 (0x00007fb6db4c9000) ``` And then ``` $ mtp-filetree Attempting to connect device(s) Android device detected, assigning default bug flags Device: Bridgemate 3 Scoring Device Storage Storage: Data 2 ColdStorage.db Storage: LogFiles 8 hald.log 7 crash 6 update.log 5 system.log Storage: Updates OK. ``` I'm not sure the test is 100% valid here, it would have been better to use the system mtp-1.1.22 but I cannot break it, I need the mtp working. Let me know if I can do any other test.
Additional note I forgot to mention. Of course the VID and PID are not recognized. The message doesn't appear in the output, but it was printed in the console.
Thanks, this one's outside my expertise but updating the title to reflect what you found