Bug 415270 - [unarchiver] Ark can't handle rar archives that contain files with square brackets (that is, "[" and "]") in the name
Summary: [unarchiver] Ark can't handle rar archives that contain files with square bra...
Status: RESOLVED FIXED
Alias: None
Product: ark
Classification: Applications
Component: plugins (show other bugs)
Version: 18.08.3
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Ragnar Thomsen
URL: https://bugs.debian.org/cgi-bin/bugre...
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-16 22:32 UTC by local10
Modified: 2022-08-07 01:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description local10 2019-12-16 22:32:35 UTC
Package: ark                             
Version: 4:18.08.3-1

Ark can't properly handle rar archives that contain files with square brackets (that is, "[" and  "]") in the name, and maybe some other chars as well.

How to test:

1. Take an existing valid epub file and rename it as "Test file - [Bracket Test].epub" (without quotes)

2. Put the above file into a rar archive with the name "Test file - [Bracket Test].epub.rar" (without quotes)

3. Open "Test file - [Bracket Test].epub.rar" wiht Ark, Ark shows "Test file - [Bracket Test].epub" inside.

4. Click on the "Test file - [Bracket Test].epub" inside Ark trying to view it

5. Ark will not be able to open the "Test file - [Bracket Test].epub" file and instead will show error: "The archive /tmp/ark-ZZyYJC/Test file - [Bracket Test].epub was not found"

6. Repeat steps 1-5 using "Test file - No Brackets in the name.epub" instead of "Test file - [Bracket Test].epub", it should work without any errors.

Thanks
Comment 1 local10 2019-12-20 18:53:22 UTC
It's disappointing that Ark has not not been fully functional for the last ten years or so. The last time it was working correctly for me was in KDE 3.5, after that it was mostly broken.
Comment 2 Elvis Angelaccio 2019-12-28 19:08:32 UTC
Please check which RAR plugin are you using.
Comment 3 local10 2020-01-10 21:22:09 UTC
Strange, I thought I was using unrar-free but it looks like I'm not using any:

# aptitude search rar | grepci ^i
i A libkpimitinerary-data - library for Travel Reservation information - arch independent data
i A libkpimitinerary5 - library for Travel Reservation information

How does Ark even unpack rar archives then? Thanks
Comment 4 Elvis Angelaccio 2020-01-12 17:23:33 UTC
You're probably using unarchiver then. Could you check?
Comment 5 local10 2020-01-14 01:24:05 UTC
(In reply to Elvis Angelaccio from comment #4)
> You're probably using unarchiver then. Could you check?

Doesn't look like I'm using unarchiver:

# aptitude search unarchiver
v   theunarchiver
Comment 6 local10 2020-01-14 11:01:20 UTC
OK, it looks like I'm unar:

# aptitude search unar | grepci ^i
i A unar - Unarchiver for a variety of file formats
Comment 7 local10 2020-01-19 15:40:53 UTC
More info:

1. Just found an "*.epub.rar" archive with square brackets in the name that I could successfully open and view with Okular from inside of Ark, even though the vast majority of the "epub.rar" files with square brackets in the name give me a "Could not open file" error. So the problem may not necessarily relate to the square brackets.

2. The actual error message for the majority of problem files (see steps 4 and 5 above) looks like this: "Could not open file /tmp/ark-ZZyYJC/Test file - [Bracket Test].epub" and for many "epub.rar" files it comes from Okular, which I use to read/view epub files. If I manually unpack the epub file from the rar archive and then try to view the unarchived epub with Okular it works fine.

HTH

# aptitude show unar
Package: unar                            
Version: 1.10.1-2+b4
State: installed

# aptitude show okular
Package: okular                          
Version: 4:17.12.2-2.2
State: installed
Comment 8 local10 2022-04-23 05:37:10 UTC
I think this issue can be closed now, I don't remember running into it recently, likely it was fixed. Even if it's not fixed I think it wasn't caused by the "[" and "]" brackets as I used to think back then, probably the brackets were just a coincidence.
Comment 9 local10 2022-08-07 01:48:46 UTC
Cannot reproduce it in:

Operating System: Debian 12 Bookworm GNU/Linux
KDE Plasma Version: 5.25.3
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.4
Kernel Version: 5.18.0-3-amd64 (64-bit)
Graphics Platform: X11