[Touch-packages] [Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

2020-05-15 Thread Chris Coulson
The updated packages just revert the security fixes which resolves this
immediate issue. Keeping the bug open though because we still want to
resolve the underlying issue so that we can republish an update with the
security fixes in it

** Changed in: json-c (Ubuntu)
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to json-c in Ubuntu.
https://bugs.launchpad.net/bugs/1878723

Title:
  Kernel panic when used with upstart after 0.11-4ubuntu2.1 update

Status in json-c package in Ubuntu:
  Triaged

Bug description:
  Installing the 0.11-4ubuntu2.1 security update on a Xenial system with
  upstart installed, the system crashes with a kernel panic.

  The error message is:

  [   99.992278] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [   99.992278] 
  [   99.996057] CPU: 0 PID: 1 Comm: init Not tainted 4.4.0-1105-aws #116-Ubuntu
  [   99.996057] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
  [   99.996057]  0086 0f10ff6977efbf32 88003d45fe10 
8140926b
  [   99.996057]  81caddf8 88003d45fea8 88003d45fe98 
81195a84
  [   99.996057]  8810 88003d45fea8 88003d45fe40 
0f10ff6977efbf32
  [   99.996057] Call Trace:
  [   99.996057]  [] dump_stack+0x6d/0x92
  [   99.996057]  [] panic+0xd3/0x227
  [   99.996057]  [] do_exit+0xb9d/0xba0
  [   99.996057]  [] do_group_exit+0x47/0xb0
  [   99.996057]  [] SyS_exit_group+0x14/0x20
  [   99.996057]  [] entry_SYSCALL_64_fastpath+0x22/0xcb
  [   99.996057] Kernel Offset: disabled

  Downgrading to libjson-c2_0.11-4ubuntu2 resolves the issue.

  Steps to reproduce:
  * Create a system with Xenial installed (I'm using an AWS instance with AMI 
ami-0f2ed58082cb08a4d)
  * Install upstart: apt-get install upstart-sysv
  * Reboot
  * Update apt and upgrade the packages: apt-get update && apt-get upgrade . 
This causes the kernel panic.
  * To repeat the kernel panic, run dpkg --configure -a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-09 Thread Chris Coulson
I've uploaded the changes that were sponsored to proposed to
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa.
Please reject the packages that are currently in the unapproved queue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-06 Thread Chris Coulson
Rather than going through -proposed, it needs to go via one of our
security PPAs (which are built without -updates) and then copied across,
which is something I can do.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

2019-09-05 Thread Chris Coulson
If this change is being reverted, it needs to be done via the security
pocket rather than proposed, as Tuesday's security update was based on
the version with this regression.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1842651

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799974] Re: [MIR] gupnp

2019-08-19 Thread Chris Coulson
.
- No sql.
- Parses XML - doesn't appear to use unsafe options such as XML_PARSE_NOENT.
- No configuration files.
- No fs capabilities.

Security team ACK for promoting gupnp to main, although I'd like someone
to take a look at the issue I mentioned with the subscribe() handler.

** Changed in: gupnp (Ubuntu)
 Assignee: Chris Coulson (chrisccoulson) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp in Ubuntu.
https://bugs.launchpad.net/bugs/1799974

Title:
  [MIR] gupnp

Status in gupnp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries

  * Security

  There is an old CVE recorded/fixed
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is used during build

  * Dependendies

  The package uses standard desktop libraries that are already in main

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 4.2, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799974] Re: [MIR] gupnp

2019-08-17 Thread Chris Coulson
** Changed in: gupnp (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => Chris Coulson 
(chrisccoulson)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp in Ubuntu.
https://bugs.launchpad.net/bugs/1799974

Title:
  [MIR] gupnp

Status in gupnp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries

  * Security

  There is an old CVE recorded/fixed
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is used during build

  * Dependendies

  The package uses standard desktop libraries that are already in main

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 4.2, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799977] Re: [MIR] gssdp

2019-08-16 Thread Chris Coulson
** Changed in: gssdp (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp in Ubuntu.
https://bugs.launchpad.net/bugs/1799977

Title:
  [MIR] gssdp

Status in gssdp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on gssdp

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is being used during build

  * Dependendies

  The package dependencies are in main

  * Standards compliance

  the package is using standard packaging (dh11), the standards-version
  is 4.1.1, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799977] Re: [MIR] gssdp

2019-08-16 Thread Chris Coulson
I reviewed gssdp 1.2.0-1 as checked in to eoan. This isn't a full
security audit, but rather a quick gauge of maintainability.

- gsspd is a gobject based library for using SSDP (Simple Service Discovery 
Protocol), and is required by rygel.
- gssdp is part of the GNOME project.
- It doesn't see a lot of git activity, but it's quite a small project so 
that's not really unexpected.
- No CVEs in our database.
- Build dependencies in main except for gnome-pkg-tools, meson and valac - none 
of which create binary dependencies.

- Doesn't spawn any subprocesses.
- Looks like it's careful with memory management.
- No logging other than a few g_debugs (which are off by default).
- Doesn't use the environment
- No privileged code.
- Does some networking:
  - Consumers of the gssdp API create a GSSDPClient for each network interface.
  - GSSDPClient sets up 3 sockets - IIUC, the first one receives SSDP (NOTIFY 
and M-SEARCH) multicast packets. The second one is for sending SSDP NOTIFY 
multicast packets and sending responses to SSDP M-SEARCH multicast queries. The 
third one is for sending SSDP M-SEARCH multicast queries and receiving 
responses to those.
  - The first socket is bound to the SSDP multicast address and port.
  - The second socket is bound to the interface address and SSDP port.
  - The third socket is bound to the interface address and a random port.
  - Unless I've misunderstood something, the way that the sockets are 
configured seems a bit weird and I think there might be a bug. The 
IP_MULTICAST_IF sockopt is set (via gssdp_socket_mcast_interface_set) and 
IP_ADD_MEMBERSHIP is set (via g_socket_join_multicast_group) on the same socket 
- the one that receives multicast packets. Shouldn't the IP_MULTICAST_IF 
sockopt be set on the other 2 sockets (the ones sending multicast packets) 
instead?
- It's using AF_NETLINK for looking up MAC addresses, which it uses for keying 
a hashtable of cached user agent strings from other devices.
- The max-age in alive announcements is set to 1800s. Re-announcements are sent 
3 times during this period.
- It responds to unicast M-SEARCH queries, which is called out in 
https://blog.cloudflare.com/ssdp-100gbps/. Devices that respond to unicast 
M-SEARCH queries and are directly connected to the internet can be used in DDoS 
attacks in scenarios where an attacker is able to generate packets with a 
spoofed source IP. It does employ some rate limiting though - it delays the 
response by a random time of between 0 and 3 seconds. This was tested with 
netcat.
- No crypto.
- No sql.
- No privileged commands.
- Doesn't use any environment variables.
- No webkit.
- Lintian clean, other than a warning about there being no manpage for 
/usr/bin/gssdp-device-sniffer
- A single binary - /usr/bin/gssdp-device-sniffer in gssdp-tools, which 
provides a UI for monitoring SSDP announcements.
- Build logs look clean other than some doc warnings.
- No configuration files.
- No systemd services.
- No dbus services.
- No setuid binaries.
- No fs capabilities.
- No sudo fragments.
- No udev rules.
- No cron jobs.

Security team ACK for promoting gssdp to main.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp in Ubuntu.
https://bugs.launchpad.net/bugs/1799977

Title:
  [MIR] gssdp

Status in gssdp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on gssdp

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is being used during build

  * Dependendies

  The package dependencies are in main

  * Standards compliance

  the package is using standard packaging (dh11), the standards-version
  is 4.1.1, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799974] Re: [MIR] gupnp

2019-08-14 Thread Chris Coulson
This one could do with a quick review from the security team.

** Changed in: gupnp (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gupnp in Ubuntu.
https://bugs.launchpad.net/bugs/1799974

Title:
  [MIR] gupnp

Status in gupnp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries

  * Security

  There is an old CVE recorded/fixed
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is used during build

  * Dependendies

  The package uses standard desktop libraries that are already in main

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 4.2, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1799977] Re: [MIR] gssdp

2019-08-14 Thread Chris Coulson
This one could do with a quick review from the security team.

** Changed in: gssdp (Ubuntu)
 Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gssdp in Ubuntu.
https://bugs.launchpad.net/bugs/1799977

Title:
  [MIR] gssdp

Status in gssdp package in Ubuntu:
  New

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian, the package was in main in the past and needs to be re-
  promoted

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on gssdp

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is being used during build

  * Dependendies

  The package dependencies are in main

  * Standards compliance

  the package is using standard packaging (dh11), the standards-version
  is 4.1.1, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2018-11-27 Thread Chris Coulson
The issue is that O_PATH doesn't work from these containers:

2025  11:00:08 openat(4, "run", O_RDONLY|O_NOFOLLOW|O_CLOEXEC|O_PATH) =
-1 ELOOP (Too many levels of symbolic links)

Apparently, O_PATH was added in 2.6.39, so this makes sense now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1804847

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2018-11-27 Thread Chris Coulson
We're just going to publish a revert of the CVE-2018-6954 fixes for
16.04 before investigating this further. As far as I can tell, this
shouldn't be an issue in bionic where MIN_KERNEL_SUPPORTED is 3.2 in
glibc.

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6954

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1804847

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1804847] Re: systemd=229-4ubuntu21.8 use of fchownat failes on some systems (openvz)

2018-11-27 Thread Chris Coulson
** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1804847

Title:
  systemd=229-4ubuntu21.8 use of fchownat failes on some systems
  (openvz)

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The following description is taken from:

  https://answers.launchpad.net/ubuntu/+source/systemd/+question/676237

  Hello everyone,
  I'm running 16.04 LTS on a virtual server which, I think, uses OpenVz. After 
