compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path() from attempting to launch System Settings

[Michael Tinsay]

Here's what I did:
1. Launch System Settings.
2. Changed launchbar sensitivity to high.
3. Exit System Settings.
4. Did a few other stuff.
5. Launch System Settings (again from the launchbar).
6. Unity hangs for a few seconds.
7. Unity crashes.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity 7.0.2+13.10.20130705.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.10.2-0ubuntu4
Architecture: amd64
Date: Thu Jul 11 10:03:01 2013
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2012-06-26 (379 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f88218d545d <g_mount_spec_to_dbus_with_path+77>: mov 0x8(%r15),%rdi
 PC (0x7f88218d545d) ok
 source "0x8(%r15)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_mount_spec_to_dbus_with_path () from /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgvfsdbus.so
 g_file_load_contents () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: compiz crashed with SIGSEGV in g_mount_spec_to_dbus_with_path()
UpgradeStatus: Upgraded to saucy on 2013-07-11 (0 days ago)
UserGroups: adm cdrom dip kvm libvirtd lpadmin 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 #1047517, 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.