webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()

[miked]

miked@free:~$ lsb_release -rd
Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04
miked@free:~$ apt-cache policy webbrowser-app
webbrowser-app:
  Installed: 0.23+16.04.20160322-0ubuntu1
  Candidate: 0.23+16.04.20160322-0ubuntu1
  Version table:
 *** 0.23+16.04.20160322-0ubuntu1 500
        500 http://mirrors.us.kernel.org/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
miked@free:~$

Webbrowser Crashes on start-up and wants to file report.

I expected the webbrowser to open for me to use.

Instead it Crashes and wants to send report.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: webbrowser-app 0.23+16.04.20160322-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sun Apr 3 03:54:19 2016
ExecutablePath: /usr/bin/webbrowser-app
ExecutableTimestamp: 1458630336
InstallationDate: Installed on 2016-04-03 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
ProcCmdline: webbrowser-app
ProcCwd: /home/miked
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: webbrowser-app
StacktraceTop:
 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
 QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
 QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
Title: webbrowser-app crashed with SIGABRT in QMessageLogger::fatal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

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 #1538601, 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.