Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#10946 - pacman lock persists after reboot

Attached to Project: Pacman
Opened by Abhishek Dasgupta (abhidg) - Friday, 18 July 2008, 09:58 GMT
Last edited by Dan McGee (toofishes) - Friday, 18 July 2008, 12:04 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
pacman lock persists after reboot. This should not be the case
since it is clear that no package manager can be running when
the OS is booting.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Just do killall pacman; and then reboot the system.
This task depends upon

Closed by  Dan McGee (toofishes)
Friday, 18 July 2008, 12:04 GMT
Reason for closing:  Won't fix
Additional comments about closing:  See comment #2. Sorry we don't hold your hand and you can't follow simple instructions. Add something to your rc.local if you really care, its a bash one-liner.
Comment by Abhishek Dasgupta (abhidg) - Friday, 18 July 2008, 09:59 GMT
The easiest solution would probably be to add
a rm /var/lib/pacman/db.lck into the startup or shutdown scripts.
Comment by Glenn Matthys (RedShift) - Friday, 18 July 2008, 10:03 GMT
Pacman CLEARLY says what to do when the lock file is in place and you're trying to run a second pacman instance or when the previous pacman instance failed somehow, like a segfault.
Comment by Abhishek Dasgupta (abhidg) - Friday, 18 July 2008, 10:09 GMT
It's true that pacman says what to do, and it's certainly true
that it shows this message because the previous pacman instance
failed somehow (as I said - by using killall); but there's no reason
why it should show this message after a clean boot.

Even if pacman crashed on an earlier session; since this session
is fresh - there's no reason to show this. Since the problem is resolved
by the user removing /var/lib/db/pacman.lck anyway and then re-running
pacman, the message does not help much. It does help (and is necessary)
when there's *really* another instance running ... but as I said, this
cannot be the case when the OS is starting.
Comment by Greg (dolby) - Friday, 18 July 2008, 10:53 GMT
  • Field changed: Attached to Project (Arch Linux → Pacman)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Dan McGee (toofishes)
Pacman has its own section in the bugtracker. Im with Redshift on this one bug the pacman developers will definately know better.

Loading...