From pvarga at inf.u-szeged.hu  Tue Feb  3 11:26:45 2015
From: pvarga at inf.u-szeged.hu (Peter Varga)
Date: Tue, 03 Feb 2015 11:26:45 +0100
Subject: [Qtwebengine] webengine crash
In-Reply-To: <54CBA12C.8010206@gmail.com>
References: <54CBA12C.8010206@gmail.com>
Message-ID: <54D0A265.90209@inf.u-szeged.hu>

Hi Tom,

I tried to reproduce the reported problem but I couldn't. I compiled the
32bit Qt5 as I usually do:
made the build in an already set up 32bit chroot environment. Therefore
I suppose that the problem is
related to the cross-compilation. It might be possible some platform
specific configuration are passed
to the V8 compilation in a wrong way.

Could you elaborate a bit how you cross-compiled the Qt5? First of all I
need answers for the following
questions:
- Just to make things clear: your target is x86 32bit and Linux, isn't it?
- I generated a 32bit cross-toolchain with buildroot. I used the default
configuration. Did you change
anything compared to the default settings in buildroot? For example, do
you use uclibc or glibc?
- Which configuration options was passed to the Qt5's configure script?
I don't know how to set the
cross-compile toolchain. The easiest way is seemed to me to use the
-device-option CROSS_COMPILE=...
option but it is useless without specifying -device option.

Regards,
Peter

On 01/30/2015 04:20 PM, Tom Deblauwe wrote:
> Hello,
> 
> I am trying out QtWebEngine 5.4.0 and I'm having a crash when enabling 
> javascript. I am crosscompiling for 32-bit on a 64-bit linux using 
> buildroot. I get it to compile and run, but only when I disable 
> javascript. Upon further investigation, I found it has something to do 
> with some types of javascript. I tested some things and it seems I get 
> the crash with "jquery" version 1.11.0, like for example that is used on 
> "xkcd.org". When I use the latest "jquery" I don't get the crash, e.g. 
> jquery 2.1.3. Anyway, in all cases, the last part of the stack trace is 
> almost the same.
> 
> It always ends with the "WriteToFlat" function.
> 
> I have set a breakpoint and the function works, it is not crashing on 
> the first try, but after a while it seems.
> Then I also checked that it was not some sort of javascript out of 
> memory thing, so I wrote a little javascript that just creates a huge 
> array, and that fails gratiously, it doesn't crash. So it seems it is 
> really some kind of internal issue. I suspect it has something to do 
> with regular expressions, or maybe the "String::Flatten" function is 
> called often in regexp's. Anyways, on this line:
> 
> src/3rdparty/chromium/v8/src/jsregexp.cc:169
> 
> There is a "pattern = String::Flatten(pattern);" call.
> 
> So any clues in what direction I would have to search to find the problem?
> 
> The problem is not reproducable when I use the regular desktop builds 
> downloadable using the qt installer.
> 
> On different sites I have differen backtraces, but all end with a call 
> to "WriteToFlat<unsigned char>".
> 
> And when I disable javascript, every site renders okay, so there is not 
> a problem with the rendering itself, everything is seen as intended.
> 
> Any help would be greatly appreciated!
> 
> Best regards,
> Tom Deblauwe
> 
> 
> gdb --args ./browser --log-level=0 --single-process
> (gdb) bt
> #0  v8::internal::String::WriteToFlat<unsigned char> (src=0xdd094881, 
> src at entry=0xdd0949a9,
>      sink=sink at entry=0xdd094e8c 
> "\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336)*)|.*)\\)|)\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336"..., 
> f=119, f at entry=0, t=171) at 
> ../../../src/3rdparty/chromium/v8/src/objects.cc:8823
> #1  0xeeceae64 in v8::internal::String::WriteToFlat<unsigned char> 
> (src=0xdd0949ed,
>      sink=0xdd094e15 
> "\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336)*)|.*)\\)|)\336\357\276\255\336\357\276\255\336\357\276\255\336\357\276\255\336\357"..., 
> 
>      f=f at entry=0, t=171, t at entry=263) at 
> ../../../src/3rdparty/chromium/v8/src/objects.cc:8864
> #2  0xeecec384 in v8::internal::String::SlowFlatten 
> (cons=cons at entry=..., pretenure=pretenure at entry=v8::internal::NOT_TENURED)
>      at ../../../src/3rdparty/chromium/v8/src/objects.cc:1044
> #3  0xee9f800a in v8::internal::String::Flatten (string=..., 
> pretenure=v8::internal::NOT_TENURED)
>      at ../../../src/3rdparty/chromium/v8/src/objects-inl.h:3180
> #4  0xeec50fd8 in v8::internal::RegExpImpl::Compile (re=re at entry=..., 
> pattern=pattern at entry=..., flag_str=...)
>      at ../../../src/3rdparty/chromium/v8/src/jsregexp.cc:169
> #5  0xeed7e513 in __RT_impl_Runtime_RegExpCompile (isolate=0xe79450d0, 
> args=...)
>      at ../../../src/3rdparty/chromium/v8/src/runtime.cc:2124
> #6  v8::internal::Runtime_RegExpCompile (args_length=3, 
> args_object=0xe16f2ee0, isolate=0xe79450d0)
>      at ../../../src/3rdparty/chromium/v8/src/runtime.cc:2117
> #7  0x20e0a076 in ?? ()
> #8  0x20e594f2 in ?? ()
> #9  0x20e3b0c4 in ?? ()
> #10 0x20e1e85b in ?? ()
> #11 0x20e1eb3b in ?? ()
> #12 0x3750ad73 in ?? ()
> #13 0x3750fe29 in ?? ()
> #14 0x20e1e85b in ?? ()
> #15 0x20e80a11 in ?? ()
> #16 0x20e80b6b in ?? ()
> #17 0x20e1edf5 in ?? ()
> #18 0x20e1e0ea in ?? ()
> #19 0xeeae7336 in v8::internal::Invoke 
> (is_construct=is_construct at entry=false, function=function at entry=..., 
> receiver=...,
>      receiver at entry=..., argc=argc at entry=0, args=args at entry=0x0) at 
> ../../../src/3rdparty/chromium/v8/src/execution.cc:94
> #20 0xeeae9580 in v8::internal::Execution::Call 
> (isolate=isolate at entry=0xe79450d0, callable=..., callable at entry=..., 
> receiver=...,
>      argc=argc at entry=0, argv=argv at entry=0x0, 
> convert_receiver=convert_receiver at entry=false)
>      at ../../../src/3rdparty/chromium/v8/src/execution.cc:149
> #21 0xeea1ceba in v8::Script::Run (this=0xe796bd48) at 
> ../../../src/3rdparty/chromium/v8/src/api.cc:1637
> #22 0xf15b8aa8 in WebCore::V8ScriptRunner::runCompiledScript 
> (script=..., context=0x5f404078, isolate=0xe79450d0)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/bindings/v8/V8ScriptRunner.cpp:105
> #23 0xf1562e44 in WebCore::ScriptController::executeScriptAndReturnValue 
> (this=0xe7970d88, context=..., source=...,
>      corsStatus=WebCore::NotSharableCrossOrigin)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/bindings/v8/ScriptController.cpp:187
> #24 0xf1564bc3 in WebCore::ScriptController::evaluateScriptInMainWorld 
> (this=0xe7970d88, sourceCode=...,
>      corsStatus=WebCore::NotSharableCrossOrigin, 
> policy=WebCore::ScriptController::DoNotExecuteScriptWhenScriptsDisabled)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/bindings/v8/ScriptController.cpp:582
> #25 0xf15649ad in WebCore::ScriptController::executeScriptInMainWorld 
> (this=0xe7970d88, sourceCode=...,
>      corsStatus=WebCore::NotSharableCrossOrigin)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/bindings/v8/ScriptController.cpp:551
> #26 0xef763ff0 in WebCore::ScriptLoader::executeScript (this=0xe7972870, 
> sourceCode=...)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/core/dom/ScriptLoader.cpp:335
> #27 0xf1d0bf9f in 
> WebCore::HTMLScriptRunner::executePendingScriptAndDispatchEvent 
> (this=0x466e47f0, pendingScript=...,
> pendingScriptType=WebCore::HTMLScriptRunner::PendingScriptBlockingParser)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/core/html/parser/HTMLScriptRunner.cpp:165
> #28 0xf1d0bda0 in 
> WebCore::HTMLScriptRunner::executeParsingBlockingScript (this=0x466e47f0)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/core/html/parser/HTMLScriptRunner.cpp:134
> #29 0xf1d0c395 in 
> WebCore::HTMLScriptRunner::executeParsingBlockingScripts (this=0x466e47f0)
>      at 
> ../../../src/3rdparty/chromium/third_party/WebKit/Source/core/html/parser/HTMLScriptRunner.cpp:226
> #30 0xf1d0c556 in 
> WebCore::HTMLScriptRunner::executeScriptsWaitingForLoad 
> (this=0x466e47f0, resource=0x467c03d0)
> 
> 
> 
> _______________________________________________
> QtWebEngine mailing list
> QtWebEngine at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qtwebengine
> 



From deblauwetom at gmail.com  Tue Feb  3 17:19:46 2015
From: deblauwetom at gmail.com (Tom Deblauwe)
Date: Tue, 03 Feb 2015 17:19:46 +0100
Subject: [Qtwebengine] webengine crash
In-Reply-To: <54D0A265.90209@inf.u-szeged.hu>
References: <54CBA12C.8010206@gmail.com> <54D0A265.90209@inf.u-szeged.hu>
Message-ID: <54D0F522.10300@gmail.com>

On 02/03/2015 11:26 AM, Peter Varga wrote:
> Hi Tom,
>
> I tried to reproduce the reported problem but I couldn't. I compiled the
> 32bit Qt5 as I usually do:

Thanks a lot for your investigation time.

> made the build in an already set up 32bit chroot environment. Therefore
> I suppose that the problem is
> related to the cross-compilation. It might be possible some platform
> specific configuration are passed
> to the V8 compilation in a wrong way.
>
> Could you elaborate a bit how you cross-compiled the Qt5? First of all I
> need answers for the following
> questions:
> - Just to make things clear: your target is x86 32bit and Linux, isn't it?

Yes, correct

> - I generated a 32bit cross-toolchain with buildroot. I used the default
> configuration. Did you change
> anything compared to the default settings in buildroot? For example, do
> you use uclibc or glibc?

Hello I used gcc 4.9.2 with glibc with a buildroot version from the 
master branch on 4th november 2014. (I forgot to note the actual commit)

> - Which configuration options was passed to the Qt5's configure script?
> I don't know how to set the
> cross-compile toolchain. The easiest way is seemed to me to use the
> -device-option CROSS_COMPILE=...
> option but it is useless without specifying -device option.
>

In the buildroot version, you can have QT5 5.3, but it works if you just 
change the version number in package/qt5/qt5.mk to 5.4.0

Then I just started from qt5webkit.mk and made qt5webengine.mk like I 
have copy-pasted below.

You don't need to worry about the cross compilation of qt5, buildroot 
creates a cross compiled qmake in the output directory.

Then for webengine source itself, I needed to change some things.

1) In tools/qmake/mkspecs/features/functions.prf I needed to add 
"linux-buildroot-g++: return (true)" so that the "isPlatformSupported" 
function accepts buildroot.

2) Then webengine wants to build the "embedded_linux.pri" configuration. 
There I changed the following because I wanted pulseaudio and x11:

use_ozone=0
use_system_icu=0   <-- the icu in buildroot is 51 and the bundled in 
webengine is 46 and webengine uses those 46 headers because they are in 
third_party
use_x11=1
use_glib=1
use_dbus=1
use_pulseaudio=1
desktop_linux=1    <-- because i had some sort of compile error, don't 
remember which one

3) In src/core/config/embedded_linux.gypi I added this, hardcoded, not 
good but it is ok for me:

     'defines': [
       '_LARGEFILE_SOURCE',
       '_LARGEFILE64_SOURCE',
       '_FILE_OFFSET_BITS=64',
     ],
     'cflags': [
        '-pipe',
        '-O2',
        '-g2',
     ],


The easiest is to do:
$ make qt5webengine-patch

<edit the things I mention>

$ make qt5webengine


I hope this somewhat helps you out.


Right now I am trying out some things, but it all takes a long time to 
compile of course :)
One idea I am now trying out is that maybe I should add something like 
this to the "tools/buildscripts/gyp_qtwebengine" python script:

os.environ['CXX'] = 
"/home/tdeblauwe/git/thinclient-os/output/host/usr/bin/ccache 
/home/tdeblauwe/git/thinclient-os/output/host/usr/bin/i686-buildroot-linux-gnu-g++"
os.environ['CC'] = 
"/home/tdeblauwe/git/thinclient-os/output/host/usr/bin/ccache 
/home/tdeblauwe/git/thinclient-os/output/host/usr/bin/i686-buildroot-linux-gnu-gcc"
args.extend(['-D', 'clang=0'])
args.extend(['-D', 'host_clang=0'])


But I'm still compiling it, so I'll let you know any outcome.

Thanks,
Best regards,
Tom,


################################################################################
#
# qt5webengine
#
################################################################################

QT5WEBENGINE_VERSION = $(QT5_VERSION)
QT5WEBENGINE_SITE = $(QT5_SITE)
#QT5WEBENGINE_SOURCE = 
qtwebengine-opensource-src-$(QT5WEBENGINE_VERSION).tar.xz
QT5WEBENGINE_SOURCE = qt5-webengine.tar.gz
QT5WEBENGINE_DEPENDENCIES = qt5base sqlite host-ruby host-gperf 
host-bison host-flex xlib_libXi xlib_libXt xlib_libXtst xapp_xrandr 
xlib_libXcursor xlib_libXcomposite pciutils
QT5WEBENGINE_INSTALL_STAGING = YES

ifeq ($(BR2_PACKAGE_QT5BASE_LICENSE_APPROVED),y)
QT5WEBENGINE_LICENSE = LGPLv2+, MIT
else
QT5WEBENGINE_LICENSE = LGPLv2+, MIT, Commercial license
QT5WEBENGINE_REDISTRIBUTE = NO
endif
QT5WEBENGINE_LICENSE_FILES = Source/WebCore/LICENSE-LGPL-2 
Source/WebCore/LICENSE-LGPL-2.1 Source/WebEngine/LICENSE

ifeq ($(BR2_PACKAGE_QT5BASE_XCB),y)
QT5WEBENGINE_DEPENDENCIES += xlib_libXext xlib_libXrender
endif

ifeq ($(BR2_PACKAGE_QT5DECLARATIVE),y)
QT5WEBENGINE_DEPENDENCIES += qt5declarative
endif

define QT5WEBENGINE_CONFIGURE_CMDS
	(cd $(@D); $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/qmake)
endef

define QT5WEBENGINE_BUILD_CMDS
	$(TARGET_MAKE_ENV) $(MAKE) -C $(@D)
endef

define QT5WEBENGINE_INSTALL_STAGING_CMDS
	$(TARGET_MAKE_ENV) $(MAKE) -C $(@D) install
	$(QT5_LA_PRL_FILES_FIXUP)
endef

ifeq ($(BR2_PACKAGE_QT5DECLARATIVE_QUICK),y)
define QT5WEBENGINE_INSTALL_TARGET_QMLS
	cp -dpfr $(STAGING_DIR)/usr/qml/QtWebEngine $(TARGET_DIR)/usr/qml/
endef
endif

define QT5WEBENGINE_INSTALL_TARGET_CMDS
	cp -dpf $(STAGING_DIR)/usr/lib/libQt5WebEngine*.so.* $(TARGET_DIR)/usr/lib
	cp -dpf $(STAGING_DIR)/usr/libexec/QtWebEngineProcess 
$(TARGET_DIR)/usr/libexec
     mkdir -p $(TARGET_DIR)/usr/translations/qtwebengine_locales
     cp -dpf 
$(STAGING_DIR)/usr/translations/qtwebengine_locales/en-US.pak 
$(TARGET_DIR)/usr/translations/qtwebengine_locales
     cp -dpf $(STAGING_DIR)/usr/qtwebengine_resources.pak $(TARGET_DIR)/usr
	$(QT5WEBENGINE_INSTALL_TARGET_QMLS)
endef

$(eval $(generic-package))



From andras.becsi at theqtcompany.com  Tue Feb  3 17:37:20 2015
From: andras.becsi at theqtcompany.com (Andras Becsi)
Date: Tue, 3 Feb 2015 17:37:20 +0100
Subject: [Qtwebengine] webengine crash
In-Reply-To: <54D0F522.10300@gmail.com>
References: <54CBA12C.8010206@gmail.com> <54D0A265.90209@inf.u-szeged.hu>
	<54D0F522.10300@gmail.com>
Message-ID: <54D0F940.30307@theqtcompany.com>

Hi Tom,

As far as I know chromium does not officially support cross-compiling 
32bits on 64 bits.

Your problem is most probably due to miscompilation, because to the 
build system is not picking up the proper configuration.

I suggest you try compiling in a 32bit chroot instead, since 
qtwebengine's cross-compilation config is set up for embedded builds.

Some additional notes inline.

/Andras

On 02/03/2015 05:19 PM, Tom Deblauwe wrote:
> On 02/03/2015 11:26 AM, Peter Varga wrote:
>> Hi Tom,
>>
>> I tried to reproduce the reported problem but I couldn't. I compiled the
>> 32bit Qt5 as I usually do:
>
> Thanks a lot for your investigation time.
>
>> made the build in an already set up 32bit chroot environment. Therefore
>> I suppose that the problem is
>> related to the cross-compilation. It might be possible some platform
>> specific configuration are passed
>> to the V8 compilation in a wrong way.
>>
>> Could you elaborate a bit how you cross-compiled the Qt5? First of all I
>> need answers for the following
>> questions:
>> - Just to make things clear: your target is x86 32bit and Linux, isn't it?
>
> Yes, correct
>
>> - I generated a 32bit cross-toolchain with buildroot. I used the default
>> configuration. Did you change
>> anything compared to the default settings in buildroot? For example, do
>> you use uclibc or glibc?
>
> Hello I used gcc 4.9.2 with glibc with a buildroot version from the
> master branch on 4th november 2014. (I forgot to note the actual commit)
>
>> - Which configuration options was passed to the Qt5's configure script?
>> I don't know how to set the
>> cross-compile toolchain. The easiest way is seemed to me to use the
>> -device-option CROSS_COMPILE=...
>> option but it is useless without specifying -device option.
>>
>
> In the buildroot version, you can have QT5 5.3, but it works if you just
> change the version number in package/qt5/qt5.mk to 5.4.0
>
> Then I just started from qt5webkit.mk and made qt5webengine.mk like I
> have copy-pasted below.
>
> You don't need to worry about the cross compilation of qt5, buildroot
> creates a cross compiled qmake in the output directory.
>
> Then for webengine source itself, I needed to change some things.
>
> 1) In tools/qmake/mkspecs/features/functions.prf I needed to add
> "linux-buildroot-g++: return (true)" so that the "isPlatformSupported"
> function accepts buildroot.
>
> 2) Then webengine wants to build the "embedded_linux.pri" configuration.
> There I changed the following because I wanted pulseaudio and x11:

