Hi Nicolas,
apt indeed does inhibit reboots while upgrades go on to avoid an inconsistent
state.
If a lot of updates need to be applied that can take a while, but should not
hang forver.
Sadly but understandably this report is from after the reboot (logs are
rather short just after boot and seem not to show the initial issue), so
it does not have most of the logs that one would need to make
assumptions what happened.
AFAICS from these post reboot bug report qemu-block-extra is only in
this bug report as it likely was the one that was updated when it was
hard restarted. Due to that it is half upgraded as now shown in the now
present log as.
Setting up qemu-system-x86 (1:9.2.1+ds-1ubuntu5.2) ...
[1mdpkg: [0m error processing package qemu-block-extra (--configure):
the package is in a really inconsistent state; you should
reinstall it before attempting to configure it
To overcome this follow up symptom please consider to re-install it as
suggested, like
$ apt install --reinstall qemu-block-extra
If that fails please provide the output and what happened here.
Maybe for the sake of having it upfront, before you try that re-install run
$ dpkg --verify qemu-block-extra
Which would let us know where files are in an unexpected state.
If this fails again, that is a log that would be interesting as it might
hint at what was going on the first time.
---
But for the initial hang of unattended-upgrades / apt - that is kind of
as it is designed, unless if it was hanging infinitely long.
In the log we see that unattended upgrade seems to have been around qemu
as expected:
Start-Date: 2025-09-13 06:51:07
Commandline: /usr/bin/unattended-upgrade
Upgrade: qemu-system-x86:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-system-modules-opengl:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-system-modules-spice:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-utils:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-system-common:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-block-extra:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-system-data:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2),
qemu-system-gui:amd64 (1:9.2.1+ds-1ubuntu5, 1:9.2.1+ds-1ubuntu5.2)
In a perfect world all you'd have needed was wait, and if curious see in e.g.
`ps` or the dpkd log which package is currently handled.
Now the question really is was that really stuck and if so why?
Your try to restart unattended-upgrades and re-upgrade has stopped the
service, but not the ongoing upgrade - hence my assumption you've hit
the "de l'interface dpkg was locked by /usr/bin/python3.13 process with
pid 1340175" - it was still going on.
If we want to go down that route it is a apt/unattended-upgrade bug and we'd
need to see the logs of what happened before boot.
I can't see a qemu package issue yet, I'm adding apt/unattended-upgrade for
awareness there.
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: New => Incomplete
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2124213
Title:
package qemu-block-extra 1:9.2.1+ds-1ubuntu5.2 failed to
install/upgrade: le paquet est dans un état vraiment incohérent ; vous
devriez le réinstaller avant de tenter de le configurer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2124213/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
