GNOME Bugzilla – Bug 490732
Does not support passworded .7z archive
Last modified: 2012-05-28 16:42:38 UTC
Please describe the problem: An error occurs when opening a passworded 7z archive in file-roller. 7-Zip (A) 4.51 beta Copyright (c) 1999-2007 Igor Pavlov 2007-07-25 p7zip Version 4.51 (locale=fr_CA.UTF-8,Utf16=on,HugeFiles=on,1 CPU) Enter password (will not be echoed) : Error: /tmp/myfile.7z is not supported archive Errors: 1 Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
To add some additional clarification, File Roller has two different error responses based on whether the header encryption option is used or not. Command to create header encrypted archive: 7za a -mhe=on -p test1.7z vi.pdf When opened in File Roller, the following error is returned immediately: "An error occurred while loading the archive" Command Line Output: 7-Zip (A) 4.51 beta Copyright (c) 1999-2007 Igor Pavlov 2007-07-25 p7zip Version 4.51 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,2 CPUs) Enter password (will not be echoed) : Error: /home/user/test1.7z is not supported archive Errors: 1 Command to create non-header encrypted archive: 7za a -p test2.7z vi.pdf File Roller opens the file alright, but the following error is returned when an extraction is attempted: "An error occurred while extracting files" Command Line Output: 7-Zip (A) 4.51 beta Copyright (c) 1999-2007 Igor Pavlov 2007-07-25 p7zip Version 4.51 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,2 CPUs) Processing archive: /home/agent86/test3.7z Enter password (will not be echoed) :Extracting vi.pdf Data Error in encrypted file. Wrong password? Sub items Errors: 1 Expected Results: File Roller prompts for archive password, and extracts archive accordingly. Bug is 100% reproducible and happens every time. Confirmed up to File Roller 2.20.3.
*** Bug 437471 has been marked as a duplicate of this bug. ***
*** Bug 378319 has been marked as a duplicate of this bug. ***
*** Bug 582917 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 588547 ***