a recent reboot I found most of my services to be in a failed state. The reason 
for that, I guess, are these log entries:

  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/elasticsearch failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/kopano 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/php 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/postgresql 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/redis 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/screen 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of /run/utmp 
failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/links failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/systemd/netif/leases failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8 failed: Invalid argument
  Nov 17 04:47:42 h2118376 systemd-tmpfiles[165]: fchownat() of 
/run/log/journal/bbad3a438f4b4fb49e5d0700bd5981e8/system.journal failed: 
Invalid argument

  To verify I tried this:

  /usr/lib/tmpfiles.d# SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --create 
elasticsearch.conf
  Reading config file "elasticsearch.conf".
  Running create action for entry d /var/run/elasticsearch
  Found existing directory "/var/run/elasticsearch".
  "/run/elasticsearch" has right mode 40755
  chown "/run/elasticsearch" to 120.128
  fchownat() of /run/elasticsearch failed: Invalid argument

  I can manually chown the directories, e.g. "chown
  elasticsearch:elasticsearch /var/run/elasticsearch" and restart the
  service successfully.  My suspicion is, this is related to an upgrade
  of systemd to 229-4ubuntu21.8.

  At this point I don't know what to do.

  I'm also confused about the version I have installed, which I thought is 
systemd-229. Howver, I looked at 
https://github.com/systemd/systemd/blob/v229/src/tmpfiles/tmpfiles.c and found 
that fchownat() is only used from version 238+:
  Tag v237 (and earlier, including 229):
  /.../
  if (chown(fn,
    i->uid_set ? i->uid : UID_INVALID,
    i->gid_set ? i->gid : GID_INVALID) < 0)
  return log_error_errno(errno, "chown(%s) 
failed: %m", path);
  }
  /.../

  Tag v238

  /.../
  if (fchownat(fd,
   "",
   i->uid_set ? i->uid : UID_INVALID,
   i->gid_set ? i->gid : GID_INVALID,
   AT_EMPTY_PATH) < 0)
  return log_error_errno(errno, "fchownat() of %s failed: %m", path);
  /.../

  Any help fixing this problem would be highly appreciated.
  Many thanks,
  Rafael

  === Notes ===
  fchownat() was added to Linux in kernel 2.6.16;
  library support was added to glibc in version 2.4.
  checkinf if it is blocked/filtered/sandboxed, rarther than unavailable.
  glibc in bionic requires minimum linux 3.2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1576432] Re: gdb crashes when trying to start a debugging session

2018-05-01 Thread Chris Coulson
This occurs when gdb sets breakpoints on various probe events in the
dynamic loader. The probe event locations are exported from ld.so as SDT
markers, but gdb needs to know whether ARM or Thumb instructions are
being exported at each marker so that it can insert the appropriate
breakpoint instruction sequence. It does this by mapping the probe
location to a function symbol (see arm_pc_is_thumb in gdb/arm-tdep.c),
and using the target address of the symbol to determine if the function
is called in Thumb or ARM more (bit 0 of the target address will be set
for Thumb mode).

The problem here is that gdb can't map any of the probes to a symbol if
the debug symbols aren't installed, and arm_pc_is_thumb returns false in
this case (indicating ARM instructions).

But the probes that gdb sets breakpoints on are in dl_main, and dl_main is 
meant to be called in Thumb mode. See the output of readelf, noting that bit 0 
of the target address is set:
$ readelf -s /usr/lib/debug/lib/arm-linux-gnueabihf/ld-2.27.so | grep dl_main
42: 172d 10516 FUNCLOCAL  DEFAULT   11 dl_main

So without the debug symbols installed, gdb inserts the ARM breakpoint
instruction sequence for the dynamic loader probes, when it should be
inserting the Thumb instruction sequence. This is why it crashes.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1576432

Title:
  gdb crashes when trying to start a debugging session

Status in gdb:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  This bug log applies to Ubuntu Mate for raspberry PI.

  I cannot use gdb to debug a program. See below. This happens on any
  program, even programs that come with ubuntu, for example try gdb
  /bin/less. It always crashes in  d-linux-armhf.so.3

  gdb mythfrontend
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from mythfrontend...done.
  (gdb) start
  Temporary breakpoint 1 at 0x62c22: file main.cpp, line 1674.
  Starting program: 
/srv/storage/homexenial/peter/proj/mythtv-build/myth-p28/usr/bin/mythfrontend

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1576432] Re: gdb crashes when trying to start a debugging session

2018-05-01 Thread Chris Coulson
(Note, I looked at this because it was breaking rustc tests on armhf.
The workaround is the same - install libc6-dbg to make the crash go
away)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1576432

Title:
  gdb crashes when trying to start a debugging session

Status in gdb:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  This bug log applies to Ubuntu Mate for raspberry PI.

  I cannot use gdb to debug a program. See below. This happens on any
  program, even programs that come with ubuntu, for example try gdb
  /bin/less. It always crashes in  d-linux-armhf.so.3

  gdb mythfrontend
  GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "arm-linux-gnueabihf".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from mythfrontend...done.
  (gdb) start
  Temporary breakpoint 1 at 0x62c22: file main.cpp, line 1674.
  Starting program: 
/srv/storage/homexenial/peter/proj/mythtv-build/myth-p28/usr/bin/mythfrontend

  Program received signal SIGSEGV, Segmentation fault.
  0x76fd9822 in ?? () from /lib/ld-linux-armhf.so.3
  (gdb)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-06 Thread Chris Coulson
This is a deliberate change in binutils-2.29, which changes how the ADR
instruction works with Thumb function symbols:

https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;a=commit;h=52a86f843b6dee1de9977293da9786649b146b05

There are some changes in openssl which work around this:

https://git.openssl.org/?p=openssl.git;a=commit;h=11208dcfb9105e8afa37233185decefd45e89e17
https://git.openssl.org/?p=openssl.git;a=commit;h=b82acc3c1a7f304c9df31841753a0fa76b5b3cda

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  Invalid
Status in gcc-7 package in Ubuntu:
  Invalid
Status in openssl package in Ubuntu:
  In Progress
Status in binutils source package in Artful:
  Invalid
Status in gcc-7 source package in Artful:
  Invalid
Status in openssl source package in Artful:
  In Progress
Status in binutils source package in Bionic:
  Invalid
Status in gcc-7 source package in Bionic:
  Invalid
Status in openssl source package in Bionic:
  In Progress

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-04 Thread Chris Coulson
I also verified that with this workaround for the first instruction, the
non-NEON path passes the test, by removing this block from
sha256-armv4.S:

#if __ARM_MAX_ARCH__>=7 && !defined(__KERNEL__)
ldr r12,.LOPENSSL_armcap
ldr r12,[r3,r12]@ OPENSSL_armcap_P
tst r12,#ARMV8_SHA256
bne .LARMv8
tst r12,#ARMV7_NEON
bne .LNEON
#endif

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-04 Thread Chris Coulson
I stepped through 2 builds side-by-side in gdb - one good build built
with gcc 7.1, and one bad build, built with gcc 7.2. I managed to narrow
it down to a bug in sha256_block_data_order.

One of the first differences I spotted was that the good build branches
almost immediately to a NEON code path (sha256_block_data_order_neon),
whereas the broken build continues on the non-NEON code path.

