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 protected]> 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844509
Title:
ubiquity-dm fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1844509/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
