"Not all updates can be installed" dialog has unclear buttons & unselectable text

Bug #120689 reported by Joachim Noreiko on 2007-06-16
94
This bug affects 13 people
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
High
Steve Langasek

Bug Description

The button labels are not clear.

"Partial Upgrade" begins an upgrade
In old versions: "Close" -- does this mean close the dialog, or close the app? (ie, give up completely)
In Raring: "Continue" -- (from bug 1137144) Reading that message, "Partial Upgrade" and "Continue" are the same thing. There is no "Cancel" to backout. I'm stuck unless I just close the dialog.

The deeper problem is that I don't understand why this dialog appears. The model of Software Update as I understand it is that the user can pick which updates they want. When faced by this dialog, I am confused about how I say "no, I only want to pick SOME packages to update).

Sebastian Heinlein (glatzor) wrote :

This dialog appears if update-manager has to change allready installed packages to install all updates. You should not see this dialog if you only use default Ubuntu software. Have you enabled any third party package repositories? Do you run gutsy?

Changed in update-manager:
status: Unconfirmed → Needs Info
Joachim Noreiko (jnoreiko) wrote :

Yes, I think I've enabled other repositories. I will remove them and report back.

How are the items listed as "Distribution updates" related to this? (Bug #120692)

Bug #120688 was actually about my problem with this dialog appearing unexpectedly.
This bug is about the design of the dialog, which is confusing. To my mind, these were two separate issues.

Sebastian Heinlein (glatzor) wrote :

All bugs have been a result of misunderstanding the dialog. The wording is far away from perfect. So we should improve it.

Disabling third party repositories could not be enough. If you have installed software packages that have not been packaged well they will still block upgrades.

Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in update-manager (Ubuntu):
status: Invalid → Confirmed
tags: added: precise quantal
description: updated
Stuart Bishop (stub) on 2013-03-05
tags: added: raring
Changed in update-manager (Ubuntu):
importance: Undecided → High
Changed in update-manager (Ubuntu):
assignee: nobody → Steve Langasek (vorlon)
rully (me-onemail) on 2013-05-03
Changed in update-manager (Ubuntu):
assignee: Steve Langasek (vorlon) → rully (me-onemail)
Changed in update-manager (Ubuntu):
assignee: rully (me-onemail) → Steve Langasek (vorlon)
Kieran O'Neill (oneillkza) wrote :

Oh god, I did not mean to set that to "fix released" -- that was just a misclick. Apparently, although I have permissions to set "fix released", I do not have permissions to set it back to "confirmed".

Changed in update-manager (Ubuntu):
status: Confirmed → Fix Released
Kieran O'Neill (oneillkza) wrote :

Note: if the plan is just to change the dialog wording, could I suggest adding the following:

"Clicking on "partial upgrade" will attempt to perform a distribution upgrade. Do not click this button if you are currently running an LTS distribution and do not wish to upgrade to a non-LTS distribution, as it will cause update-manager to perform such an upgrade in spite of settings in /etc/update-manager/release-upgrades. If you wish to simply update those packages which did not have errors, click "Close" and then click "Update Packages"."

Steve Langasek (vorlon) on 2013-05-08
Changed in update-manager (Ubuntu):
status: Fix Released → Confirmed

Since this bug:

- Is valid.
- Is well described.
- Is reported in the upstream project.
- Is ready to be worked on by a developer.

It's already triaged.

Changed in update-manager (Ubuntu):
status: Confirmed → Triaged
daniel.higa (animelp) wrote :

It was happening to me since May.
Today (July 26th), I change the repositories from:
ar.archive.ubuntu.com
to:
archive.ubuntu.com/ubuntu/

and the problem it's gone.

ghsta (ghstass) on 2013-08-31
Changed in update-manager (Ubuntu):
status: Triaged → New
status: New → Fix Committed
Steve Langasek (vorlon) on 2013-08-31
Changed in update-manager (Ubuntu):
status: Fix Committed → Triaged
vinh. (vntour) wrote :

The following packages have unmet dependencies:

icedtea-7-jre-jamvm: Depends: openjdk-7-jre-headless (= 7u75-2.5.4-1~precise1) but 7u55-2.4.7-1ubuntu1~0.12.04.2 is installed
                     Depends: zlib1g (>= 1:1.1.4) but 1:1.2.3.4.dfsg-3ubuntu4 is installed
openjdk-7-jre: Depends: openjdk-7-jre-headless (= 7u75-2.5.4-1~precise1) but 7u55-2.4.7-1ubuntu1~0.12.04.2 is installed
               Depends: libjpeg8 (>= 8c) but 8c-2ubuntu7 is installed

peterstan (stasnel) on 2015-08-22
Changed in update-manager (Ubuntu):
status: Triaged → Fix Released
Steve Langasek (vorlon) on 2015-08-23
Changed in update-manager (Ubuntu):
status: Fix Released → Triaged
omar swaby (omar-swaby) on 2016-05-23
Changed in update-manager (Ubuntu):
status: Triaged → Incomplete
Steve Langasek (vorlon) on 2017-05-08
Changed in update-manager (Ubuntu):
status: Incomplete → Triaged
Changed in update-manager (Ubuntu):
status: Triaged → Fix Committed
Steve Langasek (vorlon) on 2017-05-10
Changed in update-manager (Ubuntu):
status: Fix Committed → Triaged
faaaaa (faaaaa) on 2019-04-08
Changed in update-manager (Ubuntu):
status: Triaged → Incomplete
Steve Langasek (vorlon) on 2019-04-08
Changed in update-manager (Ubuntu):
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers