ubuntu-phone team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

On Thu, Jul 10, 2014 at 9:55 AM, David Planella <david.planella@xxxxxxxxxx>
wrote:

> On Wed, Jul 9, 2014 at 8:40 AM, Olivier Tilloy <
> olivier.tilloy@xxxxxxxxxxxxx> wrote:
>
>>
>>
>>
>> On Wed, Jul 9, 2014 at 4:27 AM, Robert Schroll <rschroll@xxxxxxxxx>
>> wrote:
>>
>>> Hi all,
>>>
>>> I'm running r113 on an i386 emulator.  It seems to be working pretty
>>> well, but all QtWebKit WebViews appear solid black.  This means that HTML5
>>> apps are broken, as are the parts of QML apps that rely on these WebViews.
>>>  Oxide WebViews, however, are displayed just fine.  I assume this is a
>>> problem with the emulator and/or my system.  Perhaps it's an OpenGL issue?
>>>
>>
>> Likely.
>>
>>
>> Has anyone else seen something similar?  Any suggestions of solutions to
>>> try?
>>>
>>
>> This was reported on Monday by dpm (not sure whether there is a bug
>> report to track the issue already though, feel free to file one at
>> https://bugs.launchpad.net/ubuntu-html5-theme/+filebug). Unfortunately
>> the HTML5 container on Ubuntu Touch hasn’t migrated to oxide yet, but this
>> is being worked on.
>>
>> QtWebKit is not something we can afford to support along with Oxide, so
>> let’s hope we can update the HTML5 container very soon.
>>
>
> Hi Olivier,
>
> That was the reason why I did not report the bug, as I thought it'd make
> more sense to focus on getting everything migrated to Oxide rather than
> trying to fix something that's going to become obsolete very soon.
>
> For more context, I could reproduce this first when running Reminders in
> the emulator (the Evernote notes are loaded in a WebKit-based web view),
> and then I could see it too running Eventunity from the store.
>
> We've now got a Reminders branch that's migrated to Oxide [1], but now
> running it on the emulator I get this error when trying to load the content
> of a note:
>
> LaunchProcess: failed to execvp:
>
> /usr/lib/i386-linux-gnu/oxide-qt/chrome-sandbox
>
> If it makes a difference, I tested this on an image (118) that's not the
> latest. Any ideas?
>

Yes, that one’s easy to fix: you need to add the "webview" policy group to
the apparmor manifest.