If we look at the first few instructions of sha256_block_data_order in a
good build:

   0xf7699c60 <+0>: sub r3, pc, #8
   0xf7699c64 <+4>: ldr r12, [pc, #-40] ; 0xf7699c44
   0xf7699c68 <+8>: ldr r12, [r3, r12]

The first instruction basically loads the address of the start of the
function in to %r3, which we can see if we step past it:

(gdb) info registers 
r0 0x413558 4273496
r1 0x413580 4273536
r2 0x1  1
r3 0xf7699c60   4150893664
r4 0x413558 4273496
r5 0xfffef35c   4294898524
r6 0x0  0
r7 0x413580 4273536
r8 0x0  0
r9 0xf77efab8   4152294072
r100xf77b9dec   4152073708
r110x0  0
r120x0  0
sp 0xfffef2c8   0xfffef2c8
lr 0xf7697e5c   -144081316
pc 0xf7699c64   0xf7699c64 
cpsr   0x80080010   -2146959344
(gdb) p sha256_block_data_order
$1 = {} 0xf7699c60 

The second instruction loads a value from an address 40 bytes before the 
instruction in to %r12. Looking in sha256-armv4.S, this value is 
"OPENSSL_armcap_P - sha256_block_data_order", or the offset of OPENSSL_armcap_P 
from the start of sha256_block_data_order.
The third instruction loads the value of OPENSSL_armcap_P in to %r12.

Stepping through these instructions gives this state:

(gdb) info registers 
r0 0x413558 4273496
r1 0x413580 4273536
r2 0x1  1
r3 0xf7699c60   4150893664
r4 0x413558 4273496
r5 0xfffef35c   4294898524
r6 0x0  0
r7 0x413580 4273536
r8 0x0  0
r9 0xf77efab8   4152294072
r100xf77b9dec   4152073708
r110x0  0
r120x3  3
sp 0xfffef2c8   0xfffef2c8
lr 0xf7697e5c   -144081316
pc 0xf7699c6c   0xf7699c6c 
cpsr   0x80080010   -2146959344

So the value of OPENSSL_armcap_P is 3, which causes the following
instructions to take the NEON path:

   0xf7699c6c <+12>:tst r12, #16
   0xf7699c70 <+16>:bne 0xf769b660 
   0xf7699c74 <+20>:tst r12, #1
   0xf7699c78 <+24>:bne 0xf769aa60 

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-04 Thread Chris Coulson
Continuing debugging the broken build, if we look at the first few
instructions of sha256_block_data_order:

   0x004160c0 <+0>: subwr3, pc, #3
   0x004160c4 <+4>: ldr.w   r12, [pc, #-36] ; 0x4160a4
   0x004160c8 <+8>: ldr.w   r12, [r3, r12]

This looks similar to before - the intention being that %r3 is loaded
with the address of the start of the function, %r12 is loaded with the
offset of OPENSSL_armcap_P from the start of the function, then %r12 is
loaded with the value of OPENSSL_armcap_P.

However, the first instruction is broken - the #3 should be a #4.
Stepping past it produces this state:

(gdb) info registers 
r0 0x4b7558 4945240
r1 0x4b7580 4945280
r2 0x1  1
r3 0x4160c1 4284609
r4 0x4b7558 4945240
r5 0xfffef44c   4294898764
r6 0x0  0
r7 0x4b7580 4945280
r8 0x3  3
r9 0xfffef44c   4294898764
r100x0  0
r110x0  0
r120x0  0
sp 0xfffef3b8   0xfffef3b8
lr 0x414387 4277127
pc 0x4160c4 0x4160c4 
cpsr   0x40080030   1074266160
(gdb) p sha256_block_data_order
$1 = {} 0x4160c0 

Now, %r3 is the address of the start of the function, off-by-1.
Continuing to step through demonstrates that we load the wrong value in
to %r12, and this causes the non-NEON code path to be executed, which
somehow doesn't work.

If I step past these first 3 instructions, and then write the expected
value of OPENSSL_armcap_P in to %r12, the test completes successfully:

(gdb) info registers 
r0 0x4b7558 4945240
r1 0x4b7580 4945280
r2 0x1  1
r3 0x4160c1 4284609
r4 0x4b7558 4945240
r5 0xfffef44c   4294898764
r6 0x0  0
r7 0x4b7580 4945280
r8 0x3  3
r9 0xfffef44c   4294898764
r100x0  0
r110x0  0
r120x10016777216
sp 0xfffef3b8   0xfffef3b8
lr 0x414387 4277127
pc 0x4160cc 0x4160cc 
cpsr   0x40080030   1074266160
(gdb) set $r12 = 3
(gdb) info registers 
r0 0x4b7558 4945240
r1 0x4b7580 4945280
r2 0x1  1
r3 0x4160c1 4284609
r4 0x4b7558 4945240
r5 0xfffef44c   4294898764
r6 0x0  0
r7 0x4b7580 4945280
r8 0x3  3
r9 0xfffef44c   4294898764
r100x0  0
r110x0  0
r120x3  3
sp 0xfffef3b8   0xfffef3b8
lr 0x414387 4277127
pc 0x4160cc 0x4160cc 
cpsr   0x40080030   1074266160
(gdb) cont
Continuing.
Testing SHA-256 .
Breakpoint 1, EVP_Digest (data=0x47f38c, count=56, md=0xfffef44c 
"\272x\026\277\217\001\317\352AA@\336]\256\"#\260\003a\243\226\027z\234\264\020\377a\362",
 size=0x0, type=0x4aff00 , impl=0x0)
at digest.c:353
353 digest.c: No such file or directory.
(gdb)

Yay!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-04 Thread Chris Coulson
The incorrect instruction at the start of sha256_block_data_order comes
from the ADR pseudo-instruction in sha256-armv4.S:

.global sha256_block_data_order
.type   sha256_block_data_order,%function
sha256_block_data_order:
#if __ARM_ARCH__<7
sub r3,pc,#8@ sha256_block_data_order
#else
adr r3,sha256_block_data_order
#endif

The ADR instruction assembles to a SUB in our case, and it appears to do
this incorrectly in Thumb mode. Adding a binutils task for this.

** Also affects: binutils (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-04 Thread Chris Coulson
On the broken build, the first thing to notice is that when entering
sha256_block_data_order, we are running in Thumb mode, as bit 5 of the
status register is set:

(gdb) info registers
r0 0x4b7558 4945240 
r1 0x4b7580 4945280 
r2 0x1  1   
r3 0x0  0   
r4 0x4b7558 4945240 
r5 0xfffef44c   4294898764  
r6 0x0  0   
r7 0x4b7580 4945280 
r8 0x3  3   
r9 0xfffef44c   4294898764  
r100x0  0   
r110x0  0   
r120x0  0   
sp 0xfffef3b8   0xfffef3b8  
lr 0x414387 4277127 
pc 0x4160c0 0x4160c0   
 
cpsr   0x40080030   1074266160

The good build was not running in Thumb mode. sha256-armv4.S enables
Thumb instructions if __thumb2__ is defined by the compiler, see:

.text
#if __ARM_ARCH__<7
.code   32
#else
.syntax unified
# ifdef __thumb2__
.thumb
# else
.code   32
# endif
#endif

Sure enough, there's a difference between the 2 tested gcc builds.

Bad build:
$ gcc -dM -E - < /dev/null | grep __thumb2__
#define __thumb2__ 1
$

Good build:
$ gcc -dM -E - < /dev/null | grep __thumb2__
$

Looking in the changelog for gcc-7, I see the following comment for 7.2.0-2:
  * Restore configuring with --with-mode=thumb on armhf. Closes: #873584.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1729850] Re: artful openssl FTBFS on armhf

2017-11-04 Thread Chris Coulson
Changing the start of sha256_block_data_order in sha256-armv4.S to avoid
the use of the ADR pseudo-instruction like this:

global sha256_block_data_order
.type   sha256_block_data_order,%function
sha256_block_data_order:
#ifdef __thumb2__
sub r3,pc,#4@ sha256_block_data_order
#else
sub r3,pc,#8@ sha256_block_data_order
#endif

... seems to work:

$ ../util/shlib_wrap.sh ./sha256t   
 
Testing SHA-256 ... passed. 
Testing SHA-224 ... passed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1729850

Title:
  artful openssl FTBFS on armhf

Status in binutils package in Ubuntu:
  New
Status in gcc-7 package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  New

Bug description:
  openssl FTBFS on artful armhf with the following:

  ../util/shlib_wrap.sh ./sha256t
  Testing SHA-256 
  TEST 1 of 3 failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1729850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260014] Re: Add an API to manage local data (cookies, local storage, app cache, indexed DB and web DB)

2017-03-31 Thread Chris Coulson
This is separate from autofill profiles, but will be necessary to clear
site-specific autocomplete data.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1260014

Title:
  Add an API to manage local data (cookies, local storage, app cache,
  indexed DB and web DB)

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  A modern browser application should offer as an advanced feature a way
  to manage cookies (list them, selectively delete some, clear all).
  Oxide needs to expose such an API.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1214048] Re: Initial support for autofill

2017-03-31 Thread Chris Coulson
** Summary changed:

- Support autofill
+ Initial support for autofill

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1214048

Title:
  Initial support for autofill

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Add support for autofill. I'm not sure how this will be implemented
  yet - Chromium has a re-usable component (//components/autofill), but
  it pulls in stuff like //components/infobars/core so I'm not sure
  whether it's really suitable for us or whether we're going to end up
  with our own autofill implementation (a not insignificant amount of
  work).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1214048] Re: Support autofill

2017-03-22 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.22 => branch-1.23

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1214048

Title:
  Support autofill

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Add support for autofill. I'm not sure how this will be implemented
  yet - Chromium has a re-usable component (//components/autofill), but
  it pulls in stuff like //components/infobars/core so I'm not sure
  whether it's really suitable for us or whether we're going to end up
  with our own autofill implementation (a not insignificant amount of
  work).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2017-03-22 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.22 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-03-17 Thread Chris Coulson
** Changed in: oxide/1.21
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-03-08 Thread Chris Coulson
** Changed in: oxide/1.21
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-02-28 Thread Chris Coulson
** Changed in: oxide/1.21
Milestone: 1.21.2 => 1.21.3

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1667662] Re: SRU: backport rustc to 14.04 and 16.04

2017-02-24 Thread Chris Coulson
In case it's not clear, rustc needs to exist in the security pocket for
each release

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1667662

Title:
  SRU: backport rustc to 14.04 and 16.04

Status in binutils package in Ubuntu:
  New
Status in cmake package in Ubuntu:
  New
Status in llvm-toolchain-3.9 package in Ubuntu:
  New
Status in llvm-toolchain-4.0 package in Ubuntu:
  New
Status in rustc package in Ubuntu:
  New

Bug description:
  newer firefox versions will require rust as a build dependency.
  Backport the recent rustc version and cmake, binutils, llvm versions
  from xenial to trusty.  It looks like xenial is recent and only needs
  the llvm backport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1667662/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-02-23 Thread Chris Coulson
** Changed in: oxide
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Released
Status in Oxide 1.21 series:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-02-21 Thread Chris Coulson
** Also affects: oxide/1.21
   Importance: Undecided
   Status: New

** Changed in: oxide/1.21
   Importance: Undecided => High

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

** Changed in: oxide/1.21
Milestone: None => 1.21.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Committed
Status in Oxide 1.21 series:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-02-21 Thread Chris Coulson
** Changed in: webbrowser-app (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665978] Re: Double-tap to zoom does not work anymore in OTA-15

2017-02-21 Thread Chris Coulson
https://git.launchpad.net/~oxide-
developers/oxide/+git/chromium/commit/?id=6cc6d8dd554737b28aa8908041b0c35a6d9c599d

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

** Changed in: oxide
   Status: New => Fix Committed

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

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665978

Title:
  Double-tap to zoom does not work anymore in OTA-15

Status in Oxide:
  Fix Committed
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Double-Tapping on an element on a web page used to zoom in on that
  element. Since OTA-15, doeble-tap does nothing.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1665655] [NEW] Scrolling over addressbar shouldn't scroll webview

2017-02-17 Thread Chris Coulson
Public bug reported:

Steps to reproduce:

1) Move mouse pointer to addressbar (over the text entry).
2) Use the scroll wheel.

What should happen:

Nothing

What happens:

The webview content scrolls

** Affects: oxide
 Importance: Medium
 Status: Triaged

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

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

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1665655

Title:
  Scrolling over addressbar shouldn't scroll webview

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1) Move mouse pointer to addressbar (over the text entry).
  2) Use the scroll wheel.

  What should happen:

  Nothing

  What happens:

  The webview content scrolls

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

