https://bugs.kde.org/show_bug.cgi?id=524059

            Bug ID: 524059
           Summary: Select-All then Delete/Trash does not delete all
                    selected files
    Classification: Applications
           Product: gwenview
      Version First 26.04.3
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

DESCRIPTION
In browse mode, Gwenview failing to delete multiple files and failing to detect
and display the dimension of files until an F5 refresh is performed.  Possibly
related to bug 523000.

STEPS TO REPRODUCE
1.  Drag a dozen JPG files to a temporary folder, such as ~/Downloads, using
Dolphin, or sync them to the folder - doesn't seem to matter how the files get
there
2.  In Gwenview's browse mode, use control-A to select all
3.  Try to delete them (shift-del) or trash them (del)

OBSERVED RESULT
Only one file is deleted.  Continuing attempts to delete the group, deletes a
single file each time.   The order is predictable;  the first in the selection
is deleted.  Upon the second and subsequent deletions, the *second* remaining
selected file is deleted; until there is only one file left, at which point it
is deleted.  

EXPECTED RESULT
All files should be deleted.


SOFTWARE/OS VERSIONS
On Wayland,plasma shell 6.6.6 
Operating System: Kubuntu 26.04 LTS 
KDE Plasma Version: 6.6.6 
KDE Frameworks Version: 6.24.0 
Qt Version: 6.10.2 

ADDITIONAL INFORMATION
If I select all files by clicking the first then shift-clicking the last, the
delete works correctly.  this seems likely related to bug 523000, where
multiple file selections in Gwenview are not functioning as expected.

Potentially useful observation - while files are being created in the directory
I am working with (through any means) thumbnails are being created correctly,
but for many files the dimensions aren't displayed until I hit F5.  This is
happening regardless of the low resource usage mode setting.  I've replicated
all these symptoms on two machines which were built with brand new clean K26
installs last week.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to