Bug 1305796 - Fileroller is unable to correctly open compressed tar archive, if contains any extra character in suffix
Fileroller is unable to correctly open compressed tar archive, if contains an...
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: file-roller (Show other bugs)
22
All Linux
unspecified Severity medium
: ---
: ---
Assigned To: Matthias Clasen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-09 04:34 EST by Michal Toth
Modified: 2016-07-19 16:00 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 16:00:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michal Toth 2016-02-09 04:34:49 EST
Description of problem:
File-roller fails to open a file, which contains  "~" in its name. Under "fails" I mean, it does not extract correctly tar file, only decompresses the gun/bunzipped part.
In file-roller window, you would be shown only with <filename>.tar<special-char>1.


Version-Release number of selected component (if applicable):
file-roller-3.16.4-1.fc22.x86_64
file-roller-nautilus-3.16.4-1.fc22.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Open a web browser (I have tested only on firefox).
2. Click on archive to download and check open instead of save option [test.tar.gz]
3. Repeat again on same link. File will be stored with different suffix [test.tar-1.gz]
4. Opened file-roller has a problem with extracting the file.

Actual results:
Only decompressed file is shown. Archive is still "tarred".

Expected results:
Archive should be decompressed and extracted from tar archive. Content of archive should be visible.

Additional info:
This also might be a firefox's issue, but I think that file-roller should be capable of executing a "$file <archive>"
and finding out what to use, instead of failing on "untar".

$ ls /tmp/mozilla_<username>0/
test.tar-1.bz2  test.tar-2.bz2  test.tar.bz2

$ file test.tar.bz2
test.tar.bz2: bzip2 compressed data, block size = 900k

$ file test.tar-2.bz2
test.tar-2.bz2: bzip2 compressed data, block size = 900k

Same happens with test.tar~2.bz2 & test.tar2.bz2.
Comment 1 Fedora End Of Life 2016-07-19 16:00:40 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.