Bug 2190380 - Nautilus view is not showing the real contents properly after removing file/sub-folder
Summary: Nautilus view is not showing the real contents properly after removing file/s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk4
Version: 38
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kalev Lember
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-28 08:38 UTC by Milan Zink
Modified: 2023-05-03 10:27 UTC (History)
6 users (show)

Fixed In Version: gtk4-4.10.3-2.fc38
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 10:27:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gtk merge_requests 5873 0 None merged Merge branch 'wip/otte/trelistmodel-fixage' into 'main' 2023-05-02 06:21:25 UTC

Description Milan Zink 2023-04-28 08:38:59 UTC 
Nautilus view is not showing the real contents properly after removing file/sub-folder.

Items that were deleted are still displayed and existing items are hidden behind the deleted item names.

It's obvious from attached screencast.

You need to user Ctrl+R to refresh the view.

Reproducible: Always

Steps to Reproduce:
1.Create several files or folder in a folder
2.Move/delete some of the files/folders
3.See the results
Actual Results:  
Deleted items are 'visible'. Remaining items are hidden/not visible. Refresh view is required to get actual directory contents.

Expected Results:  
Folder view should properly refresh and show the actual contents after item deletion.
Comment 2 Ondrej Holy 2023-05-02 06:21:26 UTC 
This is a bug in GTK, see https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941.
Comment 3 Ondrej Holy 2023-05-03 10:27:09 UTC 
It should be already fixed in gtk4-4.10.3-2.fc38 (https://bodhi.fedoraproject.org/updates/FEDORA-2023-e3b09fcca9).
Note You need to log in before you can comment on or make changes to this bug.