This will most probably already produce a problematic build.
Your build should use desktop_linux.pri, cross-compilation is set up for 
embedded.

>
> use_ozone=0
> use_system_icu=0   <-- the icu in buildroot is 51 and the bundled in
> webengine is 46 and webengine uses those 46 headers because they are in
> third_party
> use_x11=1
> use_glib=1
> use_dbus=1
> use_pulseaudio=1
> desktop_linux=1    <-- because i had some sort of compile error, don't
> remember which one
>
> 3) In src/core/config/embedded_linux.gypi I added this, hardcoded, not
> good but it is ok for me:
>
>       'defines': [
>         '_LARGEFILE_SOURCE',
>         '_LARGEFILE64_SOURCE',
>         '_FILE_OFFSET_BITS=64',
>       ],
>       'cflags': [
>          '-pipe',
>          '-O2',
>          '-g2',
>       ],
>
AFAICT this on it's own can already cause v8 JIT to miscompile, so your 
crash is definetely caused by your configuration.


>
> The easiest is to do:
> $ make qt5webengine-patch
>
> <edit the things I mention>
>
> $ make qt5webengine
>
>
> I hope this somewhat helps you out.
>
>
> Right now I am trying out some things, but it all takes a long time to
> compile of course :)
> One idea I am now trying out is that maybe I should add something like
> this to the "tools/buildscripts/gyp_qtwebengine" python script:
>
> os.environ['CXX'] =
> "/home/tdeblauwe/git/thinclient-os/output/host/usr/bin/ccache
> /home/tdeblauwe/git/thinclient-os/output/host/usr/bin/i686-buildroot-linux-gnu-g++"
> os.environ['CC'] =
> "/home/tdeblauwe/git/thinclient-os/output/host/usr/bin/ccache
> /home/tdeblauwe/git/thinclient-os/output/host/usr/bin/i686-buildroot-linux-gnu-gcc"
> args.extend(['-D', 'clang=0'])
> args.extend(['-D', 'host_clang=0'])
>

This will most certainly not fix your v8 crash.


>
> But I'm still compiling it, so I'll let you know any outcome.
>
> Thanks,
> Best regards,
> Tom,
>
>
> ################################################################################
> #
> # qt5webengine
> #
> ################################################################################
>
> QT5WEBENGINE_VERSION = $(QT5_VERSION)
> QT5WEBENGINE_SITE = $(QT5_SITE)
> #QT5WEBENGINE_SOURCE =
> qtwebengine-opensource-src-$(QT5WEBENGINE_VERSION).tar.xz
> QT5WEBENGINE_SOURCE = qt5-webengine.tar.gz
> QT5WEBENGINE_DEPENDENCIES = qt5base sqlite host-ruby host-gperf
> host-bison host-flex xlib_libXi xlib_libXt xlib_libXtst xapp_xrandr
> xlib_libXcursor xlib_libXcomposite pciutils
> QT5WEBENGINE_INSTALL_STAGING = YES
>
> ifeq ($(BR2_PACKAGE_QT5BASE_LICENSE_APPROVED),y)
> QT5WEBENGINE_LICENSE = LGPLv2+, MIT
> else
> QT5WEBENGINE_LICENSE = LGPLv2+, MIT, Commercial license
> QT5WEBENGINE_REDISTRIBUTE = NO
> endif
> QT5WEBENGINE_LICENSE_FILES = Source/WebCore/LICENSE-LGPL-2
> Source/WebCore/LICENSE-LGPL-2.1 Source/WebEngine/LICENSE
>
> ifeq ($(BR2_PACKAGE_QT5BASE_XCB),y)
> QT5WEBENGINE_DEPENDENCIES += xlib_libXext xlib_libXrender
> endif
>
> ifeq ($(BR2_PACKAGE_QT5DECLARATIVE),y)
> QT5WEBENGINE_DEPENDENCIES += qt5declarative
> endif
>
> define QT5WEBENGINE_CONFIGURE_CMDS
> 	(cd $(@D); $(TARGET_MAKE_ENV) $(HOST_DIR)/usr/bin/qmake)
> endef
>
> define QT5WEBENGINE_BUILD_CMDS
> 	$(TARGET_MAKE_ENV) $(MAKE) -C $(@D)
> endef
>
> define QT5WEBENGINE_INSTALL_STAGING_CMDS
> 	$(TARGET_MAKE_ENV) $(MAKE) -C $(@D) install
> 	$(QT5_LA_PRL_FILES_FIXUP)
> endef
>
> ifeq ($(BR2_PACKAGE_QT5DECLARATIVE_QUICK),y)
> define QT5WEBENGINE_INSTALL_TARGET_QMLS
> 	cp -dpfr $(STAGING_DIR)/usr/qml/QtWebEngine $(TARGET_DIR)/usr/qml/
> endef
> endif
>
> define QT5WEBENGINE_INSTALL_TARGET_CMDS
> 	cp -dpf $(STAGING_DIR)/usr/lib/libQt5WebEngine*.so.* $(TARGET_DIR)/usr/lib
> 	cp -dpf $(STAGING_DIR)/usr/libexec/QtWebEngineProcess
> $(TARGET_DIR)/usr/libexec
>       mkdir -p $(TARGET_DIR)/usr/translations/qtwebengine_locales
>       cp -dpf
> $(STAGING_DIR)/usr/translations/qtwebengine_locales/en-US.pak
> $(TARGET_DIR)/usr/translations/qtwebengine_locales
>       cp -dpf $(STAGING_DIR)/usr/qtwebengine_resources.pak $(TARGET_DIR)/usr
> 	$(QT5WEBENGINE_INSTALL_TARGET_QMLS)
> endef
>
> $(eval $(generic-package))
>
> _______________________________________________
> QtWebEngine mailing list
> QtWebEngine at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qtwebengine
>


