unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the active window was
StockMarketEye;
the top menu bar did not display correctly,
items missing from Files dropdown list,
then this crash occurred.
Software Updater was run this morning for Wily Werewolf daily.
StockMarketEye was current version at that time, not updated.
attempt to verify the version number was unsuccessful,
the top menu bar did not display correctly,
items missing from Files dropdown list,
then this crash occurred.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: unity-services 7.3.2+15.
ProcVersionSign
Uname: Linux 4.2.0-11-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for `/apps/
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Sep 25 10:39:41 2015
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2015-07-16 (71 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150716)
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
SHELL=/bin/bash
LANG=en_US.UTF-8
LANGUAGE=en_US
XDG_RUNTIME_
SegvAnalysis:
Segfault happened at: 0x7f2cff2c73ec: mov (%rdi),%rbx
PC (0x7f2cff2c73ec) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /usr/lib/
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
g_cclosure_
g_closure_invoke () from /usr/lib/
Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip 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 #1499133, 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.