lxlauncher crashed with SIGSEGV in menu_cache_item_dup_parent()

Bug #1352043 reported by Cristian Aravena Romero
This bug report is a duplicate of:  Bug #1236109: lxlauncher crashes. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxlauncher (Ubuntu)
New
Undecided
Unassigned

Bug Description

Crash start ubuntu.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: lxlauncher 0.2.2-4ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
Config_System_Lubuntu-Netbook_settings.conf:
 [Main]
 BUTTON_SIZE=120
 IMG_SIZE=48
CurrentDesktop: LXDE
Date: Sun Aug 3 19:59:21 2014
ExecutablePath: /usr/bin/lxlauncher
InstallationDate: Installed on 2014-04-27 (98 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
ProcCmdline: lxlauncher
SegvAnalysis:
 Segfault happened at: 0x7f7c2f785050 <menu_cache_item_dup_parent+16>: mov 0x38(%rbx),%rbx
 PC (0x7f7c2f785050) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

information type: Private → Public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.