Bug 363849

Summary: Gwenview Image View Does Not Change When Final Image Deleted and so Deletes Files Unexpectedly
Product: [Applications] gwenview Reporter: Gus Gustafson <efelthauser>
Component: generalAssignee: Gwenview Bugs <gwenview-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: critical CC: efelthauser, myriam, nate, xunilhcra
Priority: NOR    
Version: Other (add details in bug description)   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Gus Gustafson 2016-06-02 15:47:02 UTC
If you Have a Directory of images and other files, and you use Gwenview to delete images as you look at them, after you delete the last image in the directory (using the delete keys), Gwenview continues to display the final image in the directory. Yet, what it is actually "on" is a non-image file. So if you then hit 'delete' again, thinking it didn't work (ie, you have Dolphin set to not give delete confirmations), which is completely reasonable since the image continues to be displayed, you will actually delete the next non-image file, or files if you continue hitting it reapeatedly. This is very bad, as you can end up deleting a bunch of files you did not intend to without ever realizing it.
This needs to get fixed asap.
When the last image file in the directory is deleted, Gwenview should NOT continue to show that image. It should show the filename of the non-image file it currently has selected. Or better yet, don't select, and don't be able to act on, any sort of non-image files at all.

Reproducible: Always

Steps to Reproduce:
Delete last image file in directory.

Actual Results:  
Gwenview continues to display the last image, even though it was already deleted via Gwenview. Also, it will now select any non-image files, and cause you to delete them unexpectedly.

Expected Results:  
It should stop displaying the final image in directory after it is deleted.

I am using the regular Kubuntu 16.04 Repository version (4:15.12.3-0ubuntu1).
Comment 1 xunilhcra 2016-06-27 23:39:50 UTC
See also: https://bugs.kde.org/show_bug.cgi?id=355493
Comment 2 Nate Graham 2017-09-10 04:14:36 UTC

*** This bug has been marked as a duplicate of bug 355493 ***