Pamac doesn't always remove the db.lck file

[arbolis]

Since about around 5 months (more or less 3 months), pamac doesn't always remove /var/lib/pacman/db.lck.
I don't know exactly when this bug happens, but I can definitely say it has been introduced some months ago and since then, has never been fixed. I don't know the steps to reproduce the bug either.
For more information, browse the Manjaro forums and check out when lots of people started to report the "Unable to lock database" error.
They were all using pamac so that's definitely a pamac bug.

[prescott66]

I have this issue long time ago in Antergos. Devs tried many times to fix this, but i think without luck...it should be simply integrated automated deletion of db.lck file like Octopi manager have.

[jordanpavlov]

After I removed the lock for first time I habe not Seen it again. How offten dies it happen?

[arbolis]

In my case it happens almost every time between the Manjaro updates. Pamac won't show any update because of that file, and I get to know about a new update via the forum. So I remove the file and then Pamac tells me that there's an update. Sometimes I notice that the file hasn't be cleaned when I want to install or remove a program with Pamac, it simply can't.
If you hang on #manjaro on IRC you'll see like at least 1 person per day with this problem. It pops up so much that Manjaro team introduced a "fixit" bash alias that updates some stuff and remove the lock.
I think it would be very easy to know exactly when this bug was introduced by looking at the forum posts. So devs could revert the faulty patch.