-- 
Best regards,
András Bécsi
Software Engineer | The Qt Company

The Qt Company AS
Sandakerveien 116
0484 Oslo, Norway

Mailing address:
PO Box 23 Nydalen
0410 Oslo, Norway

Visit us on: http://www.qt.io


From davecortesi at gmail.com  Fri Feb  6 07:47:47 2015
From: davecortesi at gmail.com (David Cortesi)
Date: Thu, 5 Feb 2015 22:47:47 -0800
Subject: [Qtwebengine] QWebEnginePage::FindFlags vs. QWebPage::FindFlags
Message-ID: <CALyzANv6RxPb76yGz3L2z4v8gggFJav9_zSiB+Va_DA9+Zpc=w@mail.gmail.com>

Another functional reduction going from WebPage to WebEnginePage appears to
be in the set of FindFlags supported by the findText() method.

Not too much of a surprise it does not support HighlightAllOccurrences, but
the absence of support for FindWrapsAroundDocument hurts a bit.

There doesn't appear to be any way to emulate a wrap-around search.
findText() doesn't offer a way to specify a starting position, and there is
no concept of a "cursor position" (even though there can be a selection),
so if find returns false, there is no way to say "try again from the top"
-- is there?

Dave Cortesi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20150205/f381d563/attachment.html>

From asarig at interwise.com  Wed Feb 11 15:14:08 2015
From: asarig at interwise.com (Anat Sarig Shmueli)
Date: Wed, 11 Feb 2015 14:14:08 +0000
Subject: [Qtwebengine] QtWebEngine on windows 32 bit
Message-ID: <6B089DEF0C14A341BB7BE0A69E8D9BE83E987A17@ISRTLVEXMX2.interwise.com>

I have WIN32 application that uses Qt4.8.3 with WebKit. I would like to port it to use Qt5.4 with WebEngine.
I downloaded Qt5.4 commercial for evaluation and found that WebEngine.dll exists only for 64 bit OS.
Do you plan to support WIN32 as well ? When ?
Thanks, Anat

 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************



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

From antoine.maillard at gmail.com  Fri Feb 20 09:38:45 2015
From: antoine.maillard at gmail.com (Antoine Maillard)
Date: Fri, 20 Feb 2015 09:38:45 +0100
Subject: [Qtwebengine] armv7, eglfs, qtwebenginewidgets,
 fancybrowser result in blank screen, and how to enable logging.
Message-ID: <CAMfxp0uOCv_QbpfSUKtVRHKWqveQ1wFfYVZYv-S6ppVOveQDXQ@mail.gmail.com>

Hi Laszlo,

I'm facing the same "black tiles" issue with my Qt 5.4 port on ARM/Mali450
platform (eglfs backend).
QtWebEngine works fine if used within Quick app (for instance
quicknanobrowser is OK) but I can only see black tiles if I run the browser
or fancybrowser app (webenginewidget)

According to this thread, you seemed to have the same issue in the past
with iMX6 platform, do you remember how you solved it?

Thanks a lot,

Antoine Maillard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20150220/f5ce7899/attachment.html>

From Andras.Becsi at theqtcompany.com  Fri Feb 20 09:51:53 2015
From: Andras.Becsi at theqtcompany.com (Becsi Andras)
Date: Fri, 20 Feb 2015 08:51:53 +0000
Subject: [Qtwebengine] armv7, eglfs, qtwebenginewidgets,
 fancybrowser result in blank screen, and how to enable logging.
In-Reply-To: <CAMfxp0uOCv_QbpfSUKtVRHKWqveQ1wFfYVZYv-S6ppVOveQDXQ@mail.gmail.com>
References: <CAMfxp0uOCv_QbpfSUKtVRHKWqveQ1wFfYVZYv-S6ppVOveQDXQ@mail.gmail.com>
Message-ID: <9BED3E05-5008-4A7B-90C8-8AA7C265093B@theqtcompany.com>

Hi Antoine,

On 20 Feb 2015, at 9:38 , Antoine Maillard <antoine.maillard at gmail.com<mailto:antoine.maillard at gmail.com>> wrote:

Hi Laszlo,

I'm facing the same "black tiles" issue with my Qt 5.4 port on ARM/Mali450 platform (eglfs backend).
QtWebEngine works fine if used within Quick app (for instance quicknanobrowser is OK) but I can only see black tiles if I run the browser or fancybrowser app (webenginewidget)

According to this thread, you seemed to have the same issue in the past with iMX6 platform, do you remember how you solved it?

This issue has not been fixed yet and we do unfortunately not support webenginewidgets on embedded at the moment.

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

From antoine.maillard at gmail.com  Fri Feb 20 10:16:34 2015
From: antoine.maillard at gmail.com (Antoine Maillard)
Date: Fri, 20 Feb 2015 10:16:34 +0100
Subject: [Qtwebengine] armv7, eglfs, qtwebenginewidgets,
 fancybrowser result in blank screen, and how to enable logging.
In-Reply-To: <9BED3E05-5008-4A7B-90C8-8AA7C265093B@theqtcompany.com>
References: <CAMfxp0uOCv_QbpfSUKtVRHKWqveQ1wFfYVZYv-S6ppVOveQDXQ@mail.gmail.com>
	<9BED3E05-5008-4A7B-90C8-8AA7C265093B@theqtcompany.com>
Message-ID: <CAMfxp0s1hR5vz3mj8cF7bW1OjKg6KrNybr0T86oMAVMZWWXPAQ@mail.gmail.com>

Hi Andras,

Many thanks for the reply.
It's a bug to be fixed or lot of work needs to be done to support
webenginewidgets on embedded platform? If so, is it something you'll
release in next Qt version?

best regards

On Fri, Feb 20, 2015 at 9:51 AM, Becsi Andras <Andras.Becsi at theqtcompany.com
> wrote:

