Comment 5 for bug 81464

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