gnome-settings-daemon crashed with SIGABRT in g_assertion_message()

[adam]

report an error on start up (after login)...
 - distro was ubuntu 14.04 lts -> installed ubuntu-gnome-desktop ubuntu-shell -> gnome 3.12.2 by 'sudo add-apt-repository ppa:gnome3-team/gnome3-staging' -> unity removed by 'remove'
- installed lxde
~ service plexmediaserver sometimes interfere and crashing

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-settings-daemon 3.12.2-0ubuntu1~trusty2 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Aug 30 20:23:29 2014
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2014-04-27 (125 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/false
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-settings-daemon crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Ubuntu GNOME (ug-bot)]

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 #1353839, 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.