bamfdaemon crashed with signal 5 in _XReply()

[Jonathan Brier]

While running steam big picture mode main menu I started to notice some artifacts of corruption on the other two displays when using the wireless xbox360 controller and trying to scroll left at the end of the menu. Then as I tried using apport-bug the display started to lockup and blackout then the whole system locked up and this error report was waiting upon the fresh boot and login to the user account along with many other errors.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: bamfdaemon 0.5.1+13.10.20130830-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
ApportVersion: 2.12.5-0ubuntu1
Architecture: amd64
Date: Wed Oct 9 18:16:06 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
ExecutableTimestamp: 1377887130
InstallationDate: Installed on 2012-11-29 (314 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, no user)
 LANGUAGE=en_US
 LANG=en_US.UTF-8
Signal: 5
SourcePackage: bamf
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: bamfdaemon crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to saucy on 2013-09-28 (11 days ago)
UserGroups: adm cdrom dip lpadmin plex plugdev sambashare sudo

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