Ubiquity does not use the Ubuntu font

Bug #1702892 reported by Jean-Baptiste Lallement on 2017-07-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Sebastien Bacher

Bug Description

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)
 PATH=(custom, no user)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Jean-Baptiste Lallement (jibel) wrote :
Jean-Baptiste Lallement (jibel) wrote :
Dimitri John Ledkov (xnox) wrote :

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


                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):
                        [msd], stdin=null, stdout=logfile, stderr=logfile,

                elif (osextras.find_on_path(usd)):
                    # Wait until xsettings plugin is activated
                    xsettings = SignalWatcher(self, usd,
                    # the SignalWatcher will run until the signal is seen...
                    # 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):
                        [gsd], stdin=null, stdout=logfile, stderr=logfile,

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) wrote :

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

Changed in ubiquity (Ubuntu):
importance: Undecided → High
Sebastien Bacher (seb128) wrote :

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.

tags: added: patch
Changed in ubiquity (Ubuntu):
status: New → In Progress
assignee: nobody → Sebastien Bacher (seb128)
Launchpad Janitor (janitor) wrote :

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

  [ 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

Changed in ubiquity (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers