window-stack-bridge crashed with SIGSEGV in data()

StacktraceTop:
 data (this=0x4) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:134
 qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:991
 d_func (this=0x0) at qdbusabstractinterface.h:158
 QDBusAbstractInterface::asyncCallWithArgumentList (this=0x0, method=..., args=...) at qdbusabstractinterface.cpp:493
 Xprop (xprop=..., this=0x0) at /build/buildd/hud-13.10.1+13.10.20131014/obj-i686-linux-gnu/window-stack-bridge/BamfViewInterface.h:247

The issue is one of the most reported one on saucy: https://errors.ubuntu.com/problem/80ec348bd203ad9f5b91a956c463234dce72d2e7

Status changed to 'Confirmed' because the bug affects multiple users.

Fix committed into lp:hud/13.10 at revision 341, scheduled for release in hud, milestone Unknown

Status changed to 'Confirmed' because the bug affects multiple users.

Hello Кудрин, or anyone else affected,

Accepted hud into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/hud/13.10.1+13.10.20131024-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I don't experience this crash with the proposed package anymore.
HUD does crash though but that's LP bug #1239360 : hud-service crashed with signal 5 in _start()
I am marking this bug is verification done since I think this one is fixed (but there is another one causing hud crash after login).

This bug was fixed in the package hud - 13.10.1+13.10.20131024-0ubuntu1

---------------
hud (13.10.1+13.10.20131024-0ubuntu1) saucy; urgency=low

  [ Pete Woods ]
  * Fix the ref counting of application sources The application sources
    are now entirely owned by the application-list's hash table.

  [ Ted Gould ]
  * Add apport dependencies to the package hook. (LP: #1233994)
  * Don't show disabled items in search results. (LP: #1192646)
  * Don't crash if we get asked about a window we don't know about,
    return a null list. (LP: #1242339)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 341
 -- Ubuntu daily release <email address hidden> Thu, 24 Oct 2013 16:12:43 +0000

doesn't seem like the fix helped, I have hud (13.10.1+13.10.20131014-0ubuntu1) installed but I just saw the crash (segfault).

erik@jojda:~$ COLUMNS=250 dpkg -l hud
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-========================================================-=================================-=================================-======================================================================================================================
ii hud 13.10.1+13.10.20131014-0ubuntu1 amd64 Backend for the Unity HUD

Zasran, Thank you for taking the time to report this bug and helping to make Ubuntu better. If HUD is still crashing for you, it would be useful to have that crash information so that we can confirm whether or not it's the same crash; and if not, to handle it separately in its own ticket.

Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

The process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.