xreader does not open some cbr files that it would have opened before
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 283
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
Distribution
Linux Mint 22.1
Package version
4.2.6
Frequency
Not Always
Bug description
File: RAR archive data, v2.0, os: Win32
xreader 4.2.6 in
Host: alfema Kernel: 6.11.0-28-generic arch: x86_64 bits: 64
Desktop: Cinnamon v: 6.4.8 Distro: Linux Mint 22.1 Xia
Error: ** (xreader:96612): WARNING **: 22:54:35.111: Fatal error reading 'foo1' in archive: Failed to decompress data: Prefix found
Same version and error in
Host: alfema Kernel: 5.15.0-142-generic x86_64 bits: 64
Desktop: Cinnamon 6.0.4 Distro: Linux Mint 21.3 Virginia
With
xreader 3.4.3 in
Host: alfema-VirtualBox Kernel: 5.15.0-41-generic x86_64 bits: 64
Console: pty pts/1 Distro: Linux Mint 21 Vanessa
Error: (xreader:17133): Atk-CRITICAL **: 20:24:48.220: atk_object_set_name: assertion 'name != NULL' failed
It does not occur in xreader 3.2.3, Mint 20.3
or with RAR archive data, v4, os: Win32, tested only on Mint 22.1.
If you need the CBR file, please indicate so that I can send it via private message or leave a link to download it. It is 12 MiB.
Steps to reproduce
Whenever you try to open that type of cbr.
Expected behavior
You should be able to open it as you did in previous versions.
Additional information
None
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no source file, test, or entry point. First obtain the affected CBR file and reproduce the “Prefix found” failure on xreader 4.2.6, comparing RAR v2 and v4 behavior; done means the affected RAR v2 CBR files open as they did in earlier versions and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100