unity-settings-daemon crashed with signal 5

[Till Kamppeter]

After I have observed that bug 1722988 happened to me and after a reboot I got this crash report. Probably the crashing unity-settings-daemon prevented LightDM from starting.

I had to switch to GDM.

Why do we still have unity-settings-daemon after discontinuing Unity? Why not also discontinue LightDM or make it use gnome-settings-daemon?

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: unity-settings-daemon 15.04.1+17.10.20171003-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4
Uname: Linux 4.13.0-15-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Thu Oct 12 15:33:48 2017
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2015-04-30 (896 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
Signal: 5
SourcePackage: unity-settings-daemon
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_enum () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/unity-settings-daemon-1.0/libpower.so
 gsd_power_manager_start () at /usr/lib/unity-settings-daemon-1.0/libpower.so
Title: unity-settings-daemon crashed with signal 5
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #1722920. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1722920, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.