ubuntu-webapps-bugs team mailing list archive

Thread
Date

[Bug 1613258] Re: Web browser can't browse anything - "The rendering process has been closed for this tab" [signal 4 ILL_ILLOPN]

To: ubuntu-webapps-bugs@xxxxxxxxxxxxxxxxxxx
From: Chris Coulson <chrisccoulson@xxxxxxxxxx>
Date: Tue, 30 Aug 2016 18:38:55 -0000
Reply-to: Bug 1613258 <1613258@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

The new bug is bug 1618589. Would be great if someone could investigate
that.

** Changed in: oxide/1.16
       Status: Fix Committed => Fix Released

** Changed in: oxide/1.17
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1613258

Title:
  Web browser can't browse anything - "The rendering process has been
  closed for this tab" [signal 4 ILL_ILLOPN]

Status in Canonical System Image:
  New
Status in Oxide:
  Fix Released
Status in Oxide 1.16 series:
  Fix Released
Status in Oxide 1.17 series:
  Fix Released
Status in glibc package in Ubuntu:
  Invalid
Status in oxide-qt package in Ubuntu:
  Fix Released

Bug description:
  This is happening with a no-change rebuild of webbrowser-app, with the
  most likely candidate for the problem trigger being the new glibc 2.24
  in yakkety-proposed.

  ---
  https://launchpadlibrarian.net/279047362/buildlog_ubuntu-yakkety-i386.webbrowser-app_0.23+16.10.20160803.1-0ubuntu2_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613258/+subscriptions