2017-02-10 Thread Chris Coulson
Hrmmm, does X crash here too?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1560994

Title:
  webbrowser-app crashed with SIGABRT in
  oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  Crash upon maximizimg window.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160318-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar 23 14:37:35 2016
  ExecutablePath: /usr/bin/webbrowser-app
  InstallationDate: Installed on 2016-03-08 (14 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
  ProcCmdline: webbrowser-app
  Signal: 6
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0
   __run_exit_handlers (status=1, listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
   __GI_exit (status=) at exit.c:104
  Title: webbrowser-app crashed with SIGABRT in __run_exit_handlers()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1560994/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1649262] Re: webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

2017-02-10 Thread Chris Coulson
This is not a bug in Oxide - the CHECK failure in this case is a red
herring and is a side effect of a bug elsewhere that triggers an unclean
exit() (see bug 1663609)

** Project changed: oxide => qtdeclarative-opensource-src (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.net/bugs/1649262

Title:
  webbrowser app Segmentation fault (core dumped) on 17.04 Unity7

Status in Canonical System Image:
  Confirmed
Status in qtdeclarative-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  17.04 unity7

  ~$ webbrowser-app 
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file
  '/run/user/1000/dconf/user': Permission denied.  dconf will not work
  properly.

  (webbrowser-app:4695): dconf-CRITICAL **: unable to create file 
'/run/user/1000/dconf/user': Permission denied.  dconf will not work properly.
  UCUriHandler: Empty "APP_ID" environment variable, ignoring.
  unity::action::ActionManager::ActionManager(QObject*):
Could not determine application identifier. HUD will not work properly.
Provide your application identifier in $APP_ID environment variable.
  libGL error: MESA-LOADER: failed to retrieve device information
  libGL error: Version 4 or later of flush extension not found
  libGL error: failed to load driver: i915
  libGL error: MESA-LOADER: failed to retrieve device information
  could not open containers config file  
"/home/pixel/.local/share/libertine/ContainersConfig.json"
  APP_ID isn't set, the handler can not be registered
  Input device added: "Power Button" "/dev/input/event1" QFlags(0x1)
  Input device added: "Power Button" "/dev/input/event0" QFlags(0x1)
  Input device added: "HDA Intel PCH Line Out" "/dev/input/event7" QFlags(0x20)
  Input device added: "HDA Intel PCH Rear Mic" "/dev/input/event5" QFlags(0x20)
  Input device added: "HDA Intel PCH Line" "/dev/input/event6" QFlags(0x20)
  Input device added: "YSPRINGTECH USB OPTICAL MOUSE" "/dev/input/event2" 
QFlags(0x2)
  Input device added: "USB USB Keykoard" "/dev/input/event3" QFlags(0x1|0x10)
  Input device added: "USB USB Keykoard" "/dev/input/event4" QFlags(0x1)

  (webbrowser-app:4695): IBUS-WARNING **: Unable to connect to ibus: Could not 
connect: Permission denied
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  QOpenGLShader: could not create shader
  APP_ID isn't set, the handler ignored
  qml: Loaded 13 UA override(s) from 
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Web/ua-overrides-desktop.js
  ^CSegmentation fault (core dumped)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1560994] Re: webbrowser-app crashed with SIGABRT in oxide::BrowserProcessMainImpl::~BrowserProcessMainImpl

2017-02-07 Thread Chris Coulson
The abort here is a red herring and is masking the primary issue, which
you can see a few frames further down:

#5  0x7f87c8e3d088 in __run_exit_handlers (status=status@entry=1, 
listp=0x7f87c91c75f8 <__exit_funcs>, 
run_list_atexit=run_list_atexit@entry=true) at exit.c:82
atfct = 
onfct = 
cxafct = 
#6  0x7f87c8e3d0d5 in __GI_exit (status=status@entry=1) at exit.c:104
No locals.
#7  0x7f87bd0d2ea1 in gdk_x_io_error (display=) at 
/build/gtk+2.0-KsZKkB/gtk+2.0-2.24.30/gdk/x11/gdkmain-x11.c:544
No locals.
#8  0x7f87c8387cee in _XIOError (dpy=dpy@entry=0x5646ce4eb0f0) at 
../../src/XlibInt.c:1464
No locals.
#9  0x7f87c8385d4a in _XReply (dpy=dpy@entry=0x5646ce4eb0f0, 
rep=rep@entry=0x7ffebcbf6160, extra=extra@entry=0, discard=discard@entry=1) at 
../../src/xcb_io.c:708
error = 0x0
c = 
reply = 0x0
current = 0x5646cf5f8b60
__PRETTY_FUNCTION__ = "_XReply"
#10 0x7f87c838148d in XSync (dpy=0x5646ce4eb0f0, discard=0) at 
../../src/Sync.c:44
rep = {type = 167 '\247', revertTo = 98 'b', sequenceNumber = 48319, 
length = 28, focus = 3465286592, pad1 = 0, pad2 = 3166658864, pad3 = 32766, 
pad4 = 32, pad5 = 0}
#11 0x7f87c764deda in dri2SwapBuffers () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
No symbol table info available.
#12 0x7f87cb956342 in QGLXContext::swapBuffers(QPlatformSurface*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so
No symbol table info available.
#13 0x7f87ca495326 in QOpenGLContext::swapBuffers(QSurface*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
No symbol table info available.
#14 0x7f87cae4978e in QSGGuiThreadRenderLoop::renderWindow(QQuickWindow*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
#15 0x7f87cae4a521 in QSGGuiThreadRenderLoop::event(QEvent*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
No symbol table info available.
#16 0x7f87cb20e05c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#17 0x7f87cb213516 in QApplication::notify(QObject*, QEvent*) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
No symbol table info available.
#18 0x7f87c9cf45bb in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#19 0x7f87c9d4986d in QTimerInfoList::activateTimers() () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#20 0x7f87c9d49d71 in timerSourceDispatch(_GSource*, int (*)(void*), void*) 
() from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#21 0x7f87c86cc127 in g_main_context_dispatch () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#22 0x7f87c86cc380 in g_main_context_iterate.isra () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#23 0x7f87c86cc42c in g_main_context_iteration () from 
/tmp/apport_sandbox_hx8GUx/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#24 0x7f87c9d4aa4f in 
QEventDispatcherGlib::processEvents(QFlags) () 
from /tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#25 0x7f87c9cf1d7a in 
QEventLoop::exec(QFlags) () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#26 0x7f87c9cf9e1c in QCoreApplication::exec() () from 
/tmp/apport_sandbox_hx8GUx/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
No symbol table info available.
#27 0x5646ccf87e26 in BrowserApplication::run (this=0x7ffebcbf6930) at 
/build/webbrowser-app-W5j7m8/webbrowser-app-0.23+16.04.20160318/src/app/browserapplication.cpp:261
No locals.
#28 0x5646ccf7ca85 in main (argc=1, argv=0x7ffebcbf6a88) at 
/build/webbrowser-app-W5j7m8/webbrowser-app-0.23+16.04.20160318/src/app/webbrowser/webbrowser-app.cpp:122
app = { = { = {}, 
static staticMetaObject = {d = {superdata = 0x7f87cb710140 
, stringdata = 0x5646ccfca9c0 
, data = 0x5646ccfca960 
, static_metacall = 0x5646ccf92bf0 
, relatedMetaObjects = 0x0, extradata = 0x0}}, m_arguments = 
{ = { = {}, {p = 
{static shared_null = {ref = {atomic = {_q_value = -1}}, alloc = 0, begin = 0, 
end = 0, array = {0x0}}, d = 0x5646ce80fbe0}, d = 0x5646ce80fbe0}}, }, m_engine = 0x5646ce818880, m_window = 0x5646ce8c13c0, m_component = 
0x5646ce8b8570, m_webbrowserWindowProxy = 

[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2017-02-06 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.21 => branch-1.22

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1568296] Re: Make JS dialogs app modal

2017-02-01 Thread Chris Coulson
I should point out that the change which landed for this doesn't
actually make dialogs application modal, as the dialog implementation is
window modal at best. But we only ever display 1 script opened dialog at
a time now.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1568296

Title:
  Make JS dialogs app modal

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Chrome only supports app-modal JS dialogs, and so does Blink
  (window.alert blocks the calling process).

  Oxide pretends to support tab-modal JS dialogs by having a per-WebContents 
dispatch queue. However, the behaviour is quite broken:
  - It's really app-modal in single process because there's only a single 
RenderThread.
  - In multi-process it's not really tab-modal - it's render-process modal (ie, 
only a single tab in a render process can show a JS dialog). So, if 2 tabs live 
in separate processes then they can display JS dialogs at the same time. But if 
they're from the same SiteInstance and live in the same process, they can't.

  We should just change the dispatch of JS dialogs to be application
  modal instead, so it behaves consistently in all configurations.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1568296] Re: Make JS dialogs app modal

2017-01-31 Thread Chris Coulson
** Changed in: oxide
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1568296

Title:
  Make JS dialogs app modal

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Chrome only supports app-modal JS dialogs, and so does Blink
  (window.alert blocks the calling process).

  Oxide pretends to support tab-modal JS dialogs by having a per-WebContents 
dispatch queue. However, the behaviour is quite broken:
  - It's really app-modal in single process because there's only a single 
RenderThread.
  - In multi-process it's not really tab-modal - it's render-process modal (ie, 
only a single tab in a render process can show a JS dialog). So, if 2 tabs live 
in separate processes then they can display JS dialogs at the same time. But if 
they're from the same SiteInstance and live in the same process, they can't.

  We should just change the dispatch of JS dialogs to be application
  modal instead, so it behaves consistently in all configurations.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1590561] Re: webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found

2017-01-27 Thread Chris Coulson
Oxide failing to create a GL context isn't your only issue here, as Qt
also fails to create one (which happens completely independently of
Oxide)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1590561

