Ubiquity does not use the Ubuntu font

[Jean-Baptiste Lallement]

artful desktop 20170707.1

The font in Ubiquity is not the Ubuntu font (cf screenshot left 20170705, right 20170707.1)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 7 14:20:09 2017
InstallationDate: Installed on 2013-09-03 (1402 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Dimitri John Ledkov (xnox)]

There is a slight difference between unity-settings-daemon and gnome-settings-daemon code paths.

Specifically:

                msd = '/usr/bin/mate-settings-daemon'
                usd = '/usr/lib/unity-settings-daemon/unity-settings-daemon'
                gsd = '/usr/lib/gnome-settings-daemon/gnome-settings-daemon'

                if osextras.find_on_path(msd):
                    extras.append(subprocess.Popen(
                        [msd], stdin=null, stdout=logfile, stderr=logfile,
                        preexec_fn=self.drop_privileges))

                elif (osextras.find_on_path(usd)):
                    # Wait until xsettings plugin is activated
                    xsettings = SignalWatcher(self, usd,
                                              "org.gnome.SettingsDaemon",
                                              "/org/gnome/SettingsDaemon",
                                              "PluginActivated",
                                              "xsettings")
                    # the SignalWatcher will run until the signal is seen...
                    extras.extend(xsettings.run())
                    # At this point we're sure the usd xsettings plugin is
                    # available, we can continue setting up the session.

                elif osextras.find_on_path(gsd):
                    extras.append(subprocess.Popen(
                        [gsd], stdin=null, stdout=logfile, stderr=logfile,
                        preexec_fn=self.drop_privileges))

Thus in u-s-d case there is an extra blocking wait on u-s-d to initialise xsettings before proceeding.

I do not know if something similar is required in g-s-d case, to e.g. wait for g-s-d to be fully up.

However, longer term, imho ubiquity-dm should not at all be in use at all, and instead we should boot to gdm3 normally and have e.g. a casper override to start up in ubiquity installer mode, rather than full session.

[Sebastien Bacher (seb128)]

The previous comment description is not the issue, but

                 gsd = '/usr/lib/gnome-settings-daemon/gnome-settings-daemon'

or gnome-settings-daemon has been split in different binaries so the ubiquity code needs to be updated

[Sebastien Bacher (seb128)]

The change there restores the correct look but we might need to start some other gsd components as well, I'm not proposing the change for a merge yet due to that. If somebody else wants to work on that feel free, otherwise I've another look next week.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubiquity - 17.10.4

---------------
ubiquity (17.10.4) artful; urgency=medium

  [ Iain Lane ]
  * bin/ubiquity-dm: Rewrap a line to fix pep8 failure
  * Automatic update of included source packages: console-setup
    1.142ubuntu7.

  [ Jean-Baptiste Lallement ]
  * Disable screen blanking for the Ubuntu session. Thanks Heber

 -- Iain Lane <email address hidden> Mon, 21 Aug 2017 14:26:21 +0100