Bug 1228645

Summary: Delete "All files" filter does not delete any files with some tar.* archive types
Product: Red Hat Enterprise Linux 7 Reporter: Vitezslav Humpa <vhumpa>
Component: file-rollerAssignee: David King <dking>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: mclasen, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: file-roller-3.14.2-8.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 06:40:39 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:
Embargoed:
Bug Depends On:    
Bug Blocks: 1295396, 1297830, 1313485    
Attachments:
Description Flags
Reproducible archive none

Description Vitezslav Humpa 2015-06-05 12:07:37 UTC
Created attachment 1035181 [details]
Reproducible archive

Description of problem:
Trying to delete all files via the delete dialog's 'All files' filter, keeps all files in for some archive types. These seem to be tar.* archives, reproduced with .tar, .tar.gz, .tar.xz and .tar.bz2.; .tar.lzo on the other hand got all files deleted, so did .zip and .war

Whether the dialog is spawned by context menu coming from a file or empty area doesn't seem to be of influence, the "All files" does not seem to work in any of the cases.

Version-Release number of selected component (if applicable):
file-roller-3.14.2-2.el7.x86_64

Steps to Reproduce:
1. Open i.e. any tar.gz file
2. Right click somewhere in the area and choose Delete
3. If not already chosen, choose the "All files" radio.
4. "Delete"

Actual results:
Nothing happens

Expected results:
Archive is empty

Additional info:
Attaching one of the archives this got reproduced with.

Comment 5 errata-xmlrpc 2016-11-04 06:40:39 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2452.html