FTBFS on yakkety arm64: Invalid chromium version: ''

Bug #1633439 reported by Olivier Tilloy on 2016-10-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webbrowser-app (Ubuntu)
Olivier Tilloy

Bug Description

This error appears to be 100% reproducible on arm64 builds targetting yakkety (see e.g. https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2076/+build/11022370):

dh build-arch --parallel --with translations
   dh_testdir -a -O--parallel
   dh_update_autotools_config -a -O--parallel
   dh_auto_configure -a -O--parallel
-- The C compiler identification is GNU 6.2.0
-- The CXX compiler identification is GNU 6.2.0
-- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc
-- Check for working C compiler: /usr/bin/aarch64-linux-gnu-gcc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++
-- Check for working CXX compiler: /usr/bin/aarch64-linux-gnu-g++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could NOT find gcovr (missing: GCOVR_EXECUTABLE)
CMake Error at src/Ubuntu/CMakeLists.txt:31 (message):
  Invalid chromium version: ''

It is fixed in webbrowser-app in zesty (original bug report: bug #1599695), the fix needs to be backported to yakkety.

Running qmlscene inside xvfb at build time to determine the chromium version oxide is built upon proved to be unreliable, the patch attached dynamically replaces the chromium version at runtime instead.

[Regression potential]
Need to verify that the chromium version advertised in user agent overrides is still correct. This can be done by browsing to a site for which a UA override is defined (e.g. https://www.youtube.com/ on desktop) and observing the User-Agent HTTP header of the request (using e.g. wireshark).

Related branches

Martin Pitt (pitti) wrote :

There is no corresponding zesty upload. Please do that first.

Olivier Tilloy (osomon) wrote :

This is now fixed in zesty, with version 0.23+17.04.20161024.1-0ubuntu1.

Changed in webbrowser-app (Ubuntu):
status: In Progress → Fix Released
Olivier Tilloy (osomon) on 2016-10-27
description: updated

Hello Olivier, or anyone else affected,

Accepted webbrowser-app into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/webbrowser-app/0.23+16.10.20161018-0ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in webbrowser-app (Ubuntu Yakkety):
status: New → Fix Committed
tags: added: verification-needed
Jeremy Bicha (jbicha) wrote :

The new version did build on arm64. I did not test the user agent.


tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package webbrowser-app - 0.23+16.10.20161018-0ubuntu1

webbrowser-app (0.23+16.10.20161018-0ubuntu1) yakkety; urgency=medium

  * Fix FTBFS on yakkety arm64 and work around a limitation in the sound
    and microphone policy groups. (LP: #1632620, #1633439)

 -- Olivier Tilloy <email address hidden> Tue, 18 Oct 2016 07:07:56 +0000

Changed in webbrowser-app (Ubuntu Yakkety):
status: Fix Committed → Fix Released

The verification of the Stable Release Update for webbrowser-app has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers