unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()

[AleksK]

I used the quick search DoubleCommander

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libunity9 7.1.4+14.04.20140210-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
Uname: Linux 3.13.0-12-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Feb 22 17:17:46 2014
ExecutablePath: /usr/bin/unity-scope-loader
InstallationDate: Installed on 2014-02-22 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221)
ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=ru
 PATH=(custom, user)
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fbb2b735d20 <g_desktop_app_info_get_is_hidden>: movzbl 0xc0(%rdi),%eax
 PC (0x7fbb2b735d20) ok
 source "0xc0(%rdi)" (0x000000c0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: libunity
StacktraceTop:
 g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/libgnome-menu-3.so.0
 ?? () from /usr/lib/libgnome-menu-3.so.0
 gmenu_tree_load_sync () from /usr/lib/libgnome-menu-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so
Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip 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 #1212540, 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.