The Debian version actually says 16.04.2 which isn't listed in the bug tracker (more specifically: 4:16.04.2-1). When clicking my .rar file Ark opens with the following message: "The archive is empty or Ark could not open its content". I have unrar-free installed (version 1:0.0.1+cvs201), the also suggested "rar" package is not installed (unavailable). Running ` unrar-free myfile.rar --extract` works fine. Reproducible: Always Actual Results: Error message is shown. Expected Results: Open the rar file.
Forgot to add: thank you for the great work, I've been using Ark for probably over a decade and have never found the need to look for any other program. It took me quite a while to get used to the default behavior of "extract to sub-folder or not" but once I got it it makes perfect sense (if the content is already contained in a folder then the default is to extract to the given path directly). This is a very minor issue for me because I can just run the given command instead but for less technical users this means they probably can't open any RAR file at all, which could actually be a major/grave issue instead considering it's still a very popular format. Feel free to change the severity accordingly and once again thank you for the awesome work developing/maintaining this KDE-quality-level application, promoting KDE as the ultimate open-source standard of quality!
Hi, support for unrar-free was dropped a while ago. Ark 16.04 has introduced support for unar [1], which is what we recommend as free RAR backend. So a simple 'apt-get install unar' should allow you to extract RAR archives using Ark. If not, please tell us. [1]: https://packages.debian.org/stretch/unar
Thank you, I will write a Debian-specific bug so the maintainer can fix the dependencies. Thank you for the quick reply and excellent work on the ark package.
All right, closing as downstream.
For completeness sake here is the Debian bug report. The fix has been submitted already. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829265
*** Bug 380984 has been marked as a duplicate of this bug. ***