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

2016-08-23 Thread Daniel van Vugt
** Also affects: oxide-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: oxide-qt (Ubuntu)
   Importance: Undecided => Critical

** Changed in: oxide-qt (Ubuntu)
   Status: New => Triaged

-- 
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 Committed
Status in Oxide 1.16 series:
  Fix Committed
Status in Oxide 1.17 series:
  Fix Committed
Status in glibc package in Ubuntu:
  Invalid
Status in oxide-qt package in Ubuntu:
  Triaged

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

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-webapps-bugs] [Bug 1615683] Re: Oxide 1.17 breaks tab navigation between input fields

2016-08-23 Thread Chris Coulson
https://git.launchpad.net/oxide/commit/?id=b9755bb6f0e1fbed61e4d01b22ff9cbc4a51c57a

** Changed in: oxide
   Status: In Progress => 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/1615683

Title:
  Oxide 1.17 breaks tab navigation between input fields

Status in Oxide:
  Fix Released
Status in Oxide 1.17 series:
  Triaged

Bug description:
  The tab key won't let me navigate between input fields, but will
  trigger the navbar instead.

  The bug was discovered using oxide 1.17.3 and the recent webbrowser-
  app from silo 084 with multi-window support. Switching back to oxide
  1.16 resolved the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1615683/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-webapps-bugs] [Bug 1616132] Re: Accelerated 2D canvas disabled on arale

2016-08-23 Thread Chris Coulson
** Also affects: oxide/1.16
   Importance: Undecided
   Status: New

** Also affects: oxide/1.17
   Importance: Undecided
   Status: New

** Changed in: oxide
Milestone: None => branch-1.18

** Changed in: oxide/1.16
Milestone: None => 1.16.9

** Changed in: oxide/1.17
Milestone: None => 1.17.4

** Changed in: oxide
   Importance: Undecided => Critical

** Changed in: oxide/1.16
   Importance: Undecided => Critical

** Changed in: oxide/1.17
   Importance: Undecided => Critical

** Changed in: oxide
   Status: New => Triaged

** Changed in: oxide/1.16
   Status: New => Triaged

** Changed in: oxide/1.17
   Status: New => Triaged

-- 
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/1616132

Title:
  Accelerated 2D canvas disabled on arale

Status in Oxide:
  Triaged
Status in Oxide 1.16 series:
  Triaged
Status in Oxide 1.17 series:
  Triaged

Bug description:
  Accelerated 2D canvas was initially enabled for arale with
  
https://git.launchpad.net/oxide/commit/?id=11aa5a3ff4dfccc3a3608f8a6fd0e7ca70fd8f10
  (bug #1422408).

  It appears it has been recently disabled upstream (see
  https://git.launchpad.net/~oxide-
  
developers/oxide/+git/chromium/tree/gpu/config/software_rendering_list_json.cc#n856
  , id=96).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1616132/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-webapps-bugs] [Bug 1616132] [NEW] Accelerated 2D canvas disabled on arale

2016-08-23 Thread Olivier Tilloy
Public bug reported:

Accelerated 2D canvas was initially enabled for arale with
https://git.launchpad.net/oxide/commit/?id=11aa5a3ff4dfccc3a3608f8a6fd0e7ca70fd8f10
(bug #1422408).

It appears it has been recently disabled upstream (see
https://git.launchpad.net/~oxide-
developers/oxide/+git/chromium/tree/gpu/config/software_rendering_list_json.cc#n856
, id=96).

** Affects: oxide
 Importance: Critical
 Status: Triaged

** Affects: oxide/1.16
 Importance: Critical
 Status: Triaged

** Affects: oxide/1.17
 Importance: Critical
 Status: Triaged

-- 
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/1616132

Title:
  Accelerated 2D canvas disabled on arale

Status in Oxide:
  Triaged
Status in Oxide 1.16 series:
  Triaged
Status in Oxide 1.17 series:
  Triaged

Bug description:
  Accelerated 2D canvas was initially enabled for arale with
  
https://git.launchpad.net/oxide/commit/?id=11aa5a3ff4dfccc3a3608f8a6fd0e7ca70fd8f10
  (bug #1422408).

  It appears it has been recently disabled upstream (see
  https://git.launchpad.net/~oxide-
  
developers/oxide/+git/chromium/tree/gpu/config/software_rendering_list_json.cc#n856
  , id=96).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1616132/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-webapps-bugs] [Bug 1505746] Re: Browser detection is broken for many WebRTC demos

2016-08-23 Thread Chris Coulson
** Changed in: oxide
   Status: Triaged => Invalid

-- 
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/1505746

Title:
  Browser detection is broken for many WebRTC demos

Status in Oxide:
  Invalid

Bug description:
  I opened https://apprtc.appspot.com/ in webbrowser-app running on
  arale with oxide 1.10.2, and it appears some WebRTC functions are not
  being exposed:

  Error getting user media: getUserMedia is not a function

  Create PeerConnection exception: RTCPeerConnection is not a
  function

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1505746/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-webapps-bugs] [Bug 1616043] [NEW] OSK not launched on tapping input field

2016-08-23 Thread Santosh
Public bug reported:

Open google.com
tap on input field 

result : osk doesn't appear

Actual : osk should be visisble

** Affects: oxide
 Importance: Critical
 Status: Triaged

-- 
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/1616043

Title:
  OSK not launched on tapping input field

Status in Oxide:
  Triaged

Bug description:
  Open google.com
  tap on input field 

  result : osk doesn't appear

  Actual : osk should be visisble

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1616043/+subscriptions

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp


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

2016-08-23 Thread Chris Coulson
Marking the glibc task as invalid (see IRC conversation)

 does the kernel in yakkety support MADV_FREE?
 chrisccoulson, that is documented as 4.5+ so we will, and currently don't
 apw, ah thanks. See bug 1613258 for context - the new glibc 
defines MADV_FREE
 chrisccoulson, that may have been built with the 4.6 which was in 
-proposed for a time (glibc)
 that said, i am supprised that glibc is assuming it can use it
 infinity, ^
 chrisccoulson, oh but it is likely the seccomp bits right?  so just a 
profile change ?
 chrisccoulson, in the sense it is resonable for glibc to define it, and the 
kernel to return EINVAL or indeed work, but we need the seccomp profile to 
reflect that possibility
 apw, we'll probably end up doing the same as 
http://code.qt.io/cgit/qt/qtwebengine-chromium.git/commit/?h=49-based&id=b12ffcd411d4776f7120ccecb3be34344d930d2b
 chrisccoulson, wouldn't it make more sense to try MADV_FREE and if it 
fails ENOSUPPORT or whatever dropback to whatever it does when it doesn't have 
_FREE ?
 so one uses it in 4.5 and not before that all shiney and automatically 
 apw, we could probably do that

** Changed in: glibc (Ubuntu)
   Status: Triaged => Invalid

-- 
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 Committed
Status in Oxide 1.16 series:
  Triaged
Status in Oxide 1.17 series:
  Fix Committed
Status in glibc package in Ubuntu:
  Invalid

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

-- 
Mailing list: https://launchpad.net/~ubuntu-webapps-bugs
Post to : ubuntu-webapps-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs
More help   : https://help.launchpad.net/ListHelp