>  Hi Antoine,
>
>  On 20 Feb 2015, at 9:38 , Antoine Maillard <antoine.maillard at gmail.com>
> wrote:
>
>  Hi Laszlo,
>
>  I'm facing the same "black tiles" issue with my Qt 5.4 port on
> ARM/Mali450 platform (eglfs backend).
> QtWebEngine works fine if used within Quick app (for instance
> quicknanobrowser is OK) but I can only see black tiles if I run the browser
> or fancybrowser app (webenginewidget)
>
>  According to this thread, you seemed to have the same issue in the past
> with iMX6 platform, do you remember how you solved it?
>
>
>  This issue has not been fixed yet and we do unfortunately not support
> webenginewidgets on embedded at the moment.
>
>  /Andras
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20150220/4d88e47a/attachment.html>

From okraits at arcor.de  Fri Feb 20 21:48:39 2015
From: okraits at arcor.de (Oliver Kraitschy)
Date: Fri, 20 Feb 2015 21:48:39 +0100
Subject: [Qtwebengine] OpenGL errors and crash
Message-ID: <54E79DA7.2040608@arcor.de>

Hi everybody,

i can't get QWebEngineView to work on my laptop with Arch Linux and 
Intel 855GM Graphics - even with a minimal piece of code i get OpenGL 
errors and the program crashes.

main.cpp:

#include <QWebEngineView>
#include <QApplication>

int main(int argc, char *argv[])
{
     QApplication a(argc, argv);
     QWebEngineView w;
	w.load(QUrl("http://google.de"));
     w.show();

     return a.exec();
}

test.pro:

QT       += core gui webenginewidgets

greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

TARGET = test
TEMPLATE = app

SOURCES += main.cpp

This compiles without errors or warnings. When i run it, i get the 
following output:

QOpenGLFramebufferObject: Framebuffer incomplete attachment.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Framebuffer incomplete attachment.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
Speicherzugriffsfehler (Speicherabzug geschrieben)

Any hints how i can fix this?

Greetings,

Oliver


From Andras.Becsi at theqtcompany.com  Fri Feb 20 22:51:33 2015
From: Andras.Becsi at theqtcompany.com (Becsi Andras)
Date: Fri, 20 Feb 2015 21:51:33 +0000
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <54E79DA7.2040608@arcor.de>
References: <54E79DA7.2040608@arcor.de>
Message-ID: <34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>

Hi,

What version of Qt are you using? Could you run with the —log-level=0 to see more information about what is happening?
This looks like a video driver bug, but if you think there is a bug in QtWebEngine, please create a bug report at https://bugreports.qt.io.

Thanks,
/Andras

On 20 Feb 2015, at 21:48 , Oliver Kraitschy <okraits at arcor.de<mailto:okraits at arcor.de>> wrote:

Hi everybody,

i can't get QWebEngineView to work on my laptop with Arch Linux and
Intel 855GM Graphics - even with a minimal piece of code i get OpenGL
errors and the program crashes.

main.cpp:

#include <QWebEngineView>
#include <QApplication>

int main(int argc, char *argv[])
{
    QApplication a(argc, argv);
    QWebEngineView w;
w.load(QUrl("http://google.de"));
    w.show();

    return a.exec();
}

test.pro:

QT       += core gui webenginewidgets

greaterThan(QT_MAJOR_VERSION, 4): QT += widgets

TARGET = test
TEMPLATE = app

SOURCES += main.cpp

This compiles without errors or warnings. When i run it, i get the
following output:

QOpenGLFramebufferObject: Framebuffer incomplete attachment.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Framebuffer incomplete attachment.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing draw buffer.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
Speicherzugriffsfehler (Speicherabzug geschrieben)

Any hints how i can fix this?

Greetings,

Oliver
_______________________________________________
QtWebEngine mailing list
QtWebEngine at qt-project.org<mailto: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/20150220/c7e98285/attachment.html>

From okraits at arcor.de  Fri Feb 20 23:14:59 2015
From: okraits at arcor.de (Oliver Kraitschy)
Date: Fri, 20 Feb 2015 23:14:59 +0100
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
Message-ID: <20150220221459.GA26781@nohostname.de>

Hi Andras,

i'm using 5.4.0 on Archlinux.
Do you mean i should append "—log-level=0" like "./test —log-level=0"? This
doesn't give me any additional output.

I'm using the xf86-video-intel driver. The test program worked fine with
QWebView so i thought it must be some bug in Qt.

Greetings,

Oliver

On Fri, Feb 20, 2015 at 09:51:33PM +0000, Becsi Andras wrote:
> Hi,
> 
> What version of Qt are you using? Could you run with the —log-level=0 to see
> more information about what is happening?
> This looks like a video driver bug, but if you think there is a bug in
> QtWebEngine, please create a bug report at https://bugreports.qt.io.
> 
> Thanks,
> /Andras


From me at the-compiler.org  Sat Feb 21 18:18:58 2015
From: me at the-compiler.org (Florian Bruhin)
Date: Sat, 21 Feb 2015 18:18:58 +0100
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <20150220221459.GA26781@nohostname.de>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de>
Message-ID: <20150221171858.GB429@tonks>

Hi,

* Oliver Kraitschy <okraits at arcor.de> [2015-02-20 23:14:59 +0100]:
> i'm using 5.4.0 on Archlinux.
> Do you mean i should append "—log-level=0" like "./test —log-level=0"? This
> doesn't give me any additional output.
> 
> I'm using the xf86-video-intel driver. The test program worked fine with
> QWebView so i thought it must be some bug in Qt.

I'm on the same setup (5.4.0 on Archlinux, xf86-video-intel with an
i7-2620M) and this runs fine for me.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20150221/789c224c/attachment.sig>

From Andras.Becsi at theqtcompany.com  Sat Feb 21 18:30:51 2015
From: Andras.Becsi at theqtcompany.com (Becsi Andras)
Date: Sat, 21 Feb 2015 17:30:51 +0000
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <20150220221459.GA26781@nohostname.de>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>,
	<20150220221459.GA26781@nohostname.de>
Message-ID: <ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>

Hi Oliver,

Did you compile Qt and QtWebEngine yourself, did you use a binary installer from qt.io, or do you use them from the packages provided by Arch? I think Arch packages use a different configuration, which might not work with some GPUs.

/Andras



