Ubiquity is still installed after standard desktop 17.10 installation

Bug #1698752 reported by Didier Roche-Tolomelli
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ubuntu-meta (Ubuntu)
Fix Released
High
Didier Roche-Tolomelli

Bug Description

Ubiquity is supposed to be removed as one of the post-copy process in the chroot.

Consequence: ubiquity icons is still available in the G-S launcher/dash after login.

Tags: artful
description: updated
tags: added: artful
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
Changed in ubiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

This is the diff of filesystem.manifest-remove between zesty and artful. It shows that ubiquity has been removed from the manifest.

affects: ubiquity (Ubuntu) → livecd-rootfs (Ubuntu)
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

The difference in manifest-remove has been introduced with build 20170606.1 [1] It matches with the release of livecd-rootfs on the 6th and revno 1482 [2]

[1] https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/artful/ubuntu/+build/100107
[2] http://bazaar.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/revision/1482

Changed in livecd-rootfs (Ubuntu):
status: Confirmed → Triaged
assignee: nobody → Didier Roche (didrocks)
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

diff of manifest-remove between builds 20170606 and 20170606.1

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Right; the change comes from this change (essentially to add ubuntu-desktop as an install task). The problem from what I can tell is that ubiquity is not contained in that task, and somehow does show up at the install pass when building the live filesystem.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Back to the desktop team:

  Installing ubiquity-frontend-gtk as Recommends of indicator-datetime
    Installing ubiquity as Depends of ubiquity-frontend-gtk
      Installing libdebian-installer4 as Depends of ubiquity
      Installing libparted-fs-resize0 as Depends of ubiquity
      Installing ubiquity-ubuntu-artwork as Depends of ubiquity
      Installing ubiquity-casper as Depends of ubiquity
      Installing os-prober as Depends of ubiquity

Turns out this happens because indicator-datetime is seeded, but indicator-applet (the alternate Recommends from indicator-datetime) is in universe (and we don't build with universe).

(from indicator-datetime:)
Recommends: indicator-applet | indicator-renderer,

indicator-renderer is provided by ubiquity-frontend-gtk (due to the panel code, etc.), and ends up being picked to satisfy indicator-datetime's dependencies.

I see two ways to fix it, both of which are for the Desktop Team to resolve (as it requires some decision for the team):

 - MIR indicator-applet and seed it, so that it ends up satisfying the first part of indicator-datetime's deps (and other indicator packages')
 - unseed the indicators, remove them from ubuntu-desktop.

As far as I can tell they are not required in the GNOME Shell world, but that decision is not up to me to make.

Reassigning to ubuntu-meta, since that seems to be the most likely place to fix things (unseeding indicators), and I'm leaving this assigned to didrocks. Feel free to reassign to somebody else or change the task.

affects: livecd-rootfs (Ubuntu) → ubuntu-meta (Ubuntu)
Revision history for this message
Iain Lane (laney) wrote :

From <http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.artful/desktop>:

indicator-datetime | indicator-datetime | unity-greeter (Recommends) | Ubuntu Desktop Team <email address hidden> | 284772 | 1308

et al

I think they will drop off once we switch to gdm3, or at least at that point we'll see if there's another path keeping them on.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Ubiquity doesn't need it at all, so on that side it will be fine to remove.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

Thanks for the investigation cyphermox!

Ok, I guess let's pend that on the ligthdm -> gdm switch and ensure we unseed it at that point.

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I haven't done a test install recently. Is this fixed now?

Changed in ubuntu-meta (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

No it is not fixed.

Changed in ubuntu-meta (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Actually, this is fixed with 20170830. I'm closing this report.

Changed in ubuntu-meta (Ubuntu):
status: Triaged → Fix Released
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.