[Bug 1989082] Autopkgtest regression report (glibc/2.35-0ubuntu3.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted glibc (2.35-0ubuntu3.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

linux-aws-6.2/6.2.0-1007.7~22.04.1 (arm64)
linux-azure-6.2/6.2.0-1007.7~22.04.1 (arm64)
linux-oracle-5.19/5.19.0-1025.28~22.04.1 (arm64)
mysql-8.0/8.0.33-0ubuntu0.22.04.2 (s390x)
ubiquity/22.04.19 (amd64, arm64, armhf, ppc64el)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#glibc

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1989082

Title:
  execute bit is missing on libc.so.6

Status in glibc package in Ubuntu:
  In Progress
Status in glibc source package in Jammy:
  Fix Committed
Status in glibc source package in Kinetic:
  Won't Fix
Status in glibc source package in Lunar:
  Won't Fix

Bug description:
  [Impact]
  Starting with Ubuntu 22.04 the execute bit is no longer set on /lib/x86_64-linux-gnu/libc.so.6. This causes trouble for some scripts that try to determine the glibc version by executing this file, for instance the LSF scheduler.

  [Proposed fix]

  Adjust the build system to chmod the library after the fixperms stage.
  This has been fixed in Debian, although it's not easily cherry-
  pickable.

  [Test plan]

  Run the following script:

  ```
  #!/bin/bash

  for glibc in `ldconfig -p | grep libc.so.6 | sed 's/.*=>//'`
  do
      if [ -x "$glibc" ] ; then
          $glibc >/dev/null 2>&1
          if [ "$?" != "0" ] ; then
              continue
          fi
          _libcver=`$glibc 2>/dev/null | grep "GNU C Library" | awk '{print $10}' | awk -F. '{print $2}' | sed 's/,//'`
      fi
      if [ "$_libcver" != "" ] ; then
          echo "GLibc minor version is $_libcver"
          break
      fi
  done
  if [ "$_libcver" = "" ] ; then
      echo "Cannot figure out the GLibc version."
      exit 1
  fi
  ```

  On Focal, it prints out the following:
    GLibc minor version is 31

  On Jammy:
    Cannot figure out the GLibc version.
  Expected:
    GLibc minor version is 35

  [Regression potential]

  This change is fairly minimal, but could expose bugs in codepaths that
  were depending on the system version of glibc and were thus far
  dormant in Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1989082/+subscriptions