Package dependancy issue with libglib2.0-0:i386

manicholls commented 2 years ago

How did you upgrade to 21.10? (Fresh install / Upgrade)

Upgrade from 21.04 that has been working fine

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

$ apt policy libglib2.0-0:i386 libglib2.0-0:i386: Installed: 2.68.4-1ubuntu1 Candidate: 2.68.4-1ubuntu1 Version table: *** 2.68.4-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu impish/main i386 Packages 100 /var/lib/dpkg/status

Issue/Bug Description: This just happened today on an apt upgrade. It may very well be an upstream issue that sorts itself out in a day or two but I wanted to report it here just in case.

Steps to reproduce (if you know):

standard apt update, apt upgrade steps.

Expected behavior:

should complete without errors

Other Notes: Fully spammy output below:

dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however: Package libmount1:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however: Package libmount1:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed No apport report written because MaxReports is reached already dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386: libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however: Package libmount1:i386 is not configured yet.

dpkg: error processing package libglib2.0-0:i386 (--configure): dependency problems - leaving triggers unprocessed dpkg: too many errors, stopping No apport report written because MaxReports is reached already Errors were encountered while processing:

jacobgkau commented 2 years ago

What is the output of apt policy libmount1:i386, and can you run sudo apt install libmount1:i386, sudo dpkg --configure libmount1:i386, or sudo dpkg-reconfigure libmount1:i386?

manicholls commented 2 years ago

$ apt policy libmount1:i386 libmount1:i386: Installed: 2.36.1-8ubuntu2 Candidate: 2.36.1-8ubuntu2 Version table: *** 2.36.1-8ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu impish-updates/main i386 Packages 100 /var/lib/dpkg/status 2.36.1-8ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu impish/main i386 Packages

all the reconfigure's didn't help, but going a level lower and doing sudo dpkg-reconfigure --configure libblkid1:i386 seems to have worked and then working my way up through libmount1:i386 did.

Unless others have had the same issue, it's probably safe to close it off as a non-issue.

jacobgkau commented 2 years ago

Unless others have had the same issue, it's probably safe to close it off as a non-issue.

You know your setup the best. If you think you might be able to tell us how to recreate the issue in a virtual machine, from a fresh install of 21.04 upgraded to 21.10 (or a fresh install of a 21.10 iso with older packages), we'd love to know the steps so we can address it in pop-upgrade or pop-shop. If not, since this doesn't appear to be a widespread issue, we can probably close it as a one-off for now.

libblkid1:i386 wasn't mentioned before. How did you find out that's what needed to be reconfigured, was it in the error message when trying to reconfigure libmount1:i386?

manicholls commented 2 years ago

libblkid1:i386 wasn't mentioned before. How did you find out that's what needed to be reconfigured, was it in the error message when trying to reconfigure libmount1:i386?

sorry, yes, this was found when trying to do the reconfigure.

At this point i can't reproduce so let's not allocate any more time to it.

Steinegal commented 2 years ago

Sorry for commenting on a closed issue, but ran in to this issue on my underused desktop today, doing a configure of libblkid1:i386 solved it for me as well. System was upgraded from 21.04 on release.

JL102 commented 2 years ago

I'm also encountering the issue, but I'm not familiar with dpkg. @Steinegal or @manicholls would you be willing to give an explanation for how that dpkg-reconfigure command fixed it? I tried:

sudo dpkg-reconfigure --configure libblkid1:i386 and get the following message:

Unknown option: configure
Usage: dpkg-reconfigure [options] packages
  -u,  --unseen-only        Show only not yet seen questions.
       --default-priority   Use default priority instead of low.
       --force          Force reconfiguration of broken packages.
       --no-reload      Do not reload templates. (Use with caution.)
  -f,  --frontend       Specify debconf frontend to use.
  -p,  --priority       Specify minimum priority question to show.
       --terse          Enable terse mode.

I also tried: sudo dpkg-reconfigure libblkid1:i386 and got the following:

/usr/sbin/dpkg-reconfigure: libblkid1:i386 is broken or not fully installed

Why did you specify go after libblkid1:i386, not libmount1:i386? I tried the same commands with libmount1:i386 but got the same messages.

EDIT: I managed to solve the issue by removing libmount1:i386: sudo apt remove libmount1:i386. Apt then performed an autoremove without errors, and then I ran sudo apt upgrade without errors. It appears that it automatically installed libmount1 (amd64 architecture, as opposed to x86) and everything seems to be working.

But if you guys can still explain the dpkg configure stuff, I'd greatly appreciate it.

OskarZyg commented 2 years ago

Same issue here, also used https://askubuntu.com/questions/1285751/dpkg-error-processing-package-libglib2-0-0i386 to help me, I essentially got it running by running:

dpkg configure -a command from the stack overflow question
sudo apt --fix-missing install
sudo apt purge libmount1:i386
sudo apt upgrade

if at any point the original error comes back, just run the dpkg command from the SO post and it fixes it.

fanuch commented 2 years ago

No need to follow breadcrumbs...

Answer from SO:

sudo dpkg --configure -a

followed by:

sudo apt --fix-broken install

In my case it was libc6 throwing:

libglib2.0-0:i386 ... libc6:i386 is not configured yet.

pop-os / beta

Package dependancy issue with libglib2.0-0:i386 #266