Your message dated Sun, 5 Jul 2026 18:47:40 +0000
with message-id
<byapr05mb50934efee3ed672b1612860eb3...@byapr05mb5093.namprd05.prod.outlook.com>
and subject line Bug#1025833: Closing; please report to Ark upstream
has caused the Debian Bug report #1025833,
regarding libarchive13: random failure when opening RARv5 archives with password
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1025833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025833
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libarchive13
X-Debbugs-Cc: [email protected]
Version: 3.6.0-1
Severity: normal
Hi,
I am using Ark from KDE on Debian testing to open RARv5 archives (as
reported by `file` command) with password. However, randomly it can not
display archive contents. The failure rate is around 50% so it is not
difficult to trigger this.
When failing, Ark says in its GUI: "The archive is empty or Ark could
not open its content."
And on the command line it says:
$ ark foo.rar
ark.kerfuffle: Plugins run from the main thread should call directly
query->execute()
ark.part: No entry listed by the plugin
When opening archive works, the second line ("ark.part") is not displayed.
I have a sample file that I can send, but with it my email is refused…
As Ark package depends on libarchive, and as I do not have unrar package
on my system, I suppose the bug is in libarchive package, sorry if I am
wrong. Upstream changelog of libarchive version 6.2
(https://github.com/libarchive/libarchive/releases/tag/v3.6.2) mentions
that an issue has been fixed with RARv5 archives but I can not tell if
it is the same thing.
I can report this issue upstream if you want, either in libarchive or Ark.
Regards,
Yvan
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages libarchive13 depends on:
ii libacl1 2.3.1-1
ii libbz2-1.0 1.0.8-5+b1
ii libc6 2.36-5
ii liblz4-1 1.9.4-1
ii liblzma5 5.2.8-0.0
ii libnettle8 3.8.1-2
ii libxml2 2.9.14+dfsg-1.1+b2
ii libzstd1 1.5.2+dfsg-1
ii zlib1g 1:1.2.11.dfsg-4.1
libarchive13 recommends no packages.
Versions of packages libarchive13 suggests:
pn lrzip <none>
-- no debconf information
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
It appears that the issue is more likely related to Ark.
Closing for now, report to the Ark folks to see if the issue is actually on
libarchive.
Thanks for the report. Feel free to reopen the bug report if any new
information comes up.
Gabriel
--- End Message ---
