[Bug 1844509] Re: ubiquity-dm fails to start
Launchpad Bug Tracker
1844509 at bugs.launchpad.net
Wed Sep 25 19:53:45 UTC 2019
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 <iain.lane at canonical.com> Wed, 25 Sep 2019 17:55:44 +0100
** Changed in: ubiquity (Ubuntu Eoan)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1844509
Title:
ubiquity-dm fails to start
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Eoan:
Fix Released
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1844509/+subscriptions
More information about the foundations-bugs
mailing list