Version: 2.6.4 (using KDE KDE 3.5.5) Installed from: Ubuntu Packages OS: Linux When I want to extract multipart RAR archives password protected Ark says: "An error ocurred while trying to open the archive". The file to select for extraction is file.rar and the other are automatically selected, like archive.r00 and so on. I have tried "unrar e file.rar" and prompts for password and extracts the multipart archive correctly.
Exactly same scenario, exactly same problem. No dialog even shows to ask the password, just the error log which shows tha for each failed file a password is required - quite ironic :D
the problem appears also with single-part rar archives. With the command line tool rar or unrar it prompts for the password. see also https://bugs.launchpad.net/kdeutils/+bug/129729 for a example archive kubuntu 7.04 kde 3.5.6 ark 2.6.4 RAR 3.70 beta 1
*** This bug has been confirmed by popular vote. ***
It was time to be marked as new!
This seems to be a duplicate of #135099.
i confirm that with: kubuntu 8.10 kde 4.0.2 ark 2.10.999 rar 3.8b2-2 unrar e FILENAME works quite fine.
tested with trunk 905861: ark is be able to extract password protected rar files with encrypted headers. create multipart archive from ubuntu iso with following command: rar a -v10000k -hp ubuntu.rar ubuntu-8.10-desktop-amd64.iso and successful extract the 71 parts rar archive with ark
(In reply to comment #7) > tested with trunk 905861: > ark is be able to extract password protected rar files with encrypted headers. > > create multipart archive from ubuntu iso with following command: > rar a -v10000k -hp ubuntu.rar ubuntu-8.10-desktop-amd64.iso > > and successful extract the 71 parts rar archive with ark Then this issue can probably be closed
I could not extract single or multipart rar files created with -hp here with trunk. Ark just stands frozen waiting for command line input for the rar utility. Even though this bug is older, I'm marking it as a DUPLICATE of bug 188556 because the latter has got a more direct description of the problem. *** This bug has been marked as a duplicate of bug 188556 ***
Oh, and currently the problem only seems to happen with files encrypted with -hp. -p works fine.