lxlauncher crashed with SIGSEGV in menu_cache_item_dup_parent()
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
ProcVersionSign
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu3
Architecture: amd64
Config_
[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_
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_
menu_cache_
?? ()
?? () from /usr/lib/
g_main_
Title: lxlauncher crashed with SIGSEGV in menu_cache_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
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.