Bug 1010878

Summary: File manager does not refresh when multilevel directories moved to trash.
Product: [Fedora] Fedora Reporter: Roman Ovseitsev <romovs>
Component: gvfsAssignee: Ondrej Holy <oholy>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: alexl, bnocera, oholy, romovs
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:19:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
demonstration of the problem. none

Description Roman Ovseitsev 2013-09-23 08:58:58 UTC 
Created attachment 801547 [details]
demonstration of the problem.

It seems file managers relying on gfvs do not refresh properly when a directory is open in the file manager and its parent (or any directory above it) is moved to the trash.

Steps to reproduce:
1. Create two directories Test1 and Test2: $HOME/Test1/Test2
2. Open Test2 in a tab
3. Open $HOME in another tab and try moving Test1 to trash.
4. At this point Test2 tab isn't refreshed to $HOME (as it would for example if Test2 itself was moved to trash)

Please see the attached screencast for a demonstration.

MATE file manager was used in the demo above, but according to the mate devs.  this seems to affect nemo, nautilus, and thunar - hence the gvfs suspicion. Please see https://github.com/mate-desktop/mate-file-manager/issues/155

Would appreciate any clarification on this. Thanks.
Comment 1 Fedora End Of Life 2015-01-09 19:57:13 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 Fedora End Of Life 2015-02-17 17:19:15 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
bug.

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