Synaptic's 'Mark all upgrades' button is active even when there are no upgradable packages

Bug #595127 reported by Sergey "Shnatsel" Davidoff
56
This bug affects 9 people
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Triaged
Low
Unassigned
synaptic
Confirmed
Low
Unassigned
synaptic (Ubuntu)
Triaged
Low
Unassigned

Bug Description

"Mark all upgrades" button in Synaptic is clickable even when there are no upgradable packages. First of all, it's confusing. Secondly, clicking it clears all other markings (see bug #50837).

Revision history for this message
Mohamed Amine Ilidrissi (ilidrissi.amine) wrote :

Confirming this bug on 10.10

Changed in synaptic (Ubuntu):
status: New → Confirmed
summary: - Synaptic's 'Mark all upgrades' button is active even there are no
+ Synaptic's 'Mark all upgrades' button is active even when there are no
upgradable packages
Changed in synaptic:
status: New → Confirmed
Gursimran singh (simar)
Changed in hundredpapercuts:
status: New → Confirmed
Michael Vogt (mvo)
Changed in synaptic (Ubuntu):
importance: Undecided → Low
Changed in synaptic:
importance: Undecided → Low
Vish (vish)
Changed in hundredpapercuts:
assignee: nobody → Papercuts Ninja (papercuts-ninja)
importance: Undecided → Low
milestone: none → nt7-potpourri
status: Confirmed → Triaged
Changed in synaptic (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Joseph Wen (wenjoseph) wrote :

I am trying to fix this bug and have some problem. Won't it be confusing to the user if sometimes "Mark all upgrades" is clickable but sometimes it is not. Should we add some information to indicate why it is not clickable?

Revision history for this message
Vish (vish) wrote :

Joseph Wen : Not necessary. take for example of the Gedit undo/redo functions. Those buttons are "available"(clickable) only when there is something to undo or redo. When there is no action they are inactive/insensitive.

So just making the button insensitive when there is no upgrade to perform should be good enough.

Revision history for this message
Sn0w17 (sn0w17) wrote :

Did this ever get fixed?

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

No, it's not fixed yet, and it probably won't get fixed for the Precise release. I will try to take care of this in the next cycle.

Changed in synaptic (Ubuntu):
assignee: nobody → Robert Roth (evfool)
Robert Roth (evfool)
Changed in synaptic (Ubuntu):
assignee: Robert Roth (evfool) → nobody
Revision history for this message
Giacomo Picchiarelli (gpicchiarelli-deactivatedaccount) wrote :

I'll try to fix this.

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

@Giacomo Picchiarelli: Nice to hear that. If you need any help, are stuck, or anything, let us know, and keep us informed on the progress!

Changed in hundredpapercuts:
assignee: Papercuts Ninjas (papercuts-ninja) → nobody
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.