Bug 1247043 - xarchiver problem with .zip file from dropbox, doesn't shows any compressed files or errors
Summary: xarchiver problem with .zip file from dropbox, doesn't shows any compressed f...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xarchiver
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-27 08:27 UTC by Paul DeStefano
Modified: 2016-07-19 17:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 17:12:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul DeStefano 2015-07-27 08:27:49 UTC
Description of problem:
When I open .zip file with Xarchiver, it doesn't show any compressed files inside the archive.  unzip and zipinfo work.

Version-Release number of selected component (if applicable):
xarchiver-0.5.2-21.fc22.x86_64

How reproducible:
May only occur with dropbox .zip archives.  /usr/bin/zip didn't create an archive that had the problem.

Steps to Reproduce:
1. post files to dropbox
2. download files in bulk from dropbox
3. try to open .zip file with xarchiver

Actual results:
.zip file opens as if it is an empty archive.

Expected results:
Xarchiver should show contents and be able to uncompress.

Comment 1 Fedora End Of Life 2016-07-19 17:12:11 UTC
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.