unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()

[Emma Bordiga]

Logged into Unity session from LightDM after installing nvidia 364.14 drivers from graphics drivers ppa (not xorg-edgers, etc) and enabling modesetting in nvidia-drm.ko and removing nomodeset from kernel boot line.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-settings-daemon 15.04.1+16.04.20160209-0ubuntu1
Uname: Linux 4.4-6.dmz.1-liquorix-amd64 x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Tue Mar 22 13:33:52 2016
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2016-03-10 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160219)
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
SegvAnalysis:
 Segfault happened at: 0x7f63623c6e69 <up_exported_daemon_get_lid_is_closed+9>: mov (%rbx),%rdi
 PC (0x7f63623c6e69) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-settings-daemon
StacktraceTop:
 up_exported_daemon_get_lid_is_closed () from /usr/lib/x86_64-linux-gnu/libupower-glib.so.3
 gsd_power_manager_start () from /usr/lib/unity-settings-daemon-1.0/libpower.so
 ?? () from /usr/lib/unity-settings-daemon-1.0/libpower.so
 gnome_settings_plugin_info_activate ()
 ?? ()
Title: unity-settings-daemon crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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 #1546641, 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.