[xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_SYSV()

[tim nelson]

Quite possibly this is related to my wireless ac/bluetooth adapter.

Wireless 7260
3.10+
iwlwifi-7260-ucode-22.0.7.0.tgz

The wifi works but when i start dabbling with the bluetooth everything goes nuts. I think when the gnome-settings daemon was open I issued a reboot from the terminal which causes gnome 3 to try to reopen the gnome settings upon reboot? It seems any time you leave applications open and reboot you run into something saying it failed.

However, my bluetooth has stopped working entirely now.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-settings-daemon 3.8.5-0ubuntu5
ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
Uname: Linux 3.11.0-9-generic i686
ApportVersion: 2.12.5-0ubuntu1
Architecture: i386
Date: Wed Oct 2 09:06:48 2013
ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
InstallationDate: Installed on 2013-08-29 (37 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha i386 (20130828)
MarkForUpload: True
ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb5aa512a: mov (%eax),%eax
 PC (0xb5aa512a) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6
Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in ffi_call_SYSV()
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 #1232419, 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.