Title:
  webbrowser-app crashes on startup on fresh zesty Unity8: No suitable
  EGL configs found

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When trying to start webbrowser-app a unresponsive window appears and
  after a few moments it crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jun  8 22:56:35 2016
  InstallationDate: Installed on 2016-04-28 (41 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

2017-01-24 Thread Chris Coulson
** Changed in: oxide/1.20
   Status: Fix Committed => Fix Released

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1649861

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  Fix Released
Status in Oxide 1.19 series:
  Fix Released
Status in Oxide 1.20 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1656551] Re: webbrowser only partially loads some https sites after accepting self-signed certificate once

2017-01-16 Thread Chris Coulson
It's basically hitting the same issue as
https://bugs.chromium.org/p/chromium/issues/detail?id=664177 because the
build was 10 weeks old from yesterday (actually, it's not quite, but the
build date recorded in the build is the first Sunday of the month, which
is 6th November for the version of Oxide in OTA-14).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1656551

Title:
  webbrowser only partially loads some https sites after accepting self-
  signed certificate once

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The browser on my Ubuntu Phone (Meizu MX-4, OTA 15) does not open some 
https-secured sites correctly, such as https://www.amazon.com or 
https://www.amazon.de. The browser presents a warning about an invalid ssl 
certificate, although the certificate appears perfectly valid. It then presents 
the option to go back to a safe site or continue anyway. If I choose continue 
anyway, it starts to load the site, but never completes. After some time it 
stops loading and displays a rather incomplete version of the site. It is 
clearly composed of only some of the pages' elements and incomplete.The amount 
of the page that is displayed varies from time to time.
  It appears that transmission times out while loading the page.
  Test case:
  1) Try loading https://www.amazon.com. Observe that webbrowser-app displays 
warning about invalid certificate, without any apparent reason. Chose  
"continue anyway". Observe, that the site is only incompletely loaded and 
unsable.
  2) Try loading the web interface of my router: https://rkupper.no-ip.org/. 
This site uses a self-signed certificate, which is correctly displayed as a 
security risk. But self-signed certificates are a common use case on DSL or 
cable routers' web interfaces. Choose "continue anyway". You should see the 
login page of a fritz box router. Observe that the site is incompletely loaded 
and the login button does nothing at all.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1568296] Re: Make JS dialogs app modal

2017-01-16 Thread Chris Coulson
** Changed in: oxide
Milestone: None => branch-1.21

** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1568296

Title:
  Make JS dialogs app modal

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  Chrome only supports app-modal JS dialogs, and so does Blink
  (window.alert blocks the calling process).

  Oxide pretends to support tab-modal JS dialogs by having a per-WebContents 
dispatch queue. However, the behaviour is quite broken:
  - It's really app-modal in single process because there's only a single 
RenderThread.
  - In multi-process it's not really tab-modal - it's render-process modal (ie, 
only a single tab in a render process can show a JS dialog). So, if 2 tabs live 
in separate processes then they can display JS dialogs at the same time. But if 
they're from the same SiteInstance and live in the same process, they can't.

  We should just change the dispatch of JS dialogs to be application
  modal instead, so it behaves consistently in all configurations.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2017-01-11 Thread Chris Coulson
** Changed in: oxide
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

2017-01-05 Thread Chris Coulson
** Changed in: oxide/1.20
Milestone: 1.20.0 => 1.20.2

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1649861

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  In Progress
Status in Oxide 1.19 series:
  Confirmed
Status in Oxide 1.20 series:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-12-14 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-12-14 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1649861] Re: When upgrading to oxide 1.19, tabs from saved session are not restored

2016-12-14 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.20 => branch-1.21

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1649861

Title:
  When upgrading to oxide 1.19, tabs from saved session are not restored

Status in Oxide:
  Confirmed
Status in Oxide 1.19 series:
  Confirmed
Status in Oxide 1.20 series:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  When upgrading to oxide 1.19, tabs from a session saved with oxide
  1.18 are not restored. I’m seeing the following in the browser’s log:

Failed to read initial state: invalid data

  It appears sessions::SerializedNavigationEntry::ReadFromPickle()
  fails, most likely because the format of the serialized entries was
  changed in chromium 55. Specifically, this commit seems like a good
  suspect:
  
https://chromium.googlesource.com/chromium/src/+/f62ca6f9d33e93733fccb3f3815d9554429dbb38.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1638663] Re: Segfault on arm64 dragonboard

2016-11-02 Thread Chris Coulson
** Package changed: oxide-qt (Ubuntu) => oxide

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1638663

Title:
  Segfault on arm64 dragonboard

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  the following is output from the webbrowser-app or webview-demo snaps
  on arm64 dragoonboard with latest core.

  Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0'
  [1102/181614:WARNING:audio_manager.cc(314)] Multiple instances of 
AudioManager detected
  [1102/181614:WARNING:audio_manager.cc(275)] Multiple instances of 
AudioManager detected
  [1102/181614:ERROR:layer_tree_host_impl.cc(2250)] Forcing zero-copy tile 
initialization as worker context is missing
  Segmentation fault

  The screen flashes white just before the crash

  Browser from Nov 1 build at 
https://code.launchpad.net/~kgunn72/+snap/ubunutu-browser-snap
  Webbiew from Oct 20 at 
  https://code.launchpad.net/~osomon/+snap/webview-snap-demo/+build/7599

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-10-28 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.19 => branch-1.20

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()

2016-10-28 Thread Chris Coulson
** Changed in: oxide
   Status: Triaged => Fix Released

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

** Changed in: oxide
 Assignee: (unassigned) => Santosh (santoshbit2007)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1610929

Title:
  Implement Screen::GetShellMode()

Status in Mir:
  New
Status in Oxide:
  Fix Released
Status in unity8 package in Ubuntu:
  New

Bug description:
  This is currently just a stub that returns NonWindowed on mobile
  devices and Windowed everywhere else. It needs to be more intelligent
  than that (eg, Windowed on a tablet device) and needs to be dynamic,
  but I don't think there's a way for us to do that yet.

  Basically, we need to know whether the shell is in windowed or staged
  mode. The display's form factor isn't particularly relevant.

  This is needed to complete bug 1545088 and others.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1338180] Re: [Browser] iframe doesn't display anything when a load fails

2016-10-28 Thread Chris Coulson
So, the fix for this is that the error page will be implemented in HTML
and live in the new UbuntuWebView implementation inside Oxide.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1338180

Title:
  [Browser] iframe doesn't display anything when a load fails

Status in Oxide:
  Triaged
Status in Ubuntu UX:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Ex : http://jsfiddle.net/zHR89/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1524376] Re: One site started giving standard "Network error" on a single phone

2016-10-07 Thread Chris Coulson
There's not much point in keeping this bug open (see my last comment),
so I'm going to close it for now. Feel free to reopen if you this might
be a bug in Oxide

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

** No longer affects: webbrowser-app (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1524376

Title:
  One site started giving standard "Network error" on a single phone

Status in Oxide:
  Invalid

Bug description:
  Browsing to http://www.uusisuomi.fi/ now gives me a standard Network
  Error immediately instead of loading. This only happens for this
  single site, and only in my daily use Bq using stable OTA-8.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1629219] Re: Blockiness in rendering when run under unity8

2016-10-05 Thread Chris Coulson
** Changed in: oxide
   Importance: Undecided => High

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

** No longer affects: webbrowser-app (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1629219

Title:
  Blockiness in rendering when run under unity8

Status in Oxide:
  Triaged

Bug description:
  Parts of the welcome page render all strange with weird blocks all
  over, see attached screenshot

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1629219] Re: Blockiness in rendering when run under unity8

2016-10-05 Thread Chris Coulson
Can you paste the contents of chrome://gpu/ please?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1629219

Title:
  Blockiness in rendering when run under unity8

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  Parts of the welcome page render all strange with weird blocks all
  over, see attached screenshot

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1435465] Re: Alt+F4 crashes app where WebView embedded in a Window

2016-09-30 Thread Chris Coulson
Running it in valgrind gives a clue:

