WebKitPluginProcess crashed with SIGSEGV in MozNPN_GetStringIdentifier()

[Charles Silva]

error opening google's online account folder

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: libwebkit2gtk-4.0-37 2.18.0-2
ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
Uname: Linux 4.13.0-16-lowlatency x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 11:00:30 2017
ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess
InstallationDate: Installed on 2017-02-08 (257 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitPluginProcess -scanPlugin /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, user)
 LANG=pt_BR.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fe7235e817e <MozNPN_GetStringIdentifier+14>: mov 0xb0(%rax),%r11
 PC (0x7fe7235e817e) ok
 source "0xb0(%rax)" (0x000000b0) not located in a known VMA region (needed readable region)!
 destination "%r11" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: webkit2gtk
StacktraceTop:
 MozNPN_GetStringIdentifier () from /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
 DTLiteObject::initialize() () from /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
 NPAPIBasePlugin::NP_Initialize(_NPNetscapeFuncs*) () from /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
 NP_Initialize () from /usr/lib/jvm/java-8-oracle/jre/lib/amd64/libnpjp2.so
 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37
Title: WebKitPluginProcess crashed with SIGSEGV in MozNPN_GetStringIdentifier()
UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

[Apport retracing service (apport)]

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for perl-base
no debug symbol package found for perl-base
no debug symbol package found for liblttng-ust0

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

[marty (sanman900)]

thank you for your time and commitment good to have people like you out there.

[Colan Schwartz (colan)]

How does one fix the "no debug symbol package found for perl-base" problem, which is preventing this from being considered a valid issue?