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

[Bryan Quigley]

No obvious crash effect.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libunity9 7.1.4+15.10.20151002-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 4 14:59:32 2016
ExecutablePath: /usr/bin/unity-scope-loader
ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f758693d330 <g_desktop_app_info_get_is_hidden>: movzbl 0xc0(%rdi),%eax
 PC (0x7f758693d330) 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/x86_64-linux-gnu/libgnome-menu-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0
 gmenu_tree_load_sync () from /usr/lib/x86_64-linux-gnu/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 cdrom dip libvirtd lpadmin lxd 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 #1542782, 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.