unity-settings-daemon crashed with signal 5 in g_settings_get_enum()

[Ivan Podporin]

apt-get upgrade and reboot

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
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Sat Oct 14 09:33:55 2017
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2013-11-09 (1434 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
Signal: 5
SourcePackage: unity-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_enum () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
 gsd_power_manager_start () from /usr/lib/unity-settings-daemon-1.0/libpower.so
Title: unity-settings-daemon crashed with signal 5 in g_settings_get_enum()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.xdg.autostart.unity-fallback-mount-helper.desktop: 2014-12-21T06:05:03.797221
mtime.conffile..etc.xdg.autostart.unity-settings-daemon.desktop: 2014-12-21T06:05:03.797221

[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.