buffer overflow during debootstrap --variant=fakechroot

Bug #2065775 reported by Ken Sharp
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mawk (Ubuntu)

Bug Description

Running a debootstrap fakechroot fails during mawk set up.

$ fakechroot fakeroot debootstrap --variant=fakechroot noble noble

Setting up mawk ( ...
*** buffer overflow detected ***: terminated
Aborted (core dumped)
dpkg: error processing package mawk (--configure):
 installed mawk package post-installation script subprocess returned error exit status 134

Same with Oracular.

A normal debootstrap (no variant) completes without error.

Could be a fakeroot fault. I will reassign if I figure out the cause.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: mawk
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed May 15 13:19:11 2024
 gcc-14-base 14-20240412-0ubuntu1
 libc6 2.39-0ubuntu8.1
 libgcc-s1 14-20240412-0ubuntu1
 libidn2-0 2.3.7-2build1
 libunistring5 1.1-2build1
 PATH=(custom, no user)
SourcePackage: mawk
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ken Sharp (kennybobs) wrote :
Revision history for this message
Ken Sharp (kennybobs) wrote (last edit ):

This occurs on Debian Testing and Unstable too when trying to debootstrap both Noble and Oracular, but not Debian Stable, Testing or Unstable.

Workaround is --exclude=mawk.

description: updated
Revision history for this message
Ken Sharp (kennybobs) wrote :

Stable 1.31-1.2
Testing 1.33-1
Unstable 1.34-1
Noble 1.33-1
Oracular 1.34-1

Stable 2.20.1+ds-15
Testing 2.20.1+ds-17
Unstable 2.20.1+ds-17
Noble 2.20.1+ds-15
Oracular 2.20.1+ds-15

Stable 1.0.128+nmu2+deb12u1
Testing 1.0.134
Unstable 1.0.134
Noble 1.0.134ubuntu1
Oracular 1.0.134ubuntu1

Note, however, that older versions of Ubuntu fail to fakechroot debootstrap due to other issues, so don't get this far in the process. It's difficult to work out when this issue was introduced.

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.