usually the lock happens because another apt-using program is already open. Question: is Discover or MXPI open? Is mx-updater open or in use? Maybe Discover is it's in the midst of refreshing package lists to check for updates? Repo Manager might also be apt-using.Sparky wrote: Tue May 24, 2022 10:39 am...
BTW, trying to install Synaptic gives this error loop:Code: Select all
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held byWaiting for cache lock: Could not get lock /var/lib/dpkg/lock. It is held by
[ADDED: forgot that by default mx-updater is also not installed in MX KDE 21]