> On 20 Feb 2015, at 23:15, Oliver Kraitschy <okraits at arcor.de> wrote:
> 
> Hi Andras,
> 
> i'm using 5.4.0 on Archlinux.
> Do you mean i should append "—log-level=0" like "./test —log-level=0"? This
> doesn't give me any additional output.
> 
> I'm using the xf86-video-intel driver. The test program worked fine with
> QWebView so i thought it must be some bug in Qt.
> 
> Greetings,
> 
> Oliver
> 
>> On Fri, Feb 20, 2015 at 09:51:33PM +0000, Becsi Andras wrote:
>> Hi,
>> 
>> What version of Qt are you using? Could you run with the —log-level=0 to see
>> more information about what is happening?
>> This looks like a video driver bug, but if you think there is a bug in
>> QtWebEngine, please create a bug report at https://bugreports.qt.io.
>> 
>> Thanks,
>> /Andras


From davecortesi at gmail.com  Sat Feb 21 23:22:32 2015
From: davecortesi at gmail.com (David Cortesi)
Date: Sat, 21 Feb 2015 14:22:32 -0800
Subject: [Qtwebengine] "can't mmap icudtl.dat" in a Mac OS app
Message-ID: <CALyzANsTazjWYggS5fx4nXO984PO2gzRVnX9=n-WmhmyT54m-g@mail.gmail.com>

Building a Mac OS app that uses QtWebEngine.
When the program starts up it terminates with
 [0221/140053:ERROR:icu_util.cc(154)] Couldn't mmap icudtl.dat

The only place apparently the file can be found is the CWD. If I have a
copy of icudtl.dat in the current directory, wherever that may be, then the
above error does not appear!

When I put it in Contents/Resources, it is not found -- unless of course,
x.app/Contents/Resources is the CWD. Then it is found.

I have attempted to use a qt.conf file to locate the file, setting the
ArchData path and the Data path both to "Resources". The app prints out
QLibraryInfo values, thus I know that the qt.conf is being found and
applied: ArchData and Data paths are both being set to
x.app/Contents/Resources.

Where does WebEngineCore (I think) expect to find icudtl.dat, and how can I
persuade it to use the Resources folder?

Thanks,
Dave Cortesi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/qtwebengine/attachments/20150221/45fcefc5/attachment.html>

From Andras.Becsi at theqtcompany.com  Sat Feb 21 23:45:30 2015
From: Andras.Becsi at theqtcompany.com (Becsi Andras)
Date: Sat, 21 Feb 2015 22:45:30 +0000
Subject: [Qtwebengine] "can't mmap icudtl.dat" in a Mac OS app
In-Reply-To: <CALyzANsTazjWYggS5fx4nXO984PO2gzRVnX9=n-WmhmyT54m-g@mail.gmail.com>
References: <CALyzANsTazjWYggS5fx4nXO984PO2gzRVnX9=n-WmhmyT54m-g@mail.gmail.com>
Message-ID: <42C8C2C0-C897-4894-B771-3DBFC97391BF@theqtcompany.com>

Hi David,

We override the path through PathService (base::DIR_QT_LIBRARY_DATA) which on a Mac build where QT_MAC_FRAMEWORK_BUILD is defined should be in the framework bundle Resources/.

If the detected DIR_QT_LIBRARY_DATA path ends up being empty for you it means that the bundle with identifier “org.qt-project.Qt.QtWebEngineCore” is not found, which is most likely because src/core/Info_mac.plist has not been deployed together with the bundle, which could be because you did not use Qt’s macdeployqt to copy the framework and deploy your app properly.

You can find more information about this at the change that added plist file for the framework: https://codereview.qt-project.org/#/c/99052/

/Andras


On 21 Feb 2015, at 23:22 , David Cortesi <davecortesi at gmail.com<mailto:davecortesi at gmail.com>> wrote:

Building a Mac OS app that uses QtWebEngine.
When the program starts up it terminates with
 [0221/140053:ERROR:icu_util.cc(154)] Couldn't mmap icudtl.dat

The only place apparently the file can be found is the CWD. If I have a copy of icudtl.dat in the current directory, wherever that may be, then the above error does not appear!

When I put it in Contents/Resources, it is not found -- unless of course, x.app/Contents/Resources is the CWD. Then it is found.

I have attempted to use a qt.conf file to locate the file, setting the ArchData path and the Data path both to "Resources". The app prints out QLibraryInfo values, thus I know that the qt.conf is being found and applied: ArchData and Data paths are both being set to x.app/Contents/Resources.

Where does WebEngineCore (I think) expect to find icudtl.dat, and how can I persuade it to use the Resources folder?

Thanks,
Dave Cortesi
_______________________________________________
QtWebEngine mailing list
QtWebEngine at qt-project.org<mailto: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/20150221/60b01496/attachment.html>

From okraits at arcor.de  Sun Feb 22 17:25:31 2015
From: okraits at arcor.de (Oliver Kraitschy)
Date: Sun, 22 Feb 2015 17:25:31 +0100
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <20150221171858.GB429@tonks>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de> <20150221171858.GB429@tonks>
Message-ID: <20150222162531.GA32023@nohostname.de>

On Sat, Feb 21, 2015 at 06:18:58PM +0100, Florian Bruhin wrote:

> I'm on the same setup (5.4.0 on Archlinux, xf86-video-intel with an
> i7-2620M) and this runs fine for me.

Hi Florian,

unfortunately this doesn't solve the issue ;-)

What does the Device section of your xorg.conf look like?

Greetings,

Oliver


From okraits at arcor.de  Sun Feb 22 17:36:54 2015
From: okraits at arcor.de (Oliver Kraitschy)
Date: Sun, 22 Feb 2015 17:36:54 +0100
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de>
	<ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>
Message-ID: <20150222163654.GB32023@nohostname.de>

Hi Andras,

i'm using the package qt5-webengine provided by Arch. I can't judge if the
Arch package causes this issue.

I forgot to mention that i have a related issue in qtcreator as well: the
welcome screen is kind of empty and if i run qtcreator from a terminal i
get the error message: QOpenGLShader: could not create shader

glxinfo tells me that OpenGL is working though:

OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
OpenGL version string: 1.3 Mesa 10.4.4

Greetings,

Oliver

On Sat, Feb 21, 2015 at 05:30:51PM +0000, Becsi Andras wrote:

> Did you compile Qt and QtWebEngine yourself, did you use a binary installer from qt.io, or do you use them from the packages provided by Arch? I think Arch packages use a different configuration, which might not work with some GPUs.


