Hi!
Thank you for your app and work!
I lost ability to list directories on connected Android device.
On the previous 1.1.18 version that works just fine.
If to downgrade to 1.1.18, that it works fine: lists directories, copies files from/to device.
The portable device:
Android 9
MIUI12
The PC:
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.15.0-1-MANJARO (64-bit)
Graphics Platform: X11
Please suggest what information to gather to make it able to investigate the issue?
Anonymous
Made a typo in title, please read it as:
Can't see directory structure after upgrade from 1.1.18 to 1.1.19
Found the AUR package (https://aur.archlinux.org/packages/libmtp-git) and installed it instead of 1.1.18:
but it has the same issue too as 1.1.19 has.
does
mtp-detect
work? can you attach its output?
does mtp-files
work?
Thank you for your answer, Marcus!
No device connected:
The device connected, file transfer mode selected on the device:
Hm, reports that the device is busy.
May be to execute is with some TUI arguments (to force to switch to it ot to view what is using it else)?
Currently I use the
kernel.
Should I try current stable 5.14 or 5.10 LTS kernel version with the
1.1.19
?1.1.18
works just fine with that5.15.rc2
.Do you need the same commands output of the
1.1.18
(which works fine with the 5.15.rc2) to be able to compare them side by side?the problem here is that gvfs has probably grabbed the device and you can look at it in nautilus... can you check if its visible and browsable in nautilus ?
Opened Nautilus'es GUI, cliked on Android item on Locations list panel.
Got the GUI error window w/ the text:
I give it another try: I diconnected device, rebooted PC, connected device, open
nautilus
'es GUI and it works: I see directory list, can navigate and copy files to/from device.But the second and third time connections bring me that error which was before reboot:
Unable to access "Android" ...
If I understood correctly,
nautilus
is just another one file manager.Does the
1.1.19
was planned to introduce selection to file managers, which excluding Dolphin and Krusader as planned action?Also probably it was not planned to be able to act only during first connection of the device after PC reboot, making it work again only first time after reboot.
Probably somewhat gather control over somewhat in exclusive mode and can't share it with other components. But the same way that is not a problem for the
1.1.18
in the exactly the same all the environment, including hardware: if to downgradelibmtp
package only it works well.Can we proceed with investigation to fix current work state of the
libmtp
or it only my PC config problem and for others that's works fine?I started
journalctl -f
to look what happens when I acts with device and in PC GUI.Marcus, currently I am on
unstable
branch of updates (freshest on the Manjaro OS) and haveI suddenly realized that it works just fine (dir listings, copy to and from via Dolphin), I removed
nautilus
, rebooted PC and it also works all 3 times in 3 tries after that in theand in the
and currently PC running the
the OS is:
I suspect software environment got changes (not user-edited (by me) configs), but packages version itself and their configs (if was new).
Since that prev. report
there were changed:
Tried even 4th time w/o reboot: I do not meet the issue.
I suspect someone reported an issue of some component to its developers and I just got a new fixed version of it.
Thanks for help!
PS
And now while it works I see that:
It reports
device is busy
but it works well in Dolphin and Krusader (as was always for a few years before the issue).Also
is currenly.
Probably some software got control of it, but now it is typical software of user.
If you need some information to gather on my environment to investigate it, please let me know.
Thank you!
There is the
It was the nautilus + tracker3 / tracker3-miners update.
idea of what was a cause of the issue.Currently I have no
nautilus
, notracker3-miners
, but have theThanks!
Hi, Marcus!
I seethe ticket is still open. I re-read my post https://sourceforge.net/p/libmtp/bugs/1909/#1141 and I said there unclear. I meant with the 1.1.19 I just got other packages update and the issue disappeared: all works fine as always. Mentioned packages is the assumption of a powerful user about my problem. Sorry for bad worded post above. I do not have the issue anymore. The bug is fixed. Thank you!