webapp-container crashed with SIGSEGV in QMetaObject::activate()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
webbrowser-app (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occurred after I closed youtube webapp
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: webapp-container 0.23+15.
ProcVersionSign
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Mon Mar 23 08:27:46 2015
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2014-12-11 (102 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
ProcCmdline: webapp-container --app-id=
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x0: Cannot access memory at address 0x0
PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: webbrowser-app
StacktraceTop:
?? ()
?? () from /usr/lib/
QMetaObject:
?? () from /usr/lib/
?? () from /usr/lib/
Title: webapp-container crashed with SIGSEGV in QMetaObject:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip kismet libvirtd lpadmin plugdev sambashare sudo wireshark
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 #1435465, 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.