From Andras.Becsi at theqtcompany.com  Sun Feb 22 18:44:50 2015
From: Andras.Becsi at theqtcompany.com (Becsi Andras)
Date: Sun, 22 Feb 2015 17:44:50 +0000
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <20150222163654.GB32023@nohostname.de>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de>
	<ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>
	<20150222163654.GB32023@nohostname.de>
Message-ID: <482DBB58-2F8F-4DC4-A624-26CD0200C81D@theqtcompany.com>

Hi Oliver,

I would suggest trying a binary package Qt from qt.io or building QtWebEngine yourself first, to verify that it is not the custom downstream configurations in the qt5-qtwebengine arch package that is causing your problems.

/Andras

> On 22 Feb 2015, at 17:36 , Oliver Kraitschy <okraits at arcor.de> wrote:
> 
> Hi Andras,
> 
> i'm using the package qt5-webengine provided by Arch. I can't judge if the
> Arch package causes this issue.
> 
> I forgot to mention that i have a related issue in qtcreator as well: the
> welcome screen is kind of empty and if i run qtcreator from a terminal i
> get the error message: QOpenGLShader: could not create shader
> 
> glxinfo tells me that OpenGL is working though:
> 
> OpenGL vendor string: Intel Open Source Technology Center
> OpenGL renderer string: Mesa DRI Intel(R) 852GM/855GM x86/MMX/SSE2
> OpenGL version string: 1.3 Mesa 10.4.4
> 
> Greetings,
> 
> Oliver
> 
> On Sat, Feb 21, 2015 at 05:30:51PM +0000, Becsi Andras wrote:
> 
>> Did you compile Qt and QtWebEngine yourself, did you use a binary installer from qt.io, or do you use them from the packages provided by Arch? I think Arch packages use a different configuration, which might not work with some GPUs.



From okraits at arcor.de  Sun Feb 22 19:14:15 2015
From: okraits at arcor.de (Oliver Kraitschy)
Date: Sun, 22 Feb 2015 19:14:15 +0100
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <482DBB58-2F8F-4DC4-A624-26CD0200C81D@theqtcompany.com>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de>
	<ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>
	<20150222163654.GB32023@nohostname.de>
	<482DBB58-2F8F-4DC4-A624-26CD0200C81D@theqtcompany.com>
Message-ID: <20150222181414.GC32023@nohostname.de>

Hi Andras,

i just tried the binary qtcreator package from qt.io and i got the same
error messages and empty welcome screen as i got with the Arch package.

I read that current Qt needs OpenGL 2.0 - is that true?

Then i would have to investigate if i can get OpenGL 2.0 support with
xf86-video-intel and my Intel 855GM graphics chip.

Greetings,

Oliver

On Sun, Feb 22, 2015 at 05:44:50PM +0000, Becsi Andras wrote:
> Hi Oliver,
> 
> I would suggest trying a binary package Qt from qt.io or building QtWebEngine yourself first, to verify that it is not the custom downstream configurations in the qt5-qtwebengine arch package that is causing your problems.


From Andras.Becsi at theqtcompany.com  Sun Feb 22 21:07:32 2015
From: Andras.Becsi at theqtcompany.com (Becsi Andras)
Date: Sun, 22 Feb 2015 20:07:32 +0000
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <20150222181414.GC32023@nohostname.de>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de>
	<ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>
	<20150222163654.GB32023@nohostname.de>
	<482DBB58-2F8F-4DC4-A624-26CD0200C81D@theqtcompany.com>
	<20150222181414.GC32023@nohostname.de>
Message-ID: <DD2567D1-298A-4E48-A249-F7517BD72608@theqtcompany.com>

Hi Oliver,

To my knowledge Qt Quick 2 has a minimum requirement for a graphics driver to at least support OpenGL ES 2.x or higher with the framebuffer_object extension.
Note, that because QtWebEngineWidgets relies on the scene-graph integration we also require the same OpenGL version as Qt Quick 2.

/Andras

On 22 Feb 2015, at 19:14 , Oliver Kraitschy <okraits at arcor.de<mailto:okraits at arcor.de>> wrote:

Hi Andras,

i just tried the binary qtcreator package from qt.io and i got the same
error messages and empty welcome screen as i got with the Arch package.

I read that current Qt needs OpenGL 2.0 - is that true?

Then i would have to investigate if i can get OpenGL 2.0 support with
xf86-video-intel and my Intel 855GM graphics chip.

Greetings,

Oliver

On Sun, Feb 22, 2015 at 05:44:50PM +0000, Becsi Andras wrote:
Hi Oliver,

I would suggest trying a binary package Qt from qt.io or building QtWebEngine yourself first, to verify that it is not the custom downstream configurations in the qt5-qtwebengine arch package that is causing your problems.

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

From okraits at arcor.de  Sun Feb 22 21:22:27 2015
From: okraits at arcor.de (Oliver Kraitschy)
Date: Sun, 22 Feb 2015 21:22:27 +0100
Subject: [Qtwebengine] OpenGL errors and crash
In-Reply-To: <DD2567D1-298A-4E48-A249-F7517BD72608@theqtcompany.com>
References: <54E79DA7.2040608@arcor.de>
	<34003361-4D44-4ECE-8C48-047593A5226A@theqtcompany.com>
	<20150220221459.GA26781@nohostname.de>
	<ED39B3C1-660D-4AE2-8278-3EF3910A70AA@theqtcompany.com>
	<20150222163654.GB32023@nohostname.de>
	<482DBB58-2F8F-4DC4-A624-26CD0200C81D@theqtcompany.com>
	<20150222181414.GC32023@nohostname.de>
	<DD2567D1-298A-4E48-A249-F7517BD72608@theqtcompany.com>
Message-ID: <20150222202227.GD32023@nohostname.de>

Hi Andras,

i looked at Wikipedia for my Intel 855GM Chipset and saw that it only
supports OpenGL 1.3:

https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Second_generation

Seems like i really need to retire my good old Thinkpad :)

Thanks for you help!

Greetings,

Oliver

On Sun, Feb 22, 2015 at 08:07:32PM +0000, Becsi Andras wrote:
> Hi Oliver,
> 
> To my knowledge Qt Quick 2 has a minimum requirement for a graphics driver to
> at least support OpenGL ES 2.x or higher with the framebuffer_object extension.
> Note, that because QtWebEngineWidgets relies on the scene-graph integration we
> also require the same OpenGL version as Qt Quick 2.
> 
> /Andras