update-manager loses the selection

Bug #106529 reported by Vicente Ruiz
28
This bug affects 2 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: update-manager

When I have updates available, I select only the updates that I want.
Then, if I cancel the dowloading or gives error, I lose the selection
and I must return to select.

ProblemType: Bug
Architecture: i386
Date: Sat Apr 14 13:48:03 2007
DistroRelease: Ubuntu 7.04
Uname: Linux SamsungX05 2.6.20-14-generic #2 SMP Thu Apr 12 22:53:19 UTC 2007 i686 GNU/Linux

Revision history for this message
Marco Rodrigues (gothicx) wrote :

I can confirm that..

Changed in update-manager:
status: Unconfirmed → Confirmed
assignee: nobody → mvo
Changed in update-manager:
importance: Undecided → Low
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. This is still an issue in latest release.

Changed in update-manager:
status: Confirmed → Triaged
Michael Vogt (mvo)
Changed in update-manager (Ubuntu):
assignee: Michael Vogt (mvo) → nobody
milestone: later → none
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Hi Robert,

Please please don't forward dupe bugs unless the new bug has more activity/a solution that the old bug doesn't. It throws away history that a bug may have built up over time...

Duplicate against older bugs where possible rather than newer ones!

Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

As far as I can tell, both bugs contain similar levels of activity (mainly people confirming) and the newer one has been marked as a duplicated, so the process has been followed correctly.

Revision history for this message
Robert Roth (evfool) wrote :

@Sitsofe Wheeler: I have marked this as the "master bug" (set the older one as a duplicate of this one) as this had a bit more activity, and this has been set to Triaged wit Low importance, whereas the other one is still in Confirmed state with a lower (Wishlist priority). Both bugs were reported for the same release, with 3 months difference, so in this case I guess it's OK to mark the older one as a duplicate. But if this really is a problem and more people disagree with my decision, I can set the other one as the master bug, set it to Triaged and raise its priority. Anyway, I'm trying to follow the mark the newer bugs as duplicates principle, but I'll try to stick more to it from now on.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Brendan, Robert:
You're right - there is barely anything between these two so duping either way seems fine. I should have looked at the initial reporting dates rather than just bug number.

Robert:
You know what you're doing far better than I :-) My apologies for commenting in error and from above it appears most agree with your decision so I wouldn't worry.

Robert Roth (evfool)
Changed in update-manager (Ubuntu):
assignee: nobody → Robert Roth (evfool)
status: Triaged → In Progress
Robert Roth (evfool)
Changed in update-manager (Ubuntu):
assignee: Robert Roth (evfool) → nobody
status: In Progress → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.