apt-config crashed with SIGSEGV in _int_malloc()

Bug #2028454 reported by Bernard Stafford
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: apt 2.7.2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckMismatches: ./casper/minimal.fr.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.481
Date: Sun Jul 23 09:14:39 2023
ExecutablePath: /usr/bin/apt-config
JournalErrors:
 Jul 23 09:14:31 hostname kernel: overlayfs: fs on '/tmp/tmpc4daggpg/root.dir' does not support file handles, falling back to xino=off.
 Jul 23 09:14:35 hostname kernel: overlayfs: fs on '/tmp/tmpkuua06i6/root.dir' does not support file handles, falling back to xino=off.
 Jul 23 09:14:37 hostname kernel: overlayfs: fs on '/tmp/tmpkuua06i6/root.dir' does not support file handles, falling back to xino=off.
 Jul 23 09:14:37 hostname kernel: overlayfs: lowerdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior.
 Jul 23 09:14:40 hostname pipewire[1573]: spa.alsa: front:0: (0 missed) impossible htimestamp diff:-8420
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230723)
ProcCmdline: apt-config shell TRUSTEDPARTS Dir::Etc::TrustedParts/d
ProcEnviron:
 LANG=
 LC_MESSAGES=
 PATH=(custom, no user)
 SHELL=/bin/sh
SegvAnalysis:
 Segfault happened at: 0x7fd06012f111 <_int_malloc+737>: cmp 0x10(%r8),%rdx
 PC (0x7fd06012f111) ok
 source "0x10(%r8)" (0x69efc653158d0b5d) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: apt
StacktraceTop:
 _int_malloc (av=av@entry=0x7fd060287c80 <main_arena>, bytes=bytes@entry=472) at ./malloc/malloc.c:3994
 __GI___libc_malloc (bytes=bytes@entry=472) at ./malloc/malloc.c:3297
 __fopen_internal (is32=1, mode=0x7fd0604878c3 "r", filename=0x5579117a9860 "/usr/share/dpkg/tupletable") at ./libio/iofopen.c:65
 _IO_new_fopen (filename=0x5579117a9860 "/usr/share/dpkg/tupletable", mode=0x7fd0604878c3 "r") at ./libio/iofopen.c:86
 std::__basic_file<char>::open(char const*, std::_Ios_Openmode, int) () from /lib/x86_64-linux-gnu/libstdc++.so.6
Title: apt-config crashed with SIGSEGV in _int_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

Revision history for this message
Bernard Stafford (bernard010) wrote :
information type: Private → Public
Revision history for this message
Bernard Stafford (bernard010) wrote :

Screenshot of Apport crash findings

tags: removed: need-amd64-retrace
Revision history for this message
Julian Andres Klode (juliank) wrote :

The bug report description seems unrelated to the bug report, the reported crash is a crash in apt while trying to open "/usr/share/dpkg/tupletable". As we can see in the stack trace, the call arguments all make sense.

So either there's a weird bug in libc6, apt is corrupting the memory prior to that call (but then the stack trace usually doesn't look that clean) or your RAM is damaged. Consider running memtest86+ to check your RAM.

Changed in apt (Ubuntu):
status: New → Incomplete
description: updated
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2028454

tags: added: iso-testing
Revision history for this message
Leó Kolbeinsson (leok) wrote :

Tested Ubuntu Mantic Daily ISO dated 23-07-2023 and unable to reproduce the bug.

Test Info:

ASUS Pro H610M-C i7-12700 Motherboard,32GB,Intel UHDGraphics 770,Intel 219-V GB Ethernet,1TB Intel SSD
Testcase:UEFI,no encryption,full disk,Internet - run in VirtualBox 7.0.6 ubuntu r155176 with 4096RAM enabled
Reboot,login,full disk utilized,run Firefox and stream media

Revision history for this message
Bernard Stafford (bernard010) wrote (last edit ):

Re-downloaded Ubuntu 23.10 Mantic Build 20230723 Tested in virtual box.
During the initial entering of information.
Entered the first letter of the password, Crash.
Just to make sure, restarted the OS. selected install.
reproduced bug 2nd time, Crash
Entered information until first letter of password, Crash -
White Blank installer page.
My RAM is not damaged MEMTest: 24 cores @ 64GB RAM: Errors/None 3 hours
I have RAM check during boot of my OS. Okay
Ubuntu 22.04 LTS Minimal installed just fine.

Revision history for this message
Julian Andres Klode (juliank) wrote :

This bug is about a specific crash in apt-config, not about installer crashing during password entry, please use the other bug for that.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for apt (Ubuntu) because there has been no activity for 60 days.]

Changed in apt (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.