Version: (using Devel) Installed from: Compiled sources I have several issues regarding Ark that forces me to use CLI solutions for extraction. For example, If I open a zip or tar.gz file with ark which has several files inside and no folders, click the extract, create a new folder and extract there, no file is extracted at all. The new folder remains empty. If I select all files and extract with "Selected files only" extraction works as expected. Here's another issue: If I open a compressed file which has several folders inside and simply click the extract button, files are extracted but the directory structure is ignored, all files are extracted in the same base directory (the location selected when extracting). Not having a working solution on compressed file management for KDE 4.1 is really a shame :( However, I understand that resources are limited and you're doing your best, so let's hope this will be ready for at least 4.2. (though it would be FAR better if this in a 4.1.x release, considering how critical this is). BTW, I'm using 4.1 SVN (from the 4.1 branch, not trunk) from the Gentoo KDE overlay.
I've notice that Dolphin has an option to browse through archives. This allow the user to go inside and copy the files from there "extracting" them, which works perfectly well. Maybe this should be enable my default to compensate this issue in 4.1? Al least the new user would have a way of extracting compressed archives without having to use the command line. Just an idea.
Please try to keep one problem one bug at a time. The two problems you describe are both already reported in two separate bugs, one (paths not being preserved when extracting) which is already fixed in trunk, and another (zip files and possibly other files sometimes do not extract), which is current my main priority. Marking this bug as a duplicate of that one. On a personal note, including "making Ark unusable" in the subject line is IMO unneccesary information. All bugs hinder program flow in some way another, and the severity field is the correct way to describe this. *** This bug has been marked as a duplicate of 166986 ***
Ok, my one intention of the title was make someone aware that this was critical, because I really didn't found a way to set the severity you mention. The only options I had were Bug and Crash, but this was no crash and this is not just a simple bug for me so that's why I put that on the title. Anyway, sorry for the mixed and duplicate bug. It's great to see someone is working on this :) Thanks for your work and to the Ark team!