Version: (using Devel) OS: Linux Installed from: Compiled sources In ark under KDE 3, if I tried to open an archive file with a non-standard extension, ark would ask me what type of archive to open it as. Ark under KDE 4 does not do this. I have some files with extension CBR, which should be (according to the conventions of the extension) a RAR archive. In actuality, the files in question are ZIP archives that should (again, according to convention) have the extension CBZ. Ark under KDE 4 tries to open the files as RAR archives and predictably fails to show the contents of the archive. Ark under KDE 3 will say that the file has a non-standard extension and that the type of archive was determined to be ZIP, but I'm also given the option of opening the file as a different type of archive. Opening these files using ark under KDE 4 gave me the impression that the files had been corrupted. Only opening the files with the KDE 3 version of ark alerted me to the fact that the files were not corrupt, but simply had an incorrect extension. The non-standard extension warning is something that I would very much like to have back in the latest version of ark.
What version of Ark do you use? It might be that what you are describing has already been done in the trunk version, and will be released with KDE 4.2. What the trunk version does right now, is to first find the mimetype based on just the filename of the archive. If this can not be resolved, then it will try to look at the content of the file, and again try to resolve a mime type. If this also should fail, then it will ask the user what kind of file it is, like you describe. You say the cbr extension is really a zip file. I don't see how ark can have made misread that file so bad that it actually thinks it's a rar file. Unless the rar plugin .desktop file has been modified to include the cbr mime type. It should be the same case as with odt-files, which are also just normal zip-files with documents inside. Could you maybe upload one of these cbr files for me to try?
The bug in question, however, was already reported, but I still want to confirm the case that you have described above. *** This bug has been marked as a duplicate of bug 169376 ***
Created attachment 28525 [details] Test-case incorrectly extensioned CBR file.