Update manager Instruction cannot be carried out

Bug #81464 reported by Michael Wood on 2007-01-25
6
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Wishlist
Unassigned

Bug Description

Binary package hint: update-manager

The update manager had a problem doing a dist-upgrade, a notice came up saying to resolve this please type in a terminal "sudo apt-get dist-upgrade" or something to that affect.

The problem here is that the update manager application still has a lock on:

E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

the instructions need not to be a part of update-manager in some way so that you can close it to perform the instructions. You would still want the instructions open to be able to copy from them into your terminal.

John Vivirito (gnomefreak) wrote :

Thanks for your report. Your idea might get more attention and have the possibility of being implemented if you submit a specification for it. First check whether the idea is already registered <https://launchpad.net/ubuntu/+specs>, and if so, contact the specification's drafter about your ideas. Otherwise, you can start writing a spec yourself. <https://wiki.ubuntu.com/FeatureSpecifications>

Changed in update-manager:
importance: Undecided → Wishlist
Sebastian Heinlein (glatzor) wrote :

John? What's up? This is an error report :)

Changed in update-manager:
assignee: nobody → glatzor
status: Unconfirmed → Confirmed
John Vivirito (gnomefreak) wrote :

This has been fixed already. this was a normal problem but as i recall it was fixed.
This first paragraph threw me off when i made above comment.
Most likely the cause was either you had dpkg/apt already running or synaptic open or it was doing it auto update what is in a cron process. This bug is really old can you please confirm this is no longer an issue?

Michael Wood (x3n) wrote :

Sorry for not being clear.

You are correct John, the cause is that dpkg had an existing lock, this lock exists from update manager. Which means that the user can not perform the instruction that they are prompted to do via the popup window.

The Scenario:

1) User goes to dist upgrade via update manager
** dpkg now locked **
2) problem occurs with upgrade
3) popup error message is run with the message that the user should go to a terminal and instigate dpkg manually through "sudo apt-get/dpk whatever"
4) User gets error message:
E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

Having moved a "gui orientated" user to the terminal they then panic or don't realise that the command has not been successful

when the popup comes up it needs to have the prerequisite of having released the lock on dpkg.

This bug is only fixed when either the lock is removed when the error message + instructions are put up or if all these types of errors are now handled by update-manager.

Thanks

On 03/11/2009 02:02 PM, Michael Wood wrote:
> Sorry for not being clear.
>
> You are correct John, the cause is that dpkg had an existing lock, this
> lock exists from update manager. Which means that the user can not
> perform the instruction that they are prompted to do via the popup
> window.
>
> The Scenario:
>
> 1) User goes to dist upgrade via update manager
> ** dpkg now locked **
> 2) problem occurs with upgrade
> 3) popup error message is run with the message that the user should go to a terminal and instigate dpkg manually through "sudo apt-get/dpk whatever"
> 4) User gets error message:
> E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
> E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
>
> Having moved a "gui orientated" user to the terminal they then panic or
> don't realise that the command has not been successful
>
> when the popup comes up it needs to have the prerequisite of having
> released the lock on dpkg.
>
> This bug is only fixed when either the lock is removed when the error
> message + instructions are put up or if all these types of errors are
> now handled by update-manager.
>
> Thanks
>
You can set in gconf editer to make update manager not look for updates
this will handle your problem other wise it not realistic to add it to
update-manager its self. "mvo" would be the person to askse should be
assigned to this bug but if i run into him on IRC i will poke him to
find out best solution but i think the above is best we can really do
since update manager is intended to work that way.

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from Unforgiven III

Michael Vogt (mvo) wrote :

Thanks for the additional information on this bug.

This is fixed partly now in update-manager, when a problem happens during a release upgrade this bubble is no longer displayed (update-notifier is deactivated during release upgrades).

John Vivirito (gnomefreak) wrote :

Un assigning Sebatian, This is assuming because he asked for more info and assigned himself. It not the best practice to do that due to someone thinks that user is fixing the bug.

Changed in update-manager:
assignee: glatzor → nobody
Robert Roth (evfool) wrote :

Is this still an issue? The only place I see apt-get dist-upgrade in the instructions is in the update-manager-text and it exits after displaying the instructions. Update-notifier and Update-manager do not seem to contain any more references to the apt-get dist-upgrade command, so can this bug be closed?
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

Changed in update-manager (Ubuntu):
status: Confirmed → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers