Ctrl+A does not always select all contents of the visited folder (can lead to permanently lost work!)

Bug #1862541 reported by Linus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
Unknown
nautilus (Ubuntu)
Fix Committed
Low
Unassigned

Bug Description

The other day I wanted to move all the files in one folder over to another folder using the cut + paste method. I visited the source folder, pressed Ctrl+A (select all) followed by Ctrl+X (cut), and then browsed to the target folder and pressed Ctrl+V (paste). Then I went and deleted the source folder, which I reasonably assumed to now be empty. However, it turned out that not all the files had been moved, and that the remaining files had been deleted along with the original folder (which I deleted permanently with Shift+Del, I might add).

After some troubleshooting I've been able to determine the most likely cause. When visiting a folder, there is usually some delay during which the contents of the folder are read from disk and the thumbnails are being updated (for large folders this delay can be on the order of seconds). If Ctrl+A is pressed before this process has finished, only a subset of the files/folders are selected. Thus, I probably only cut/moved some of the files, and left the remaining files behind.

This is a very serious bug, as it can lead to permanent loss of work (as it did for me).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nautilus 1:3.26.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18
Uname: Linux 4.15.0-76-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 9 21:22:24 2020
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
InstallationDate: Installed on 2020-02-09 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

Revision history for this message
Linus (linus2) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report. That looks like an upstream issue, could you report it there?
https://gitlab.gnome.org/GNOME/nautilus/issues

Changed in nautilus (Ubuntu):
importance: Undecided → Low
Revision history for this message
Linus (linus2) wrote :
Changed in nautilus (Ubuntu):
status: New → Triaged
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
status: New → Fix Released
Changed in nautilus (Ubuntu):
status: Triaged → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.