Ubuntu
update-manager package

first update fails after fresh hardy install

Bug #208112 reported by Shane O'Connell
2
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

I just did a fresh install of hardy from the beta alternate installer CD. The install went fine, but while upgrading the packages to their latest versions, I got a message saying an error had occurred, with a message in the log saying "dpkg: status database area is locked by another process". At the same time I also got a message saying restricted drivers were available for my hardware, I suspect that perhaps that was locking the dpkg database. After closing the error message and trying again the upgrade went through fine.

Here's the end of the log from the terminal:

Preparing to replace lsb-base 3.1-24ubuntu2 (using .../lsb-base_3.2-4ubuntu1_all.deb) ...
Unpacking replacement lsb-base ...
Setting up lsb-base (3.2-4ubuntu1) ...
(Reading database ... 95001 files and directories currently installed.)
Preparing to replace tzdata 2008a-1ubuntu1 (using .../tzdata_2008b-1ubuntu1_all.deb) ...
Unpacking replacement tzdata ...
Setting up tzdata (2008b-1ubuntu1) ...

Current default timezone: 'America/St_Johns'
Local time is now: Fri Mar 28 02:44:39 NDT 2008.
Universal Time is now: Fri Mar 28 05:14:39 UTC 2008.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

(Reading database ... 95010 files and directories currently installed.)
Preparing to replace util-linux 2.13.1-2ubuntu1 (using .../util-linux_2.13.1-3ubuntu1_i386.deb) ...
Unpacking replacement util-linux ...
Setting up util-linux (2.13.1-3ubuntu1) ...

(Reading database ... 95010 files and directories currently installed.)
Preparing to replace bsdutils 1:2.13.1-2ubuntu1 (using .../bsdutils_1%3a2.13.1-3ubuntu1_i386.deb) ...
Unpacking replacement bsdutils ...
dpkg: status database area is locked by another process
Log ended: 2008-03-28 02:44:42

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add all the files contained in /var/log/dist-upgrade/ to your bug report as separate attachments? Thanks in advance.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
Shane O'Connell (shaneoc) wrote :

Hmm, I don't seem to have any files at all in there..

Revision history for this message
Shane O'Connell (shaneoc) wrote :

It really looked like the "restricted drivers available" message happened at the exact same time as this error. Does that program access the dpkg database, perhaps to see if restricted drivers are already installed? If so, maybe the update manager should lock the dpkg database the entire time it is doing updates instead of unlocking and relocking it very quickly between installing updates, which it appears to be doing now.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

This is a package upgrade rather than a distribution upgrade so there won't be any logs in /var/log/dist-upgrade. Are you still able to reproduce the problem?

When you saw the message from the restricted drivers manager did you ask it to do anything such as install any restricted driversor take any other action? If so then this would indeed lock the dpkg database.

Revision history for this message
Shane O'Connell (shaneoc) wrote :

Hmm, well to reproduce the problem I'd have to completely reinstall ubuntu from the beta cd, and I can't really do that right now. :P

I didn't ask the restricted drivers manager to install anything though, I just clicked "close". Are you sure the only time it locks the database is when it's installing drivers and it doesn't when it checks it to see if driver packages are already installed, when it starts up?

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

I'm not sure by any means but I'm informed that the driver manager should be able to check to see what is installed and what is available with out needing to lock the database. Whether this is actually what it does is question for the developers of restricted drivers manager.

Another thing that could have a caused a lock is a second instance of synaptic/apt-get/dpkg running at the same time but I'm assuming that's not the case or you'd have noticed.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

Setting status to triaged for a developer to review

Changed in update-manager:
status: Incomplete → Triaged
Revision history for this message
PirateSmack (stevenlinuxuser) wrote :

I just did a fresh install of Hardy (not beta) today and got the same error

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in update-manager:
status: Triaged → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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