Hey guys
I just installed LM on a new machine and after launching the drive manager I got stuck with this message on the terminal.
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
Now I cant download new software or upgrade them.
ive tried to kill the process using kill 2068 but «operation not permitted. I also tried the command «systemctl disable packagekit» but it doesnt seem to change things.
i am a bit lost now and I would be very happy to get some direction on hoz to get back on track and enjoy the ride with my new machine.
Thank so much
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions use the other forums in the support section.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
Try:
Code: Select all
sudo killall apt apt-get Re: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
sudo killall apt apt-get didnt work
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2191 (packagekitd)
Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2191 (packagekitd)
Last edited by SMG on Wed Aug 31, 2022 2:13 pm, edited 1 time in total.
Reason: Removed partial duplicate of message for clarity in the post.
Reason: Removed partial duplicate of message for clarity in the post.
Re: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
If you reboot it should remove the lock. If not, after the reboot, do:
Code: Select all
sudo rm -v /var/lib/dpkg/lock-frontend
Re: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
no, don't just remove the lock. Make sure the offending process (in this case,sleeper12 wrote: ⤴Wed Aug 31, 2022 3:51 pmIf you reboot it should remove the lock. If not, after the reboot, do:
Code: Select all
sudo rm -v /var/lib/dpkg/lock-frontend
packagekitd) isn't running first ...Re: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
Correct, but a reboot should stop it from running. I admit though, I stated it poorly. 
Re: Waiting for cache lock: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 2068 (packagekitd)
Yeah, that packagekit process is kicked off by (as I recall) cron / systemd-timer (whatever). I think at one time that it had something like an explicit "@reboot" job; in addition to its standard N-hourly scheduled kickoff.