** Changed in: python-apt (Ubuntu)
Importance: Undecided = Low
** Changed in: update-manager (Ubuntu)
Importance: Undecided = Low
--
update-manager cpu-bound for a long time opening
https://bugs.launchpad.net/bugs/613743
You received this bug notification because you are a member of
** Tags added: patch
--
update-manager cpu-bound for a long time opening
https://bugs.launchpad.net/bugs/613743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
first patch was rejected, unsubscribing ubuntu-sponsors
** Changed in: update-manager (Ubuntu)
Status: New = Fix Released
--
update-manager cpu-bound for a long time opening
https://bugs.launchpad.net/bugs/613743
You received this bug notification because you are a member of Ubuntu
Bugs,
Latest version of update-manager has been fixed:
update-manager (1:0.142.5) maverick; urgency=low
* more python-apt 0.8 porting
* less updates to the progressbar
* DistUpgrade/DistUpgradeViewNonInteractive.py:
- fix crash in non-interactive upgrader when a conffile prompt
is
I tracked this down to a very high frequency of GUI updates, when the
'Building data structures' progress bar is being updated.
With the attached patch, we still get many progress-bar updates and
update-manager opens in now 5 seconds, rather than ~60s (or more with
further power saving).
**
Changing status to NEW again. We did not even take a look at it, and did
not commit a fix in one of the repos. And the patch is not correct
either, it should be done differently.
** Changed in: python-apt (Ubuntu)
Status: Fix Committed = New
** Changed in: python-apt (Ubuntu)
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
update-manager cpu-bound for a long time opening
https://bugs.launchpad.net/bugs/613743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have added update-manager to the affected packages, because I think
that the bug should be fixed there, by adding a check that the progress
is not updated more than about 25 times per second (or what ever else is
useful).
I did not close the python-apt bug, as we might want to decrease the
Oops - sorry for the marking with the wrong status.
With the recent update to libcairo for slow progress bar drawing, the
number of progress bar updates is still needlessly high, making update-
manager slow opening over a TCP socket, so this bug is still valid.
The patch changes a value (100)
Yes, but 2000 means 6% (currently it is 0.3%) which means that the
progress bar will jump. The frontend should limit itself to an usable
level of updates, that can not be the job of the code driving the
progress. Just skip some updates in the frontend if the last update was
less than n seconds ago
10 matches
Mail list logo
