This bug was fixed in the package gsettings-desktop-schemas -
3.31.0.2-2ubuntu3
---------------
gsettings-desktop-schemas (3.31.0.2-2ubuntu3) disco; urgency=medium
* Add Restore-peripherals-display-keys.patch:
- Add 2 dummy keys for renamed gsettings keys to give us more
time to fix their users (LP: #1812143)
* Revert "Add Breaks: mutter << 3.31.4"
-- Jeremy Bicha <jbi...@debian.org> Thu, 24 Jan 2019 12:43:44 -0500
** Changed in: gsettings-desktop-schemas (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1812143
Title:
gsettings-desktop-schemas 3.31 breaks mutter 3.30
Status in gsettings-desktop-schemas package in Ubuntu:
Fix Released
Status in mutter package in Ubuntu:
Triaged
Status in ukwm package in Ubuntu:
Confirmed
Bug description:
We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to
gsettings-desktop-schemas.
Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in
gdm/gnome-shell being unable to start.
Also, ukwm is a fork of mutter so the Kylin devs need to backport the
relevant commits from mutter.
The problematic gsettings commit was:
https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c
I think the mutter commits can be found at
https://gitlab.gnome.org/GNOME/mutter/merge_requests/133
We could easily add a dummy key with the old name but I'm thinking the
way forward is just to package the newer mutter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
