D’oh. The issue is with apparmor confinement. Disabling it for the
browser "fixes" the issue:
sudo apparmor_parser -R /etc/apparmor.d/usr.bin.webbrowser-app
** Changed in: webbrowser-app (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Apps bug tracking, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1575556
Title:
webbrowser-app fails to start when installed system-wide and run
against a custom oxide build
Status in webbrowser-app package in Ubuntu:
Invalid
Bug description:
Oxide has a "test-package" make target that generates a tarball that
can be unpacked anywhere on the filesystem and has a script that
allows running applications against that build of oxide.
This works well when running a locally built version of webbrowser-
app, but it fails with the following error with the system-wide app:
file:///usr/share/webbrowser-app/webbrowser/webbrowser-app.qml:41 Type
Browser unavailable
file:///usr/share/webbrowser-app/webbrowser/Browser.qml:22 module
"com.canonical.Oxide" definition
"/home/osomon/dev/phablet/oxide/trunk/objdir-x64/out/imports/com/canonical/Oxide/qmldir"
not readable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1575556/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-apps-bugs
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntu-apps-bugs
More help : https://help.launchpad.net/ListHelp
