Public bug reported:
[Summary]
Running 'apt why' on a non-existent or legacy package name causes a
segmentation fault in APT version 3.1.6ubuntu2 on Ubuntu 25.10 (Questing
Quokka).
[Steps to reproduce]
1. Open terminal on Ubuntu 25.10.
2. Run command: apt why libasound2
(Note: libasound2 is a legacy package name, replaced by libasound2t64 in this
release).
[Expected result]
APT should report that the package cannot be found or provide dependency
information without crashing.
[Actual result]
Segmentation fault (core dumped).
[Technical Details]
- OS: Ubuntu 25.10 (Questing Quokka)
- APT version: 3.1.6ubuntu2
- Stack trace points to: APT::Solver::InternalCliWhy in libapt-pkg.so.7.0
- Querying the new package name 'libasound2t64' works as expected, but the
legacy name triggers the crash.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: apt 3.1.6ubuntu2
Uname: Linux 6.19.4-x64v2-xanmod1 x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Sat Feb 28 09:10:06 2026
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2142922
Title:
apt why results in Segmentation fault in InternalCliWhy on Ubuntu
25.10 (Questing Quokka)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2142922/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
