Bug 1653016 - Nautilus updates extremely slow for mtp connected device
Summary: Nautilus updates extremely slow for mtp connected device
Alias: None
Product: Fedora
Classification: Fedora
Component: libmtp
Version: 29
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Linus Walleij
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-11-24 14:02 UTC by Jan Vlug
Modified: 2019-11-27 20:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-27 20:00:48 UTC
Type: Bug

Attachments (Terms of Use)

Description Jan Vlug 2018-11-24 14:02:02 UTC
Description of problem:
I connect my Android phone to the Fedora host via USB. MTP is selected at the phone for the USB behavior.

Version-Release number of selected component (if applicable):
esmtp.x86_64               1.2-12.fc29                         @System                
gvfs-mtp.x86_64            1.38.1-1.fc29                       @System                
libesmtp.x86_64            1.0.6-16.fc29                       @System                
libmtp.x86_64              1.1.16-1.fc29                       @updates

How reproducible:

Steps to Reproduce:
1. Connect MTP Android phone via USB to Fedora host

Actual results:
1. I see in Nautilus that the MTP device is mounted, but no files in Nautilus.
2. There is no indication that Nautilus is still 'loading' the file list.
3. Minutes later, the content of the MTP device appears.

Expected results:
1. See immediately the content of the MTP device.
1. See an indicator that shows that the file list is still being loaded.

The current behavior gives the suggestion that there is something wrong with the mount/connection of the MTP device, because no files are visible and no indication is given that Nautilus is still obtaining the file list.

Comment 1 Ben Cotton 2019-10-31 20:28:01 UTC
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2019-11-27 20:00:48 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.