No, this was just an observation of a webbrowser-app rebuild. But at the time of when I reported this bug, there already was a new oxide-qt built in yakkety which was built against the new glibc.
-- 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/1613258 Title: signal 4 ILL_ILLOPN in webbrowser-app tests (glibc upgrade?) Status in glibc package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: This is happening with a no-change rebuild of webbrowser-app, with the most likely candidate for the problem trigger being the new glibc 2.24 in yakkety-proposed. --- https://launchpadlibrarian.net/279047362/buildlog_ubuntu-yakkety-i386.webbrowser-app_0.23+16.10.20160803.1-0ubuntu2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1613258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
