[Feature Request] Automatic dpkg --configure -a

Bug #1270541 reported by Michael Murphy
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
Confirmed
Wishlist
Unassigned

Bug Description

1) If /var/lib/dpkg/lock or /var/lib/apt/lists/lock is detected, ask if it is OK to remove these files before running apt-get.
2) If package installation was disrupted (example: power was lost / system crash), it should automatically run sudo dpkg-reconfigure -a instead of prompting to run it manually.

Tags: trusty
Michael Murphy (mmstick)
description: updated
tags: removed: amd64 apport-bug
Revision history for this message
Julian Andres Klode (juliank) wrote :

Summary:
1) No, you have a wrong understand of how it works.
2) Maybe

Details:
1)
It does not make any sense to remove lock files. They do not lock anything by being present. The locks are aqcquired using F_WRLCK write locks of fcntl() and are automatically released once the process ends. If something is locked, something is still running somewhere.

2)
You mean dpkg --configure -a, not dpkg-reconfigure -a.

summary: - [Feature Request] APT Unlock
+ [Feature Request] Automatic dpkg --configure -a
Revision history for this message
Michael Murphy (mmstick) wrote :

Actually no, it seems you didn't read #1 or fully comprehend the issue caused by it. It isn't that something is still running somewhere. As I stated, if power is lost while apt is running, on a reboot that file will still be there, and the owner of the system will be unable to use APT to install or upgrade packages until they manually delete that file.

Revision history for this message
Vlad Orlov (monsta) wrote :

#2 would be nice to have.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apt (Ubuntu):
status: New → Confirmed
Revision history for this message
Julian Andres Klode (juliank) wrote :

No, the files can exist and do not prevent APT from running. They exist on *every* system, which obviously includes mine as well. And they are not a problem. They do not prevent APT from doing anything. I explained to you precisely how APT's locking works. Maybe you remember things incorrectly.

And you did not say anything about reboots WRT to that anyway.

Revision history for this message
Alberto Salvia Novella (es20490446e) wrote :

Since what you submitted is not really a bug, or a problem, but rather an idea to improve Ubuntu, you are invited to post your idea in Ubuntu Brainstorm at http://brainstorm.ubuntu.com/ where it can be discussed, voted by the community and reviewed by developers.

Changed in apt (Ubuntu):
importance: Undecided → Wishlist
status: Confirmed → Invalid
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

brainstorm.ubuntu.com does not exist any more. It’s legitimate to propose ideas for improvement as bug reports, though it’s better to focus on the problem and leave open the possibility that there are other solutions.

Changed in apt (Ubuntu):
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.