==19941== Invalid read of size 4
==19941==at 0x6604DA4: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1)
==19941==by 0x1877174F: ???
==19941==by 0xFFFD: ???
==19941==by 0x2483D3FE: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x27C117AB: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x27C36ADC: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x27C3DDD3: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x27C3E1A8: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x24861F42: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x24861FF8: ??? (in 
/usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0)
==19941==by 0x2414E312: 
QScopedPointerDeleter::cleanup(oxide::qt::WebViewProxy*)
 (in /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x2414D996: QScopedPointer::~QScopedPointer() (in 
/usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x241467FB: 
OxideQQuickWebViewPrivate::~OxideQQuickWebViewPrivate() (in 
/usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x24146847: 
OxideQQuickWebViewPrivate::~OxideQQuickWebViewPrivate() (in 
/usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x2414E4D6: 
QScopedPointerDeleter::cleanup(OxideQQuickWebViewPrivate*)
 (in /usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x2414DED6: QScopedPointer::~QScopedPointer() (in 
/usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x24147E1C: OxideQQuickWebView::~OxideQQuickWebView() (in 
/usr/lib/x86_64-linux-gnu/libOxideQtQuick.so.0)
==19941==by 0x240855BD: 
QQmlPrivate::QQmlElement::~QQmlElement() (in 
/usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide/libqmloxideplugin.so)
==19941==by 0x240855F3: 
QQmlPrivate::QQmlElement::~QQmlElement() (in 
/usr/lib/x86_64-linux-gnu/qt5/qml/com/canonical/Oxide/libqmloxideplugin.so)
==19941==by 0x64BE52A: QObjectPrivate::deleteChildren() (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1)
==19941==by 0x64C7D9F: QObject::~QObject() (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.5.1)
==19941==by 0x5DBD028: QWindow::~QWindow() (in 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.5.1)
==19941==by 0x4FD26E8: QQuickWindow::~QQuickWindow() (in 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.5.1)
==19941==by 0x50AA74C: 
QQmlPrivate::QQmlElement::~QQmlElement() (in 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.5.1)
==19941==by 0x405115: main (in /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene)
==19941==  Address 0x151bcd9e is 18 bytes before a block of size 664 alloc'd
==19941==at 0x4C2E0EF: operator new(unsigned long) (in 
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==19941==by 0x50A96E9: QQuickWindowQmlImpl::QQuickWindowQmlImpl(QWindow*) 
(in /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.5.1)
==19941==by 0x50AA78F: void 
QQmlPrivate::createInto(void*) (in 
/usr/lib/x86_64-linux-gnu/libQt5Quick.so.5.5.1)
==19941==by 0x547B71A: QQmlType::create() const (in 
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.5.1)
==19941==by 0x54DCE23: QQmlObjectCreator::createInstance(int, QObject*, 
bool) (in /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.5.1)
==19941==by 0x54DD8CE: QQmlObjectCreator::create(int, QObject*, 
QQmlInstantiationInterrupt*) (in /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.5.1)
==19941==by 0x5465B04: QQmlComponentPrivate::beginCreate(QQmlContextData*) 
(in /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.5.1)
==19941==by 0x546378E: QQmlComponent::create(QQmlContext*) (in 
/usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.5.1)
==19941==by 0x404F0F: main (in /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene)

So we're accessing the window after it's been deleted.

Some stepping through in gdb shows that this access occurs here:

oxide::qt::InputMethodContext::FocusedNodeChanged (this=0xb426d0) at 
../../oxide/qt/core/browser/input/oxide_qt_input_method_context.cc:236
236   QGuiApplication::focusWindow()->focusObject()) {
(gdb) bt
#0  0x7fffb699d3fe in oxide::qt::InputMethodContext::FocusedNodeChanged() 
(this=0xb426d0) at 
../../oxide/qt/core/browser/input/oxide_qt_input_method_context.cc:236
#1  0x7fffb8edf9fc in 
oxide::ImeBridgeImpl::SetContext(oxide::InputMethodContext*) (this=0xaea948, 
context=0x0) at ../../oxide/shared/browser/input/oxide_ime_bridge_impl.cc:109
#2  0x7fffb8f04d4d in 
oxide::WebContentsView::SetClient(oxide::WebContentsViewClient*) 
(this=0xcbe100, client=) at 
../../oxide/shared/browser/oxide_web_contents_view.cc:786
#3  0x7fffb8f09790 in oxide::WebView::~WebView() (this=0xb62660, 
__in_chrg=) at ../../oxide/shared/browser/oxide_web_view.cc:984
#4  0x7fffb8f098f9 in oxide::WebView::~WebView() (this=0xb62660, 
__in_chrg=) at 

[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-09-23 Thread Chris Coulson
** Changed in: oxide
Milestone: None => branch-1.19

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1435465] Re: Alt+F4 crashes app

2016-09-14 Thread Chris Coulson
*** This bug is a duplicate of bug 1448079 ***
https://bugs.launchpad.net/bugs/1448079

** This bug has been marked a duplicate of bug 1448079
   Don't run the event loop after QGuiApplication begins to tear down

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1435465

Title:
  Alt+F4 crashes app

Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  was just watching something on Youtube Web App created by unity
  itself. when i pressed alt-f4 Ubuntu said it had an error and if i
  want to submit it.

  that is all folks.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150320.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 23 19:56:16 2015
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2015-03-22 (0 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306)
  ProcCmdline: webapp-container --app-id=YouTubeyoutubecom 
--webapp=WW91VHViZQ== --enable-back-forward
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
  Title: webapp-container crashed with SIGSEGV in QMetaObject::activate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1435465/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1435332] Re: webapp-container crashed with SIGSEGV in QMetaObject::activate()

2016-09-14 Thread Chris Coulson
*** This bug is a duplicate of bug 1448079 ***
https://bugs.launchpad.net/bugs/1448079

** This bug is no longer a duplicate of bug 1435465
   Alt+F4 crashes app
** This bug has been marked a duplicate of bug 1448079
   Don't run the event loop after QGuiApplication begins to tear down

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1435332

Title:
  webapp-container crashed with SIGSEGV in QMetaObject::activate()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Occurred after I closed youtube webapp

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150320.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  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/webapp-container
  InstallationDate: Installed on 2014-12-11 (102 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  ProcCmdline: webapp-container --app-id=YouTubeyoutubecom 
--webapp=WW91VHViZQ== --enable-back-forward
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   ?? ()
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
  Title: webapp-container crashed with SIGSEGV in QMetaObject::activate()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip kismet libvirtd lpadmin plugdev 
sambashare sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1435332/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1437351] Re: webapp-container crashed with SIGSEGV in QGuiApplication::focusObject()

2016-09-14 Thread Chris Coulson
*** This bug is a duplicate of bug 1448079 ***
https://bugs.launchpad.net/bugs/1448079

** This bug is no longer a duplicate of bug 1435465
   Alt+F4 crashes app
** This bug has been marked a duplicate of bug 1448079
   Don't run the event loop after QGuiApplication begins to tear down

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1437351

Title:
  webapp-container crashed with SIGSEGV in
  QGuiApplication::focusObject()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  occurred after I closed the youtube app

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150323-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu4
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Fri Mar 27 08:56:43 2015
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2014-12-11 (106 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141210)
  ProcCmdline: webapp-container --app-id=YouTubeyoutubecom 
--webapp=WW91VHViZQ== --enable-back-forward
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f2ffc7daed4 
<_ZN15QGuiApplication11focusObjectEv+36>:   jmpq   *%rdx
   PC (0x7f2ffc7daed4) ok
   source "*%rdx" (0x736544656c694678) not located in a known VMA region 
(needed readable region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QGuiApplication::focusObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
  Title: webapp-container crashed with SIGSEGV in QGuiApplication::focusObject()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm autopilot cdrom dip kismet libvirtd lpadmin plugdev 
sambashare sudo wireshark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1437351/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1437638] Re: webapp-container crashed with SIGSEGV in QGuiApplication::focusObject()

2016-09-14 Thread Chris Coulson
*** This bug is a duplicate of bug 1448079 ***
https://bugs.launchpad.net/bugs/1448079

** This bug is no longer a duplicate of bug 1435465
   Alt+F4 crashes app
** This bug has been marked a duplicate of bug 1448079
   Don't run the event loop after QGuiApplication begins to tear down

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1437638

Title:
  webapp-container crashed with SIGSEGV in
  QGuiApplication::focusObject()

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  Can't say what exactly happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: webapp-container 0.23+15.04.20150323-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Mar 28 14:47:49 2015
  ExecutablePath: /usr/bin/webapp-container
  InstallationDate: Installed on 2014-11-02 (145 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcCmdline: webapp-container --app-id=GoogleCalendargooglecom 
--webapp=R29vZ2xlQ2FsZW5kYXI= --enable-back-forward --store-session-cookies
  SegvAnalysis:
   Segfault happened at: 0x7fa41a5fded4 
<_ZN15QGuiApplication11focusObjectEv+36>:   jmpq   *%rdx
   PC (0x7fa41a5fded4) ok
   source "*%rdx" (0x72005000650074) not located in a known VMA region (needed 
readable region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: webbrowser-app
  StacktraceTop:
   QGuiApplication::focusObject() () from 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   QMetaObject::activate(QObject*, int, int, void**) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libibusplatforminputcontextplugin.so
  Title: webapp-container crashed with SIGSEGV in QGuiApplication::focusObject()
  UpgradeStatus: Upgraded to vivid on 2015-03-28 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1437638/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-09-12 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.18 => branch-1.19

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1610929] Re: Implement Screen::GetShellMode()

2016-09-09 Thread Chris Coulson
And confined applications can't access that anyway.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1610929

Title:
  Implement Screen::GetShellMode()

Status in Mir:
  New
Status in Oxide:
  Triaged
Status in unity8 package in Ubuntu:
  New

Bug description:
  This is currently just a stub that returns NonWindowed on mobile
  devices and Windowed everywhere else. It needs to be more intelligent
  than that (eg, Windowed on a tablet device) and needs to be dynamic,
  but I don't think there's a way for us to do that yet.

  Basically, we need to know whether the shell is in windowed or staged
  mode. The display's form factor isn't particularly relevant.

  This is needed to complete bug 1545088 and others.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1620313] Re: stop using hardening-wrapper, obsoleted by recent dpkg-dev

2016-09-06 Thread Chris Coulson
Ditto for firefox (but to precise)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1620313

Title:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev

Status in firefox package in Ubuntu:
  New
Status in gtk2-engines-murrine package in Ubuntu:
  Fix Released
Status in lxc package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  New
Status in hardening-wrapper package in Debian:
  New

Bug description:
  stop using hardening-wrapper, obsoleted by recent dpkg-dev.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1620313/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

2016-09-01 Thread Chris Coulson
** Changed in: oxide/1.17
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Canonical System Image:
  Fix Committed
Status in Oxide:
  Fix Released
Status in Oxide 1.17 series:
  Fix Released
Status in webapps-sprint:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

2016-08-24 Thread Chris Coulson
** Changed in: oxide/1.17
Milestone: 1.17.4 => 1.17.5

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Canonical System Image:
  In Progress
Status in Oxide:
  In Progress
Status in Oxide 1.17 series:
  Confirmed
Status in webapps-sprint:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

2016-08-24 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.17 => branch-1.18

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Canonical System Image:
  In Progress
Status in Oxide:
  In Progress
Status in webapps-sprint:
  Fix Committed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1613257] Re: oxide-qt fails to build on yakkety due to missing hybris dependencies

2016-08-15 Thread Chris Coulson
The other Oxide issue is intermittent. It'll probably work if you retry
it

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libhybris in Ubuntu.
https://bugs.launchpad.net/bugs/1613257

Title:
  oxide-qt fails to build on yakkety due to missing hybris dependencies

Status in libhybris package in Ubuntu:
  Fix Committed
Status in oxide-qt package in Ubuntu:
  Confirmed

Bug description:
  Next problem in Oxide:

  --
  
https://launchpadlibrarian.net/279072570/buildlog_ubuntu-yakkety-armhf.oxide-qt_1.16.7-0ubuntu1_BUILDING.txt.gz

  -- Running gyp
  sh: echo: I/O error
  gyp: Call to '(echo | $(echo ${CXX_host:-$(which g++)}) -m32 -E - > /dev/null 
2>&1) && echo "-m32" || true' returned exit status 0 while in 
/«PKGBUILDDIR»/third_party/icu/icu.gyp.
  CMake Error at oxide/CMakeLists.txt:307 (message):
Running gyp failed

  
  -- Configuring incomplete, errors occurred!
  See also "/«PKGBUILDDIR»/obj-arm-linux-gnueabihf/CMakeFiles/CMakeOutput.log".
"tail -v -n +0 CMakeCache.txt"
  --

  
  Original report:

  As seen here: https://launchpad.net/ubuntu/+source/oxide-
  qt/1.16.7-0ubuntu1

  That means webbrowser-app is also unbuildable on yakkety when using
  proposed, and that the oxide-qt cannot migrate to release pocket.

  ---
  Depends: libmedia-hub-dev but it is not going to be installed
  Depends: libhybris-dev but it is not going to be installed
  ---

  Laney observes: libhybris-common1 : Depends: libc6 (< 2.24) but
  2.24-0ubuntu1 is to be installed

  Note that the bug was originally filed against oxide-qt while the
  problem probably lies in those unfulfille dependencies.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1613257/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1613278] [NEW] QScreen::name is empty

2016-08-15 Thread Chris Coulson
Public bug reported:

It looks like this isn't implemented in qtubuntu. We want to identify
the internal panel in Oxide for bug 1601887, and thought we might be
able to use this.

** Affects: qtubuntu (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1613278

Title:
  QScreen::name is empty

Status in qtubuntu package in Ubuntu:
  New

Bug description:
  It looks like this isn't implemented in qtubuntu. We want to identify
  the internal panel in Oxide for bug 1601887, and thought we might be
  able to use this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1613278/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-07-29 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.17 => branch-1.18

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-29 Thread Chris Coulson
** Changed in: oxide
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1605218] Re: Google account login using 2FA isn’t remembered across sessions

2016-07-21 Thread Chris Coulson
The only time the browser should restore session cookies is after a
crash or some other abnormal shutdown. Restoring should never be the
default as it turns session cookies in to permanent cookies - they will
never expire, as they don't have an expiration date.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1605218

Title:
  Google account login using 2FA isn’t remembered across sessions

Status in webbrowser-app package in Ubuntu:
  Triaged

Bug description:
  This has been reliably reproduced on desktop and a phone running
  webbrowser-app 0.23+16.04.20160711-0ubuntu1 (and oxide
  1.15.8-0ubuntu0.16.04.1).

  Steps to reproduce:
  1) wipe your session data (make a backup first if you care) by removing 
~/.local/share/webbrowser-app/
  2) launch webbrowser-app
  3) browse to https://mail.google.com
  4) log in with an account that uses 2FA (I’m testing with a @canonical.com 
address)
  5) read your e-mails
  6) close the browser window
  7) launch webbrowser-app again

  Expected result: you’re back to your inbox, logged in and ready to
  work

  Actual result: google prompts you for your e-mail address. Once
  entered, the login happens automatically, there is no need to do the
  2FA dance again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1605218/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1590776] Re: hide selection handle when start typing

2016-07-21 Thread Chris Coulson
** Changed in: oxide/1.16
   Status: Fix Committed => Fix Released

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1590776

Title:
  hide selection handle when start typing

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Released
Status in Oxide 1.16 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  we are showing the selection handle (in addition to the cursor)
  whenever entering a text field that already has text in it. For
  example, if you are replying to a Gmail message, you have an annoying
  blue selection handle blinking where you are trying to type and you
  can't turn it off. Or on a form, focusing on a field to append text
  will also show the selection handle. Or a multi line text area, adding
  a new line and typing at the beginning.

  Tested Chrome on Android and it behaves differently, and think we should do 
similar:
   1. Show the selection handle initially, but have it disappear when you press 
any key (space, character, etc.)
   2. Tapping anywhere in the field will cause handle to be shown again
   3. Also, can we put the selection handle on the bottom of the cursor instead 
of the top? This is the behavior on Chrome for Android and the rest of our 
non-html platform in Ubuntu touch.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1604446] Re: getcurrentPosition in oxide does not cause a wake up of the GPS

2016-07-19 Thread Chris Coulson
I'm not sure what Oxide is meant to do here - we query the location
service via the qtpositioning API. There is no API for "waking up the
GPS" AFAICT.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1604446

Title:
  getcurrentPosition in oxide does not cause a wake up of the GPS

Status in Oxide:
  New
Status in location-service package in Ubuntu:
  New

Bug description:
  A browser based application that wants to use position can call 
getCurrentPosition
  
https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/getCurrentPosition
  or watchPosition
  https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/watchPosition

  maps (such as google maps) and navigation applications will typically use 
watchPosition which will cause location services to turn on the GPS chip and 
get a new location for the device.
  non-map applications that just want location aware context for things such as 
weather or local stores e.g. https://www.aldi.co.uk/store-finder do not 
subscribe to updates with watchPosition. They just call getCurrentPosition and 
expect a decent enough position to use.

  Ubuntu Touch returns the last known position from the cache when
  getCurrentPosition is called, and then fails to turn on the GPS. It
  should block until it has a decent position and return good data to
  the success callback. It certainly shouldn't return a bad position and
  then fail to make an effort to get a good position.

  The result of this bug is that you can go to a location aware web
  page, it will think you are somewhere else entirely, and refreshing
  will not improve the situation, you have to open a mapping application
  that uses watchPosition and wait for a fix to be obtained before going
  back to your location aware web page and refreshing to get good data.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

2016-07-13 Thread Chris Coulson
That won't work for child processes, where the environment variable
won't exist. Also, we should have something that works for current apps
on the phone (I assume there's a different environment variable for
that). If you're not using PathService, there would at least need to be
a command line option to make this work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Oxide:
  In Progress
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

2016-07-12 Thread Chris Coulson
I would modify base::GetShmemTempDir() to lookup a path via
base::PathService and then have Oxide override this. You'll need to add
a new key in base/base_paths_posix.h as well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Oxide:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1260103] Re: oxide should use an app-specific path for shared memory files

2016-07-12 Thread Chris Coulson
** Changed in: oxide
 Assignee: (unassigned) => Olivier Tilloy (osomon)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1260103

Title:
  oxide should use an app-specific path for shared memory files

Status in Oxide:
  Triaged
Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Confirmed

Bug description:
  Oxide creates shared memory files as /run/shm/.org.chromium.Chromium.*. This 
results in an AppArmor rule like the following:
owner /run/shm/.org.chromium.Chromium.* rwk, 

  But this rule is too lenient because a malicious app could enumerate
  these files and attack shared memory of other applications. Therefore,
  these paths need to be made application specific.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1593700] Re: Add spellchecking support

2016-07-12 Thread Chris Coulson
** Changed in: oxide
 Assignee: (unassigned) => Santosh (santoshbit2007)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1593700

Title:
  Add spellchecking support

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  We currently don't support spell-checking - it would be nice to have
  this.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1593700] Re: Add spellchecking support

2016-07-12 Thread Chris Coulson
This will also require webbrowser-app changes to support the spelling
suggestions in the context menu

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1593700

Title:
  Add spellchecking support

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  We currently don't support spell-checking - it would be nice to have
  this.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-11 Thread Chris Coulson
Whatever we do, we should stop using QQuickItem::hasActiveFocus() for
the reason outlined in comment 8. I don't understand the issue with
QQuickWindow::activeFocusItem() though - it looks like it's cleared to
nullptr before a focus out event and initialized to the new focus item
before a focus in event. It sounds like exactly what we want.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1601887] Re: camera is inverted and rotated on M10

2016-07-11 Thread Chris Coulson
** Package changed: webbrowser-app (Ubuntu) => oxide

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1601887

Title:
  camera is inverted and rotated on M10

Status in Oxide:
  Triaged

Bug description:
  M10 proposed 138

  Open a google hangout preview

  The image is flipped horizontally and rotated 90 deg right

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-08 Thread Chris Coulson
** Changed in: oxide
   Status: Confirmed => Triaged

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-08 Thread Chris Coulson
I think I'd prefer to just use QQuickWindow::activeFocusItem in
oxide::qquick::ContentsView::HasFocus(). From looking at the code, I
don't even think that QQuickItem::hasActiveFocus has the correct
semantics as it will indicate active focus for ancestors of the active
focus item which isn't really what we want (ie, if an application adds
another item as a child of the webview, we shouldn't think we're
actively focused if the child item is the active focus item).

We should really add some integration tests for these cases in
qt/tests/qmltests/web_platform

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-08 Thread Chris Coulson
(after looking at QQuickWindowPrivate::setFocusInScope)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-08 Thread Chris Coulson
I suspect that oxide::qquick::ContentsView::HasFocus also needs to
verify that item_ == item_->window()->activeFocusItem()
(http://doc.qt.io/qt-5/qquickwindow.html#activeFocusItem-prop). It looks
like this is cleared before dispatching QQuickItem::focusOutEvent(),
whereas QQuickItemPrivate::activeFocus isn't.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] Re: Webview appears to think it's in focus when typing in the addressbar

2016-07-07 Thread Chris Coulson
** Changed in: oxide
 Assignee: (unassigned) => Santosh (santoshbit2007)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1599771] [NEW] Webview appears to think it's in focus when typing in the addressbar

2016-07-07 Thread Chris Coulson
Public bug reported:

See the screenshot - when keyboard focus is on the addressbar, the
webview thinks it is still in focus (indicated by the presence of the
caret in the search field).

