Do release upgrade from 21.04 to 21.10 fails with libc-bin dependency on locales, i386 libc-bin version

Bug #1947176 reported by Vipul
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have locales installed and i386 architecture installed

$ dpkg --print-foreign-architectures
i386

Whenever I try to upgrade from the upgrade fails at libc-bin installation, which leaves system in a broken stage. I am able to recover with btrfs snapshot.

For locales expect version 2.34, and bin is still from 21.04 2.33 version. I tried removing locales and doing upgrade and then libc-bin fails because the i386 version of files are at 2.33 version.

Revision history for this message
Vipul (vipul-bhandari) wrote :
Download full text (3.4 KiB)

After removing both locales and i386 packages, I still get error:

Preparing to unpack .../libc6_2.34-0ubuntu3_amd64.deb ...
Checking for services that may need to be restarted...
Checking init scripts...
Checking for services that may need to be restarted...
Checking init scripts...
Stopping some services possibly affected by the upgrade (will be restarted later):
  cron: stopping...done.

Unpacking libc6:amd64 (2.34-0ubuntu3) over (2.33-0ubuntu5) ...

Progress: [ 38%]
Setting up libc6:amd64 (2.34-0ubuntu3) ...
/usr/bin/perl: symbol lookup error: /usr/local/lib/AppProtection/libAppProtection.so: undefined symbol: _dl_sym, version GLIBC_PRIVATE
dpkg: error processing package libc6:amd64 (--configure):
 installed libc6:amd64 package post-installation script subprocess returned error exit status 127
/usr/bin/python3: symbol lookup error: /usr/local/lib/AppProtection/libAppProtection.so: undefined symbol: _dl_sym, version GLIBC_PRIVATE
                                                                                                                                         Errors were encountered while processing:
 libc6:amd64
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)

Could not install the upgrades

The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).

Setting up libc6:amd64 (2.34-0ubuntu3) ...
/usr/bin/perl: symbol lookup error: /usr/local/lib/AppProtection/libAppProtection.so: undefined symbol: _dl_sym, version GLIBC_PRIVATE
dpkg: error processing package libc6:amd64 (--configure):
 installed libc6:amd64 package post-installation script subprocess returned error exit status 127
dpkg: dependency problems prevent configuration of libc6-dev:amd64:
 libc6-dev:amd64 depends on libc6 (= 2.34-0ubuntu3); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing package libc6-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc-dev-bin:
 libc-dev-bin depends on libc6 (>> 2.34); however:
  Package libc6:amd64 is not configured yet.
 libc-dev-bin depends on libc6 (<< 2.35); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing package libc-dev-bin (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libc6-dbg:amd64:
 libc6-dbg:amd64 depends on libc6 (= 2.34-0ubuntu3); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing package libc6-dbg:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent processing triggers for man-db:
 man-db depends on libc6 (>= 2.33); however:
  Package libc6:amd64 is not configured yet.

dpkg: error processing package man-db (--configure):
 dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for libc-bin:
 libc-bin depends on libc6 (>> 2.33); however:
  Package libc6:amd64 is not configured yet.
 libc-bin depends on libc6 (<< 2.34); however:
  Version of libc6:amd64 on system is 2.34-0ubuntu3.

dpkg: error processing package libc-bi...

Read more...

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.