bash crashes in qemu-user environments (bionic)

Status changed to 'Confirmed' because the bug affects multiple users.

This has been fixed in Debian's bash (4.4.18-1.1)

Upstream's fix is not something we are keen to change.

 bash (4.4.18-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Build again with -no-pie as dropping it broke bash when run under
     qemu-user (with the same symptoms as #842037). Closes: #889869

The ROS (http://www.ros.org/) team uses qemu and docker to build native arm packages on our buildfarm. So this is a pretty significant roadblock for us as we prepare our next release based on bionic.

Many of our build processes rely on bash scripts, but even if we were to port all of those away from bash, it's an essential package and building an image without it is not really tenable. I have packaged bash with the -no-pie flag restored and that's working for us at the moment, but even incorporating that into our image baking process is not very clean (https://github.com/osrf/multiarch-docker-image-generation/pull/21).

If upstream's solution is not preferred. Is there another way to get bash working under qemu within the release window?

https://lists.gnu.org/archive/html/bug-bash/2018-02/msg00093.html

I'd like to know any progress from the qemu community. I feel like it would be long journey to address this problem.

This is upstream LP: #1749393

<jbicha> slangasek: can you explain the bash 4.4.18-1.1ubuntu1 removal?
<jbicha> because I used sbuild-launchpad-chroot to create an armhf chroot but it is stuck trying to update bash with an error that looks like Debian bug 889869
<slangasek> jbicha: PIE is a security feature, and shouldn't be disabled to work around a bug in qemu-user-static

Matthias, please investigate compiling bash using --without-bash-malloc (and then re-enabling PIE in Debian).

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865599#15

Status changed to 'Confirmed' because the bug affects multiple users.

I'm readding the rls-bb-incoming tag. Hope y'all don't mind. I just think this needs to be fixed for the 18.04 LTS release. It doesn't matter to me whether it's fixed/worked around in bash or in qemu as long as it works. :)

Another use case is in LTSP, where we debootstrap an armhf chroot to netboot raspberrypi clients.
This currently fails in 18.04.

qemu patch proposed at http://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04700.html

This bug was fixed in the package bash - 4.4.18-2ubuntu1

---------------
bash (4.4.18-2ubuntu1) bionic; urgency=medium

  * Merge with Debian; remaining changes:
    - skel.bashrc:
      - Run lesspipe.
      - Enable ls aliases.
      - Set options in ll alias to -alF.
      - Define an alert alias.
      - Enabled colored grep aliases.
    - etc.bash.bashrc:
      - Add sudo hint.

bash (4.4.18-2) unstable; urgency=medium

  * Revert the changes from the last upload.
  * Configure the normal build --without-bash-malloc as well.
    See http://lists.nongnu.org/archive/html/qemu-devel/2018-03/msg04700.html
    for the qemu fix. Closes: #865599. LP: #1751011.
  * Apply upstream patch 019.

bash (4.4.18-1.1) unstable; urgency=high

  * Non-maintainer upload.
  * Build again with -no-pie as dropping it broke bash when run under
    qemu-user (with the same symptoms as #842037). Closes: #889869
    Re-opens: #865599

 -- Matthias Klose <email address hidden> Wed, 04 Apr 2018 20:30:26 +0200