lxlauncher crashed with SIGSEGV in menu_cache_item_dup_parent()

[Jim Hunziker]

Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

I just upgraded from 13.10 (or maybe 13.04? not sure if Software Updater would have allowed that), and I don't think I did anything that triggered this.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: lxlauncher 0.2.2-4ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
Config_System_Lubuntu-Netbook_settings.conf:
 [Main]
 BUTTON_SIZE=120
 IMG_SIZE=48
CurrentDesktop: LXDE
Date: Sat Apr 5 19:34:57 2014
ExecutablePath: /usr/bin/lxlauncher
ProcCmdline: lxlauncher
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f1de8f34050 <menu_cache_item_dup_parent+16>: mov 0x38(%rbx),%rbx
 PC (0x7f1de8f34050) ok
 source "0x38(%rbx)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: lxlauncher
StacktraceTop:
 menu_cache_item_dup_parent () from /usr/lib/x86_64-linux-gnu/libmenu-cache.so.3
 menu_cache_item_get_parent () from /usr/lib/x86_64-linux-gnu/libmenu-cache.so.3
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libmenu-cache.so.3
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: lxlauncher crashed with SIGSEGV in menu_cache_item_dup_parent()
UpgradeStatus: Upgraded to trusty on 2014-04-05 (0 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin 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 #1236109, 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.