Not sure if this is Oxide or webbrowser-app

** Affects: oxide
 Importance: Undecided
 Status: New

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Ubuntu Start Page - Ubuntu Web Browser_007.png"
   
https://bugs.launchpad.net/bugs/1599771/+attachment/4696757/+files/Ubuntu%20Start%20Page%20-%20Ubuntu%20Web%20Browser_007.png

** Also affects: webbrowser-app (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1599771

Title:
  Webview appears to think it's in focus when typing in the addressbar

Status in Oxide:
  New
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  See the screenshot - when keyboard focus is on the addressbar, the
  webview thinks it is still in focus (indicated by the presence of the
  caret in the search field).

  Not sure if this is Oxide or webbrowser-app

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1591157] Re: webbrowser-app does not honour scale setting on HiDPI display

2016-06-13 Thread Chris Coulson
This isn't really a webbrowser-app or Oxide issue - this is a desktop
environment issue. If you run webbrowser-app with
QT_DEVICE_PIXEL_RATIO=2 then it works fine.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1591157

Title:
  webbrowser-app does not honour scale setting on HiDPI display

Status in Oxide:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  New
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  The attached screenshot should say it all, showing it in comparison
  with Firefox and, indeed, the rest of the Unity desktop.

  Basically, on a 4K display, with a native resolution of 3840x2160, but
  with the scaling factor set to 2, and Scale all window contents set
  on, *most* of the unity desktop these days respects this; it nearly
  all works.

  webbrowser-app seems to have no awareness of it at all, and thus its
  windows show up tiny.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: webbrowser-app 0.23+16.04.20160413-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 10 12:55:30 2016
  InstallationDate: Installed on 2016-03-30 (71 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  SourcePackage: webbrowser-app
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1570511] Re: Select All shows up when replying to gmail message

2016-06-03 Thread Chris Coulson
** Changed in: oxide/1.15
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1570511

Title:
  Select All shows up when replying to gmail message

Status in Canonical System Image:
  In Progress
Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  In Progress

Bug description:
  open gmail webapp (or in browser), try to reply to a mail
  scroll to the top of the message and tap to begin typing

  expected result:
  - can start typing, no menu

  actual result:
  - can start typing but Select All menu is incorrectly displayed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1586968] Re: Touch selection menu initially empty when focusing a text field

2016-06-03 Thread Chris Coulson
** Changed in: oxide/1.15
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1586968

Title:
  Touch selection menu initially empty when focusing a text field

Status in Oxide:
  Fix Released
Status in Oxide 1.15 series:
  Fix Released
Status in webbrowser-app package in Ubuntu:
  Invalid

Bug description:
  This appears to be 100% reproducible when the device has just been rebooted 
(not always reproducible otherwise).
  Steps to reproduce:
   1) browse to e.g. http://pastebin.ubuntu.com
   2) long press on one of the text fields ("Poster:" or "Content:")
   3) wait for the touch selection menu to appear next to the insertion handle 
(note that at the moment there is a bug in oxide which also triggers the page 
context menu, dismissing it will get you the touch selection menu)

  Expected result: assuming the clipboard is empty (device just
  rebooted), the "Select All" action is the only one visible in the
  touch selection menu.

  Current result: no action is visible, the menu is empty (see attached
  screenshot).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1544754] Re: implement the HTML5 pointer lock API

2016-06-02 Thread Chris Coulson
** Changed in: oxide
Milestone: branch-1.16 => branch-1.17

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1544754

Title:
  implement the HTML5 pointer lock API

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  The internet archive just released a collection of Win 3.1 games, using the 
DosBox emulator to run them on the website. On Chrome this triggers a 
"Allow/Deny archive.org to disable your mouse cursor" popup. Games are only 
playable using mouse or touch after accepting this.
  In the browser app/ Oxide there's no such popup and mouse input doesn't work.

  https://archive.org/details/win3_Mono3Dlx

  Another (more lightweight) example page: https://mdn.github.io
  /pointer-lock-demo/

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1570511] Re: Select All shows up when replying to gmail message

2016-05-26 Thread Chris Coulson
** Changed in: oxide/1.15
Milestone: 1.15.5 => 1.15.7

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1570511

Title:
  Select All shows up when replying to gmail message

Status in Canonical System Image:
  Confirmed
Status in Oxide:
  In Progress
Status in Oxide 1.15 series:
  Confirmed
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  open gmail webapp (or in browser), try to reply to a mail
  scroll to the top of the message and tap to begin typing

  expected result:
  - can start typing, no menu

  actual result:
  - can start typing but Select All menu is incorrectly displayed

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1585370] Re: pepper flash plugin disallowed from apparmor

2016-05-25 Thread Chris Coulson
The browser can also load the plugin from the partner repository (in
/usr/lib/adobe-flashplugin), although that's currently broken for a
different reason.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1585370

Title:
  pepper flash plugin disallowed from apparmor

Status in apparmor-easyprof-ubuntu package in Ubuntu:
  Incomplete
Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When launching webbrowser-app from unity8 under confinement, i get
  disallowed errors for /opt/google/chrome/PepperFlash/manifest.json and
  /opt/google/chrome/PepperFlash/libpepflashplayer.so

  When I add the following to the apparmor profile of webbrowser-app and
  to the oxide_helper subprocess, it works:

  /opt/google/** r,

  /opt/google/**/*.so mr,

  Don't know what's exactly needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1585370/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1569315] Re: Scrolling performance is dreadful after text has been selected

2016-05-20 Thread Chris Coulson
Fixed with
https://git.launchpad.net/oxide/commit/?id=0cf0e457da8772747e764c200428ae3fdbb659e1

** Changed in: oxide
   Status: In Progress => Fix Released

** No longer affects: webbrowser-app (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1569315

Title:
  Scrolling performance is dreadful after text has been selected

Status in Oxide:
  Fix Released

Bug description:
  I just noticed this - after selecting text with the mouse (I haven't
  tried this on the phone yet), scrolling becomes very laggy. It
  normally doesn't recover after cancelling the selection.

  chrome://tracing shows the UI thread is blocking for ~50ms periods in
  MessageLoop::RunTask, which isn't particularly helpful. The task being
  executed was posted from
  IPC::ChannelProxy::Context::OnMessageReceivedNoFilter, so it's
  basically a message handler somewhere that's responsible.

  Bug 1565280 would really help here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1569315] Re: Scrolling performance is dreadful after text has been selected

2016-05-20 Thread Chris Coulson
There's multiple issues here:

1) Oxide is reading data from the clipboard every time the selection
bounds change, in order to update the editing capability flags. This is
really expensive (more than 50ms!)

2) Selections aren't always completely cancelled in Blink, and we
continue to receive selection bounds updates with focus_rect ==
anchor_rect as content is scrolled.

3) Scrolling over active Flash content causes us to begin to receive
selection bounds updates (again, with focus_rect == anchor_rect) as
content is scrolled.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1569315

Title:
  Scrolling performance is dreadful after text has been selected

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I just noticed this - after selecting text with the mouse (I haven't
  tried this on the phone yet), scrolling becomes very laggy. It
  normally doesn't recover after cancelling the selection.

  chrome://tracing shows the UI thread is blocking for ~50ms periods in
  MessageLoop::RunTask, which isn't particularly helpful. The task being
  executed was posted from
  IPC::ChannelProxy::Context::OnMessageReceivedNoFilter, so it's
  basically a message handler somewhere that's responsible.

  Bug 1565280 would really help here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1569315] Re: Scrolling performance is dreadful after text has been selected

2016-05-20 Thread Chris Coulson
** Changed in: oxide
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1569315

Title:
  Scrolling performance is dreadful after text has been selected

Status in Oxide:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I just noticed this - after selecting text with the mouse (I haven't
  tried this on the phone yet), scrolling becomes very laggy. It
  normally doesn't recover after cancelling the selection.

  chrome://tracing shows the UI thread is blocking for ~50ms periods in
  MessageLoop::RunTask, which isn't particularly helpful. The task being
  executed was posted from
  IPC::ChannelProxy::Context::OnMessageReceivedNoFilter, so it's
  basically a message handler somewhere that's responsible.

  Bug 1565280 would really help here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1569315] Re: Scrolling performance is dreadful after text has been selected

2016-05-20 Thread Chris Coulson
** Changed in: oxide
 Assignee: (unassigned) => Chris Coulson (chrisccoulson)

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1569315

Title:
  Scrolling performance is dreadful after text has been selected

Status in Oxide:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  I just noticed this - after selecting text with the mouse (I haven't
  tried this on the phone yet), scrolling becomes very laggy. It
  normally doesn't recover after cancelling the selection.

  chrome://tracing shows the UI thread is blocking for ~50ms periods in
  MessageLoop::RunTask, which isn't particularly helpful. The task being
  executed was posted from
  IPC::ChannelProxy::Context::OnMessageReceivedNoFilter, so it's
  basically a message handler somewhere that's responsible.

  Bug 1565280 would really help here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1566373] Re: GMail webapp keyboard hide and seek

2016-05-18 Thread Chris Coulson
And the same behaviour happens with GMail in Chrome/Desktop

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1566373

Title:
  GMail webapp keyboard hide and seek

Status in Canonical System Image:
  Confirmed
Status in webapps-sprint:
  Triaged
Status in webbrowser-app package in Ubuntu:
  Confirmed

Bug description:
  This is possibly a keyboard problem instead, please feel free to
  reassign as necessary.  Testing with Frieza r75.

  TEST CASE
  GMail account connected, GMail app open, landscape mode
  1.  Compose e-mail, compose screen appears
  2.  Tap in address header
  EXPECTED
  Keyboard appears
  ACTUAL
  Keyboard appears, keyboard immediately hides

  Possibly this is a layout issue; also the delay in opening the
  keyboard (blank white space left open during delay) may explain?
  Here's a link to a video (note upside-down :/ ):
  http://people.canonical.com/~alesage/video20160404_164751052.mp4 .

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   >