[Aptitude-devel] Bug#980035: aptitude: segmentation fault when starting aptitude

[Vincent Lefevre]

On 2021-01-13 12:04:57 +0100, Vincent Lefevre wrote:
> On 2021-01-13 11:24:33 +0100, Vincent Lefevre wrote:
> > A bundle is available for a limited time:
> > 
> >   https://www.vinc17.net/aptitude-segv.bundle
> > 
> > I can reproduce the crash (but not always) with
> > 
> >   aptitude-run-state-bundle aptitude-segv.bundle
> > 
> > on this machine and on another one.
> 
> When it doesn't crash, aptitude doesn't suggest any action.
> 
> But on a 3rd machine, which has the same aptitude version, but older
> versions of dependencies, aptitude never crashes, and I get:
> 
> [1(1)/...] Actions: 2 keeps, 1 upgrade
> e: Examine  !: Apply  .: Next  ,: Previous
> 
> and 'e' says:
> 
>                 Packages                          Resolve Dependencies
>   --\ Keep the following packages at their current version:                     
>     desktop-file-utils                         [0.26-1 (now, testing, unstable)]
>     gvfs-common                              [1.46.1-2 (now, testing, unstable)]
>   --\ Upgrade the following packages:
>     libmtp-common     [1.1.17-3 now, testing, unstable -> 1.1.18-1 experimental]
> 
> (suggesting to upgrade a package to experimental like that is
> incorrect, unless aptitude already broke the system).

The cause of this issue seems to be that aptitude-run-state-bundle
depends on the current system status, not just aptitude-segv.bundle.

-- 
Vincent Lefèvre <vincent at vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)