[Aptitude-devel] Bug#1035976: Bug#1035976: Bug#1035976: aptitude dies with SEGV

[Axel Beckert]

Hi Harald,

Harald Dunkel wrote:
> apparently it is not sufficient to just add the entry to sources.list.d.
> I had to update the local cache to make aptitude die.

Ok, another try:

# pbuilder update --autocleanaptcache
# pbuilder login
## apt install aptitude wget gpg ca-certificates
## wget -O- https://apt.releases.hashicorp.com/gpg | gpg --dearmor -o /etc/apt/trusted.gpg.d/hashicorp-archive-keyring.gpg
## echo "deb https://apt.releases.hashicorp.com bookworm main" > /etc/apt/sources.list.d/hashicorp.list
## apt update
Hit:1 http://debian.ethz.ch/debian sid InRelease
Get:2 https://apt.releases.hashicorp.com bookworm InRelease [12.9 kB]
Get:3 https://apt.releases.hashicorp.com bookworm/main amd64 Packages [84.4 kB]
## aptitude

TUI comes up. No crash.

> > * Do you have any custom settings for settings influencing aptitude's
> >    package display like "Aptitude::UI::Package-Display-Format" or
> >    "Aptitude::UI::Default-Grouping"?
> 
> No, I just have
> 
> 	# cat .aptitude/config

Looks harmless indeed.

> > * Under which locale settings does it happen for you?
> 
> On some systems I have set LANG=C or LANG=en_US.UTF-8, but I can reproduce
> this using
> 
> 	# locale
> 	LANG=
> 	LANGUAGE=
> 	LC_CTYPE="POSIX"
> 	LC_NUMERIC="POSIX"
> 	LC_TIME="POSIX"
> 	LC_COLLATE="POSIX"
> 	LC_MONETARY="POSIX"
> 	LC_MESSAGES="POSIX"
> 	LC_PAPER="POSIX"
> 	LC_NAME="POSIX"
> 	LC_ADDRESS="POSIX"
> 	LC_TELEPHONE="POSIX"
> 	LC_MEASUREMENT="POSIX"
> 	LC_IDENTIFICATION="POSIX"
> 	LC_ALL=
> 
> I doubt that this is related to the locale.

Thanks. I indeed think we can rule that out, too.

Then again, I'm out of ideas now, except for looking with strace where
the crash happens.

> > If you neither use any of these settings nor use a non-english locale,
> > is there any chance that you can install these packages (for
> > bookworm/sid, otherwise run "find-dbgsym-packages aptitude" from the
> > debian-goodies package) on one of the affected machines:
> > 
> > strace aptitude-dbgsym libapt-pkg6.0-dbgsym
> > libboost-iostreams1.74.0-dbgsym libbz2-1.0-dbgsym libc6-dbg
> > libcap2-dbgsym libcwidget4-dbgsym libelogind0-dbgsym libgcc-s1-dbgsym
> > libgcrypt20-dbgsym libgpg-error0-dbgsym liblz4-1-dbgsym
> > liblzma5-dbgsym libncursesw6-dbgsym libsigc++-2.0-0v5-dbgsym
> > libsqlite3-0-dbgsym libstdc++6-dbgsym libtinfo6-dbgsym libudev1-dbgsym
> > libuuid1-dbgsym libxapian30-dbgsym libxxhash0-dbgsym libzstd1-dbgsym
> > zlib1g-dbgsym
> > 
> 
> libelogind0? This breaks systemd.

Ah, sorry, didn'y notice that.

Wanted to avoid that you need to install debian-goodies for
find-dbgsym-packages so I ran "find-dbgsym-packages --all aptitude" on
one of my systems. Seems as if the output actually depends on which
alternatives have been chosen on the local system. Of course
libsystemd0-dbgsym is fine as well if you have libsystemd0 installed.

(I also doubt that all of these are really necessary. Probably
"aptitude-dbgsym libapt-pkg6.0-dbgsym libboost-iostreams1.74.0-dbgsym
libcwidget4-dbgsym libgcc-s1-dbgsym libncursesw6-dbgsym
libsigc++-2.0-0v5-dbgsym libxapian30-dbgsym" already suffice to cover
everything which might be involved in such a crash, especially since
it does not happen when downloading or accessing the package lists.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE