[Bug 133139] Re: update-manager bug when loading Changes is slow

Robert Roth evfool at gmail.com
Mon Sep 5 18:25:34 UTC 2011


** Changed in: update-manager (Ubuntu)
     Assignee: (unassigned) => Robert Roth (evfool)

** Changed in: update-manager (Ubuntu)
       Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/133139

Title:
  update-manager bug when loading Changes is slow

Status in “update-manager” package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: update-manager

  Hello. This is about the latest (and older) update-manager on Gutsy.

  I have the update-manager window opened with the "Changes" tab
  selected and expanded, so it shows the changes for every package to be
  updated.

  Imagine there are three packages in the updates list, A, B and C. If A
  is selected, its changes are displayed correctly below it. If I press
  down arrow on the keyboard, the B package is selected, its changes
  should be looked-up and displayed. The same for C.

  This works OK normally, but:

  (We're back with A selected.) I click down, B gets selected. The
  Changes tab briefly displays "Downloading the list of changes" or
  something similar. This is the trick: If I press down again _before_
  the changes for B are displayed (this happens often for me, but it
  might depend on your connection), then the bug happens.

  Usually the changes for C are displayed (not sure why it's quicker
  than B), then I get a warning in the console, then the changes for B
  are displayed, although C is still selected. I can get the changes for
  C by going back to B and then returning to C.

  Here's an example for this happening three times in a row:
  /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py:584: Warning: /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:1741: instance `0x875ece0' has no handler with id `362'
    button.disconnect(id);
  /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py:584: Warning: /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:1741: instance `0x875ece0' has no handler with id `367'
    button.disconnect(id);
  /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py:584: Warning: /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:1741: instance `0x875eb70' has no handler with id `377'
    button.disconnect(id);

  I suppose a callback waiting for the download of the changes forgets
  to check if it should still display them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/133139/+subscriptions




More information about the foundations-bugs mailing list