CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I clicked an encrypted 7z file in the Files Manager, it did not ask for the password but returned the error "empty archive". Can anyone help?
Since you provide no details at all, no. You don't say how big this file is (does it actually HAVE data in it??), what you're clicking on, in what program, etc.
I clicked on the encrypted 7z file in the Files Manager (Dolphin). The file size is 8KB, and it has data in it.
8KB for a 7z file?? Are you *SURE* it has data in it?? And have you tried typing in "7z e <filename>.7z" at the command line??? Tried any other utilities like ark??
Sorry, but 8kb is incredibly small for an encrypted, compressed file that has actual data in it.
The command 7z and Ark can extract the encrypted 7z.
Then you need to go into KDE system settings (assuming you're using that, since you mention Dolphin..you don't actually tell us), and define what program to use for opening 7z files.
Sorry, but 8kb is incredibly small for an encrypted, compressed file that has actual data in it.
Quote:
Originally Posted by John VV
8 Kb is a bit on the very small size .
Are you sure this is correct ?
I don't understand these remarks. How big does a 7z file have to be before you guys accept it has actual data in it?
I can only assume you do not know how big a 7z file containing a single empty file is? Or an actually empty 7z file (achieved by deleting contents)?
Put differently: the only way an empty archive would appear to be 8KB is on a filesystem with a non-default block size and using a tool that displays disk usage rather than file size. (Such a case is unlikely but could be confirmed with "ls" or "stat".)
An 8 KB archive could easily contain anything from 8,000 bytes to 200,000 bytes of actual data, depending on the file types and compressability.
(This thread has a compression ratio of ~14% - it shrank from ~204KB to ~15KB, whilst three similar-to-each-other HTML files in my home directory had a ratio of ~4% - they shrunk from ~129KB to ~5KB.)
For the record, an actually empty 7z archive is 32 bytes, and Ark will display the message "This archive is empty or Ark could not open its content." whilst for a manually corrupted encrypted 7z file, Ark said "Loading the Archive FILENAME failed with the following error: Listing the archive failed."
I don't understand these remarks. How big does a 7z file have to be before you guys accept it has actual data in it? I can only assume you do not know how big a 7z file containing a single empty file is? Or an actually empty 7z file (achieved by deleting contents)?
Put differently: the only way an empty archive would appear to be 8KB is on a filesystem with a non-default block size and using a tool that displays disk usage rather than file size. (Such a case is unlikely but could be confirmed with "ls" or "stat".)
An 8 KB archive could easily contain anything from 8,000 bytes to 200,000 bytes of actual data, depending on the file types and compressability. (This thread has a compression ratio of ~14% - it shrank from ~204KB to ~15KB, whilst three similar-to-each-other HTML files in my home directory had a ratio of ~4% - they shrunk from ~129KB to ~5KB.)
For the record, an actually empty 7z archive is 32 bytes, and Ark will display the message "This archive is empty or Ark could not open its content." whilst for a manually corrupted encrypted 7z file, Ark said "Loading the Archive FILENAME failed with the following error: Listing the archive failed."
Understand totally, and it *COULD* have data in it...however, given the lack of information about where the file was obtained or any other pertinent details (post #1), the OP was asked to provide details. If it was downloaded from a website, it's entirely possible that it was corrupted, leading to errors in decompression, especially through Dolphin (which may not have the appropriate program associated to open 7z files by default). That is why I asked if it could be opened with ark or CLI. After the OP confirmed that it could, it was then suggested they associate the appropriate program to the file type in KDE.
Didn't think that given the lack of details from the OP it was inappropriate to confirm the file wasn't corrupted/zero bytes, and could actually be opened with another utility...how would you determine those things without asking???
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.