Ubuntu
ubiquity package

ubiquity-dm fails to start

Bug #1844509 reported by Jean-Baptiste Lallement on 2019-09-18

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	ubiquity (Ubuntu)	Fix Released	Critical	Iain Lane
	Eoan	Fix Released	Critical	Iain Lane

Bug Description

Ubuntu Desktop 20190917

ubiquity-dm fails to start.

Test Case:
Boot the iso

Actual result
Black screen and an error dialog saying the the installer failed to start.

There are several critical messages in dm logs:

biquity-dm: starting
ubiquity-dm: plymouth
ubiquity-dm: start X ['X', '-br', '-ac', '-noreset', '-nolisten', 'tcp', '-background', 'none', 'vt1', ':0']
Kernel command line: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
ubiquity-dm: set vars
ubiquity-dm: pam_open_session
ubiquity-dm: dm-scripts
ubiquity-dm: dconf-service
ubiquity-dm: start frontend gtk_ui
ubiquity-dm: start greeter
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.861: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.861: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.861: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.862: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.874: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.874: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.877: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): Clutter-CRITICAL **: 09:17:29.879: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed
(gnome-shell:1418): IBUS-CRITICAL **: 09:17:30.009: ibus_bus_hello: assertion 'ibus_bus_is_connected (bus)' failed
(gnome-shell:1418): GLib-GIO-CRITICAL **: 09:17:30.014: Error while sending AddMatch() message: The connection is closed
(gnome-shell:1418): IBUS-CRITICAL **: 09:17:30.014: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
(gnome-shell:1418): IBUS-CRITICAL **: 09:17:30.014: ibus_bus_call_async: assertion 'ibus_bus_is_connected (bus)' failed
ubiquity-dm: greeter exited with code 143
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:30.787: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:31.278: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:31.283: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:31.285: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:31.286: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:31.288: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GObject-CRITICAL **: 09:17:31.408: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(gnome-shell:1418): GLib-GIO-CRITICAL **: 09:17:31.450: Error while sending AddMatch() message: The connection is closed
ubiquity-dm: Exiting with code 143

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.9
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CasperVersion: 1.415
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 18 09:18:56 2019
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

See original description

Tags:

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2019-09-18:

Casper.txt Edit (1.4 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.9 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1004 bytes, text/plain; charset="utf-8")
UbiquityDebug.txt Edit (1.2 KiB, text/plain; charset="utf-8")
UbiquityDm.txt Edit (9.9 KiB, text/plain; charset="utf-8")
UbiquitySyslog.txt Edit (524.6 KiB, text/plain; charset="utf-8")

Jean-Baptiste Lallement (jibel) on 2019-09-18

description:	updated
tags:	added: rls-ee-incoming
Changed in ubiquity (Ubuntu):
importance:	Undecided → Critical

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2019-09-19:

This is fixed in latest image (20190919)

From the diff there is a new libatk and given there was several ibus error, it could be it. Closing.

Changed in ubiquity (Ubuntu):
status:	New → Fix Released

Jean-Baptiste Lallement (jibel) on 2019-09-24

Changed in ubiquity (Ubuntu):
status:	Fix Released → Confirmed

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2019-09-24:

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1844509

tags:

added: iso-testing

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2019-09-24:

This bug reappeared with image 20190924.

Will Cooke (willcooke) on 2019-09-24

Changed in ubiquity (Ubuntu):
assignee:	nobody → Sebastien Bacher (seb128)
tags:	removed: rls-ee-incoming

Iain Lane (laney) on 2019-09-25

Changed in ubiquity (Ubuntu Eoan):
assignee:	Sebastien Bacher (seb128) → Iain Lane (laney)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2019-09-25:

This bug was fixed in the package ubiquity - 19.10.11

---------------
ubiquity (19.10.11) eoan; urgency=medium

  * ubiquity-dm: Adjust to GNOME Shell's gsd-xsettings related changes. GNOME
    Shell now launches gsd-xsettings itself, via the systemd units provided in
    `gnome-session` and `gnome-settings-daemon-common`. This conflicts with
    what we're doing in ubiquity-dm in two ways:
      - We are trying to launch gsd-xsettings ourselves, and you can only have
        one of these running at a time.
      - The user systemd environment does not have $DISPLAY in it, meaning
        that gsd-xsettings can't connect to the X server.
    Stop launching gsd-xsettings from ubiquity-dm, letting the shell handle it
    directly, and also export $DISPLAY into the D-Bus and systemd environments
    so that it can start up. (LP: #1844509)
  * ubiquity-dm: Don't launch ibus when we're running gnome-shell. These days
    gnome-shell takes care of running it itself.

-- Iain Lane <email address hidden> Wed, 25 Sep 2019 17:55:44 +0100

Changed in ubiquity (Ubuntu Eoan):
status:	Confirmed → Fix Released

Revision history for this message

fossfreedom (fossfreedom) wrote on 2019-09-26:

Link this report - the above changes has caused a regression in Ubuntu Budgie https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1845432

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntuubiquity package

ubiquity-dm fails to start

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
ubiquity package