A thought about getting 2 updates running concurrently.
When I have not run the ubuntu computer recently (it is set up for my
wife at the moment), I tend to go to Update Manager and run it
manually. If it would also run automatically, and I do not notice
that it is already running, that could cause it to run twice.
Robert
(I am stuck with using this windows xp computer because of some
software I need to use. Ubuntu is so very much more efficient and
faster on a computer with similar hardware. If I could get everything
I want to work on ubuntu, I would abandon windows completely.)
On 21 February 2011 21:47, Olivier Tilloy <email address hidden> wrote:
> I can easily reproduce, on Maverick and Natty, by running concurrently
> two instances of /usr/share/software-center/update-software-center-
> agent.
>
> Fixing the symptom would be trivial too: if the temporary DB file
> already exists, or if we catch a DatabaseLockError, exit cleanly, as
> this means an update is already running.
>
> However I’d like to understand how we end up in this situation of two
> updates running concurrently. I’ll dig into it.
>
A thought about getting 2 updates running concurrently.
When I have not run the ubuntu computer recently (it is set up for my
wife at the moment), I tend to go to Update Manager and run it
manually. If it would also run automatically, and I do not notice
that it is already running, that could cause it to run twice.
Robert
(I am stuck with using this windows xp computer because of some
software I need to use. Ubuntu is so very much more efficient and
faster on a computer with similar hardware. If I could get everything
I want to work on ubuntu, I would abandon windows completely.)
On 21 February 2011 21:47, Olivier Tilloy <email address hidden> wrote: software- center/ update- software- center-
> I can easily reproduce, on Maverick and Natty, by running concurrently
> two instances of /usr/share/
> agent.
>
> Fixing the symptom would be trivial too: if the temporary DB file
> already exists, or if we catch a DatabaseLockError, exit cleanly, as
> this means an update is already running.
>
> However I’d like to understand how we end up in this situation of two
> updates running concurrently. I’ll dig into it.
>
--
Robert Higginson