Public bug reported:
While trying to unpack some .ARC files from a 1980s "shareware of the
month"-style 5.25" floppy disk, I got `lsar -t` to segfault and then
`unar`.
I was unable to trigger it in a brand new build made from a fresh
download of the upstream TheUnarchiverSource.zip archive, which would
suggest that simply upgrading the package may fix it.
However, identifying WHAT was fixed may be difficult because I was also
unable to trigger it when running under gdb to attempt a backtrace, and,
of the four .ARC files on the floppy disk, which ones work and which
ones segfault vary from run to run and `unar` may work while `lsar -t`
segfaults or vice-versa.
I suspect it's caused by reading from uninitialized memory.
The original archival tool reports success with no corruption for all of
them when run under DOSBox and since the DOS extractor is freeware and
the archives' contents are all either freeware or shareware (and the
entire floppy was just 360K), I'll attach them to the bug report in case
anyone wants to run their own testing.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: unar 1.10.1-2build7
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 17 13:57:52 2021
SourcePackage: unar
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: unar (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
** Attachment added: "Complete contents of the floppy disk (freeware DOS
extraction tool which always works and shareware archives which sometimes
segfault unar and `lsar -t`)"
https://bugs.launchpad.net/bugs/1943998/+attachment/5526002/+files/floppy_contents.zip
** Description changed:
While trying to unpack some .ARC files from a 1980s "shareware of the
- month"-style 5.25" floppy disk, I got `lsar -t` to segfault.
+ month"-style 5.25" floppy disk, I got `lsar -t` to segfault and then
+ `unar`.
I was unable to trigger it in a brand new build made from a fresh
download of the upstream TheUnarchiverSource.zip archive, which would
suggest that simply upgrading the package may fix it.
However, identifying WHAT was fixed may be difficult because I was also
unable to trigger it when running under gdb to attempt a backtrace, and,
of the four .ARC files on the floppy disk, which ones work and which
ones segfault vary from run to run and `unar` may work while `lsar -t`
segfaults or vice-versa.
I suspect it's caused by reading from uninitialized memory.
The original archival tool reports success with no corruption for all of
them when run under DOSBox and since the DOS extractor is freeware and
the archives' contents are all either freeware or shareware (and the
entire floppy was just 360K), I'll attach them to the bug report in case
anyone wants to run their own testing.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: unar 1.10.1-2build7
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 17 13:57:52 2021
SourcePackage: unar
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943998
Title:
`unar` and `lsar -t` sometimes segfault on certain files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unar/+bug/1943998/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
