Posts: 24
Threads: 4
Joined: Jul 2025
Reputation:
0
10 hours ago
(This post was last modified: 9 hours ago by stevef.
Edit Reason: subject modified to aid search
)
============ Log ===========
E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5604 (apt-get)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
Countfoxx
Posts: 1,220
Threads: 13
Joined: Feb 2019
Reputation:
25
That message indicates that there was already a package management process running when a second one has tried to start.
A package manager requires exclusive access to update resources and will try to lock the resources while it is running to prevent another instance starting.
Usually all that is needed is to wait until the first process completes before running update/upgrade again.
The length of time the resource remains locked will be variable.
If the problem does not self-resolve after a while, shutdown, reboot and try again.
If the problem persists it is possible that something (like an interrupted update) may have broken the mechanism and more investigation will be required to clear the lock.
stevef
clueless
Posts: 1,220
Threads: 13
Joined: Feb 2019
Reputation:
25
If you initiate an update/upgrade and confirm the action, then yes, you need to wait for it to finish.
Most Linux Lite systems will show progress on screen. There are cases where the GUI does not show the progress, but in cases reported (so far) the final 'completed' window has always popped up at the end. This 'silent updating' has been investigated and seems to be associated with a 'divide by zero error' which kills the GUI progress window.
No complete explanation has been found as far as I am aware.
If you don't get the GUI progress AND the GUI complete message you may have something new.
stevef
clueless