[Qtwebengine] gl_context_glx.cc(69) Failed to create GL context with glXCreateContextAttribsARB

[Notorious]

Hello,

Attached output of chrome://gpu from latest stable chromium.
Apparently this one (35.0.1916.153) is using hardware rendering with no 
problems..

Kind Regards

On 06/17/2014 03:57 PM, Notorious wrote:
> Hi,
>
> I re-fetched & recompiled the whole repository to no avail.
> So I upgraded the kernel to 3.15, same result.
>
> Any ideas?
>
> Kind Regards
>
> On 06/17/2014 02:17 PM, Jocelyn Turcotte wrote:
>> Hello,
>>
>> the actual fix is in the src/3rdparty submodule
>> <https://codereview.qt-project.org/87518>. The patch I linked was
>> updating the ref of src/3rdparty to include that change.
>>
>> Could you make sure that you also ran git submodule update?
>>
>> If it still doesn't work, do you know if you got that problem only with
>> the kernel update, or did you have the issue before as well?
>>
>> Cheers,
>> Jocelyn
>>
>>
>> On Tue, Jun 17, 2014 at 02:01:13PM +0200, Notorious wrote:
>>> Hi,
>>>
>>> I committed this patch and recompiled, no changes...
>>>
>>> Kind Regards
>>>
>>> On 06/16/2014 07:09 PM, Jocelyn Turcotte wrote:
>>>> Hello,
>>>>
>>>> The issue that you're facing should be fixed by the change
>>>> <https://codereview.qt-project.org/87527>, currently integrating.
>>>>
>>>> we don't have any plan yet to fallback to software rendering since Qt itself
>>>> still requires GL on all graphic hardware. When Qt has a concrete plan on
>>>> how to handle faulty drivers we should also add support to QtWebEngine.
>>>>
>>>> Cheers,
>>>> Jocelyn
>>>>
>>>>
>>>> On Mon, Jun 16, 2014 at 06:49:01PM +0200, Notorious wrote:
>>>>> Hi all,
>>>>>
>>>>> When using qWebEngine on a laptop with i915 graphics driver (Intel 3rd
>>>>> gen GPU) on kernel 3.14-1 nothing gets rendered and following messages
>>>>> occur:
>>>>> gl_context_glx.cc(69) Failed to create GL context with
>>>>> glXCreateContextAttribsARB
>>>>> command_buffer_proxy_impl.cc(165) Failed to initialize command buffer
>>>>> service.
>>>>>
>>>>> I googled around and apparently this patch
>>>>> (https://codereview.chromium.org/93593002/) was created to automatically
>>>>> fall back on sofware rendering if this situation does occur.
>>>>> As far as I can see these changes are present in the chromium fork on
>>>>> qt-labs, but it obviously doesn't fall back on software rendering.
>>>>>
>>>>> Is there any way to force software rendering to work around this issue?
>>>>> As with "chromium --disable-gpu"?
>>>>>
>>>>> Kind Regards
>>>>> _______________________________________________
>>>>> QtWebEngine mailing list
>>>>> QtWebEngine at qt-project.org
>>>>> http://lists.qt-project.org/mailman/listinfo/qtwebengine
>>> _______________________________________________
>>> QtWebEngine mailing list
>>> QtWebEngine at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/qtwebengine
> _______________________________________________
> QtWebEngine mailing list
> QtWebEngine at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qtwebengine

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20140617/f0e79404/attachment.html>