When doing a “Full Upgrade” I got the lock status with the message
“Status: Waiting for configuration file prompt”
my distro is a 20.04: Description: Ubuntu 20.04.5 LTS (copied from lsb-release -a)
Please i need your support to fix this issue because I have it in two devices now!
(my previous post of this issue got no answers)
1 Like
Please show the output of
sudo apt update && sudo apt full-upgrade && sudo apt autopurge
1 Like
This is a bug in lubuntu-update-notifier. It is currently being fixed in Lubuntu 22.04 and Lubuntu 22.10, however 20.04 was originally left because it wasn’t known if it was really necessary to fix it there and Lubuntu 20.04 is close to end-of-life anyway.
When this happens, the easiest way to fix it is to forcibly shut down the system, turn it back on, then run:
sudo dpkg --configure -a && sudo apt update && sudo apt full-upgrade
This will finish the incomplete installation, then apply any new updates.
Thank you for reporting this, I’ll see what I can do to get the bug fixed in 20.04 as well. Also, as Lubuntu 20.04 is almost out of support, it may be wise to upgrade your system to 22.04 at the earliest possible convenience. Lubuntu 20.04 reaches its end-of-life date sometime in April 2023.
3 Likes
A word of warning - depending on what all got upgraded, forcibly shutting down your system during an upgrade could cause things to go wrong (for instance, if the kernel is being upgraded, you may find your system unable to boot when you do this). If you’re worried about this, you can terminate the upgrade by running sudo killall -9 aptd rather than forcibly shutting down the system.
In the event you find your system unable to boot, you can use the “Advanced Options for Ubuntu” menu in GRUB to select an older kernel, and that will likely work to boot your system so you can fix the upgrade.
I am actively working on patching this bug.
3 Likes
Hi, Hope your doing well =)
I would suggest adding the tag 22.04.
I just installed Lubuntu version 22.04 on an old laptop, Lenovo 3000 N200, and got the upgrade notification and decided to upgrade.
- It also got stuck on the mentioned spot.
- I managed to close the upgrade window and then opened a terminal prompt and performed the suggested command and got the message.
:~$ sudo dpkg --configure -a && sudo apt update && sudo apt full-upgrade
dpkg: error: dpkg frontend lock was locked by another process with pid 1287
Note: removing the lock file is always wrong, and can end up damaging the
locked area and the entire system. See <https://wiki.debian.org/Teams/Dpkg/FAQ>.
:~$ ps u --pid 1287
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1287 0.7 2.7 209408 110264 ? SNl 11:16 0:17 /usr/bin/python3 /usr/sbin/aptd
:~$ kill 1287
bash: kill: (1287) - Operation not permitted
:~$ sudo kill 1287
:~$ sudo dpkg --configure -a && sudo apt update && sudo apt full-upgrade
dpkg: error: dpkg frontend lock was locked by another process with pid 1287
Note: removing the lock file is always wrong, and can end up damaging the
locked area and the entire system. See <https://wiki.debian.org/Teams/Dpkg/FAQ>.
Proceeded to follow the instructions of following post:
:~$ sudo killall -9 aptd
[sudo] password for paui:
:~$ sudo dpkg --configure -a && sudo apt update && sudo apt full-upgrade
Setting up sddm (0.19.0-2ubuntu2.2) ...
Configuration file '/usr/share/sddm/scripts/Xsetup'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** Xsetup (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /usr/share/sddm/scripts/Xsetup ...
Setting up libfwupd2:amd64 (1.7.9-1~22.04.1) ...
Setting up pipewire-bin (0.3.48-1ubuntu3) ...
Setting up software-properties-common (0.99.22.4) ...
Setting up apport (2.20.11-0ubuntu82.3) ...
apport-autoreport.service is a disabled or a static unit, not starting it.
Setting up dbus-user-session (1.12.20-2ubuntu4.1) ...
Setting up plasma-discover (5.24.7-0ubuntu0.1) ...
Installing new version of config file /etc/xdg/autostart/org.kde.discover.notifier.desktop ...
Setting up ure (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up plasma-discover-backend-snap (5.24.7-0ubuntu0.1) ...
Setting up pipewire:amd64 (0.3.48-1ubuntu3) ...
Setting up libfwupdplugin5:amd64 (1.7.9-1~22.04.1) ...
Setting up fwupd (1.7.9-1~22.04.1) ...
Installing new version of config file /etc/fwupd/redfish.conf ...
fwupd-offline-update.service is a disabled or a static unit not running, not starting it.
fwupd-refresh.service is a disabled or a static unit not running, not starting it.
fwupd.service is a disabled or a static unit not running, not starting it.
Setting up plasma-discover-backend-fwupd (5.24.7-0ubuntu0.1) ...
Setting up software-properties-qt (0.99.22.4) ...
Setting up libreoffice-common (1:7.3.7-0ubuntu0.22.04.1) ...
Replacing config file /etc/libreoffice/registry/main.xcd with new version
Setting up libreoffice-core (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-math (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-gtk3 (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-draw (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-help-common (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-impress (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-qt5 (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-base-core (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-help-en-us (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up python3-uno (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-calc (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up libreoffice-writer (1:7.3.7-0ubuntu0.22.04.1) ...
Setting up linux-image-5.15.0-58-generic (5.15.0-58.64) ...
I: /boot/vmlinuz is now a symlink to vmlinuz-5.15.0-58-generic
I: /boot/initrd.img is now a symlink to initrd.img-5.15.0-58-generic
Setting up linux-modules-5.15.0-58-generic (5.15.0-58.64) ...
Setting up linux-modules-extra-5.15.0-58-generic (5.15.0-58.64) ...
Setting up linux-image-generic (5.15.0.58.56) ...
Setting up linux-generic (5.15.0.58.56) ...
Setting up python3-distupgrade (1:22.04.15) ...
Setting up ubuntu-release-upgrader-core (1:22.04.15) ...
Setting up python3-update-manager (1:22.04.10) ...
Setting up ubuntu-release-upgrader-qt (1:22.04.15) ...
Setting up update-manager-core (1:22.04.10) ...
Processing triggers for install-info (6.8-4build1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for fontconfig (2.13.1-4.2ubuntu5) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
Processing triggers for initramfs-tools (0.140ubuntu13.1) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-43-generic
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for libc-bin (2.35-0ubuntu3.1) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for ca-certificates (20211016ubuntu0.22.04.1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for shared-mime-info (2.1-2) ...
Processing triggers for linux-image-5.15.0-58-generic (5.15.0-58.64) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-58-generic
/etc/kernel/postinst.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Sourcing file `/etc/default/grub.d/lubuntu-grub-theme.cfg'
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/lubuntu-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-5.15.0-58-generic
Found initrd image: /boot/initrd.img-5.15.0-58-generic
Found linux image: /boot/vmlinuz-5.15.0-43-generic
Found initrd image: /boot/initrd.img-5.15.0-43-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows 7 on /dev/sda1
done
Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Ign:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Ign:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Ign:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Ign:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Err:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Temporary failure resolving ‘archive.ubuntu.com’
Err:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
Temporary failure resolving ‘security.ubuntu.com’
Err:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Temporary failure resolving ‘archive.ubuntu.com’
Err:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Temporary failure resolving ‘archive.ubuntu.com’
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy/InRelease Temporary failure resolving ‘archive.ubuntu.com’
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease Temporary failure resolving ‘archive.ubuntu.com’
W: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease Temporary failure resolving ‘security.ubuntu.com’
W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease Temporary failure resolving ‘archive.ubuntu.com’
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libflashrom1 libftdi1-2
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
language-selector-common libinput-bin libinput10 update-notifier-common
0 to upgrade, 0 to newly install, 0 to remove and 4 not to upgrade.
Afterwards the wireless connection stopped working so I decided to reboot and seems to be working ok for now.
So I guess that would be it. At least for now. Hope the feedback helps for the debugging process.
Thanks for the indications and the great support =)
Have a great day!
2 Likes
This is sadly expected behavior - while there is a fix for this bug in Lubuntu already, there’s no way to get it to apply before the bug is triggered. (We tried everything we could think of, and couldn’t get it to work perfect.) However, the bug fix we pushed also is able to repair things after this happens. The basic idea is that a user should be able to force their system to reboot and when they power it on next, the updater will simply fix things the next time it runs.
Even this isn’t quite perfect - there are some tricky edge cases where this doesn’t work perfectly (particularly if a kernel update comes through in the same update that triggers the bug - the user will have to boot into an earlier kernel if this happens), but it’s the best we could do with the situation - the apt package manager doesn’t provide any good way for us to replace the running Lubuntu updater during the update. In retrospect, it might have been possible to add functionality that also automatically kills a latent aptd process to prevent the need for a reboot or manual intervention, but that could potentially have caused more trouble than it was worth.
On the bright side, the same fix that was issued for Jammy and Kinetic has also been backported to Focal, and should be rolling out to users early next week.
3 Likes
Hi ArrayBolt3,
Thanks for the reply and the explanation.
First of all, many thanks for all the effort you and the team put into attempting to find the “perfect” solution. Good enough is that, good enough and this as an expected behavior I consider fine.
Second, the only thing I would suggest that may improve the users experience for future updates could be to inform the user in a simple manner.
This could be as simple as a hyperlink in the upgrading dialog box with the title “Troubleshooting” or “Help” for example.
This link could link to :
- a README file which describes the possible “known” issues with this specific upgrade
- a troubleshooting wiki
- this forum
Providing a more or less simple path to information is really valuable for the user. Stumbling upon the “correct” link when searching key words in the ocean of google results is not always easy.
If there was a mention of this issue in some readme file related to the upgrade which I didn’t see, I’m sorry I missed it.
Anyway, thanks for the feedback and all the hard work!
Have a great day!
3 Likes
I definitely agree it should be documented. Thanks, I’ll try and get that done at some point.
Sadly, I don’t think we can add a troubleshooting hyperlink to the upgrader for the same reason we can’t get the upgrader to fix and restart itself mid-update (apt just doesn’t provide the needed functionality).
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.