Hello Will, 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: Confirmed => Fix Committed ** Tags added: verification-needed -- 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/1632620 Title: No audio from webbrowser-app in 16.10 Status in Oxide: Invalid Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Fix Released Status in apparmor-easyprof-ubuntu source package in Yakkety: Confirmed Status in webbrowser-app source package in Yakkety: Fix Committed Bug description: [Test case] Load the browser on 16.10 in either a U8 or U7 session. Browse to YouTube. Play a video. Notice there is no sound. Nor does the browser show in the sound menu/panel. TLDR: this is an apparmor confinement issue: on yakkety pulse audio needs write access to /{run,dev}/shm/pulse-shm*, which is being denied by the audio and microphone policy groups. The fix consists in punching an additional hole in the generated apparmor profile for webbrowser-app. [Regression potential] Low. As the fix consists in weakening the apparmor profile for webbrowser-app, the only concerns should be security-related. The change was ack’d by Jamie Strandboge (see comment #11 in this bug report). It is not anticipated that this change would make the browser’s functionality regress. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1632620/+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