Bug 14794 - Enable/Provide QtWebEngine module
Summary: Enable/Provide QtWebEngine module
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: Mageia 6
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks: 18097
  Show dependency treegraph
 
Reported: 2014-12-13 14:42 CET by Johnny Accot
Modified: 2017-07-18 21:44 CEST (History)
3 users (show)

See Also:
Source RPM: qtbase5-5.4.0-1.mga5.src.rpm
CVE:
Status comment:


Attachments
QtWebEngine spec file (9.24 KB, text/x-rpm-spec)
2015-07-10 08:07 CEST, Johnny Accot
Details

Description Johnny Accot 2014-12-13 14:42:04 CET
Description of problem:

QtWebEngine [1] is Qt's new web renderer, first available for Qt 5.3 but officially introduced in Qt 5.4 [2].  QtWebEngine deprecates QtWebKit and is one of the main "hot" features in Qt 5.4.

Mageia's Cauldron now includes Qt 5.4 but, for some reason, the new QtWebEngine module does not seem to be provided by any package.  Searching for "webengine" in packages [3] yields no significant result.

I think it would be very beneficial for Mageia 5 to include the QtWebEngine module along with QtWebKit.  I don't know if it's just a matter of enabling a configuration option when building Qt or if an external source is needed.

As of today, at least the QupZilla browser can be built to use QtWebEngine instead of QtWebKit [4,5].  Attempting to build QupZilla with QtWebEngine fails today (with all Qt5 packages installed) with the following error message: âUnknown module(s) in QT: webenginewidgetsâ.

The release announcement for Qt 5.4 mentions two other new modules: QtWebChannel 
 and QtWebView.  My guess is that they are somehow related to QtWebEngine and should be provided at the same time.


[1] http://qt-project.org/wiki/QtWebEngine
[2] http://blog.qt.digia.com/blog/2014/12/10/qt-5-4-released/
[3] $ urpmf -i webengine
[4] http://www.cupoflinux.com/SBB/index.php/topic,446.msg3103.html
[5] https://github.com/jturcotte/qupzilla-qtwebengine

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-12-14 00:03:50 CET

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 Nicolas Lécureuil 2014-12-21 18:12:11 CET
ok adding it.
Comment 2 Nicolas Lécureuil 2014-12-27 03:07:54 CET
it does not build, i need to find how to fix .
Comment 3 Samuel Verschelde 2015-05-31 19:25:50 CEST
(In reply to Nicolas Lécureuil from comment #2)
> it does not build, i need to find how to fix .

Have you found since?

Keywords: (none) => NEEDINFO

Comment 4 Johnny Accot 2015-07-07 09:30:45 CEST
Qt 5.5 was released on July 1st.  With this release, Qt WebKit is officially deprecated in favor of Qt WebEngine [1].  I'd be glad to help and get Qt WebEngine to compile in Mageia.  Do you have a specific spec file or should I start out with the WebKit one? Thanks in advance.

[1] https://wiki.qt.io/New_Features_in_Qt_5.5#Deprecated_Functionality
Samuel Verschelde 2015-07-07 10:25:51 CEST

Keywords: NEEDINFO => (none)

Comment 5 Johnny Accot 2015-07-10 08:07:51 CEST
Created attachment 6831 [details]
QtWebEngine spec file

I successfully compiled and packaged QtWebEngine with the attached spec file.  The compilation error was fixed by setting the following environment variable:

export GYP_DEFINES="disable_fatal_linker_warnings="

before building, as suggested here:

http://code.google.com/p/chromium/issues/detail?id=378006
Comment 6 Johnny Accot 2015-09-12 10:08:52 CEST
Qt WebKit will be officially removed from Qt 5.6 [1], which should be released in December [2].  Of course it will be possible to build it on the side but it makes a lot of sense to look into packaging Qt WebEngine, IMHO.

[1] https://wiki.qt.io/New_Features_in_Qt_5.6#Removed_Modules
[2] https://wiki.qt.io/Qt-5.6-release
Comment 7 Otto Leipälä 2016-03-31 13:20:28 CEST
Qupzilla 2.0 qtwebengine is released to stable,can somebody take a look this qtwebengine in Cauldron and try to build new qupzilla ?.

http://blog.qupzilla.com/2016/03/qupzilla-200-released-with-qtwebengine.html

CC: (none) => otto.leipala

Comment 8 Nicolas Lécureuil 2016-03-31 13:50:58 CEST
it on my todo, i will try today or tomorow.
Comment 9 Otto Leipälä 2016-04-02 09:06:33 CEST
I builded qupzilla against qtwebengine qt provided binaries i found bug in ssl it can't connect to google at all.
https://github.com/QupZilla/qupzilla/issues/1870
https://download.qt.io/archive/qt/5.6/5.6.0/
Frédéric "LpSolit" Buclin 2016-04-02 12:05:41 CEST

CC: (none) => LpSolit
Blocks: (none) => 18097
Summary: Enable/Provide Qt 5.4's QtWebEngine module => Enable/Provide QtWebEngine module

Comment 10 Frédéric "LpSolit" Buclin 2016-04-09 02:24:23 CEST
(In reply to Nicolas Lécureuil from comment #8)
> it on my todo, i will try today or tomorow.

Today or tomorrow of which week? ;)
Comment 11 Otto Leipälä 2016-04-09 10:09:45 CEST
Which year ?.
Comment 12 Nicolas Lécureuil 2016-04-09 10:32:32 CEST
"try" means that this is something not 100% sure.

When something is 100% the word used is WILL.

qtwebengine5 is on the BS, let see if it builds.
Comment 13 Frédéric "LpSolit" Buclin 2016-04-12 19:36:37 CEST
QtWebEngine is in Cauldron. Thanks Nicolas! :)

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 14 Frédéric "LpSolit" Buclin 2016-04-12 19:41:06 CEST
All RPMs can be installed correctly except libqt5webengine-devel-5.6.0-1.mga6.i586 because "devel(libv8) is not satisfied"
Comment 15 David GEIGER 2016-04-13 08:18:25 CEST
Should be fixed now with qtwebengine5-5.6.0-3.mga6.

CC: (none) => geiger.david68210

Comment 16 Otto Leipälä 2016-04-13 09:22:49 CEST
Thanks there is other problem qupzilla drop support to old qtwebkit so we may need to provide qtwebengine to Mageia 5,otherwise we do have unsupported qupzilla in stable release.
Comment 17 Frédéric "LpSolit" Buclin 2016-04-13 16:12:47 CEST
(In reply to Otto Leipälä from comment #16)
> Thanks there is other problem qupzilla drop support to old qtwebkit so we
> may need to provide qtwebengine to Mageia 5,otherwise we do have unsupported
> qupzilla in stable release.

QupZilla 2.0 requires Qt 5.6.0 or newer. Mageia 5 has Qt 5.4.2. IMO, Qupzilla 2.0.0 should only land in Cauldron.
Comment 18 Otto Leipälä 2016-04-13 17:26:08 CEST
No then we don't get any security fixes to qupzilla in Mageia 5 what's supported to december 2016.
Comment 19 Nicolas Lécureuil 2016-04-13 23:35:52 CEST
we will have to pick sec patches from the qupzilla git repo.
Comment 20 Otto Leipälä 2016-04-19 12:25:33 CEST
(In reply to Frédéric Buclin from comment #17)
> (In reply to Otto Leipälä from comment #16)
> > Thanks there is other problem qupzilla drop support to old qtwebkit so we
> > may need to provide qtwebengine to Mageia 5,otherwise we do have unsupported
> > qupzilla in stable release.
> 
> QupZilla 2.0 requires Qt 5.6.0 or newer. Mageia 5 has Qt 5.4.2. IMO,
> Qupzilla 2.0.0 should only land in Cauldron.

Not a problem system can have unlimited amount different qt versions installed same time so backporting it from Cauldron is possible and very easy.
I have right now qt 5.4 5.5 5.6 installed in test install where i build lot of my qt5 apps.
Comment 21 Otto Leipälä 2016-04-25 12:30:07 CEST
I reopen this as it can be backported to Mageia 5 as qupzilla legacy is unsupported officially discontinued.

Bugs google drive if i close from x whole browser crash in second.

My favorite ruutu.fi (finnish) video site won't work black screen in every video it's fixed in webengine version,lot of other page i can't browse because qupzilla first freeze and then crash.

There is no point to even try to give any errors log it's useless this point when those are upstream fixed already.

Also qt 5.6 is fully compatible with qt 5.4 so they can be installed same time to system.

Here is so many reasons enough to backport it to Mageia 5.

Status: RESOLVED => REOPENED
Component: RPM Packages => Backports
Resolution: FIXED => (none)
Summary: Enable/Provide QtWebEngine module => Backport qt 5.6/QtWebEngine module to Mageia 5

Otto Leipälä 2016-04-25 12:30:31 CEST

Target Milestone: --- => Mageia 5

Comment 22 Frédéric "LpSolit" Buclin 2017-07-18 21:44:16 CEST
Per discussion with neoclust and Akien on IRC, Qt 5.6 won't be backported to Mageia 5, which will reach EOL in 3 months. Restoring old bug summary and re-closing this bug.

Resolution: (none) => FIXED
Summary: Backport qt 5.6/QtWebEngine module to Mageia 5 => Enable/Provide QtWebEngine module
Component: Backports => RPM Packages
Status: REOPENED => RESOLVED
Target Milestone: Mageia 5 => Mageia 6


Note You need to log in before you can comment on or make changes to this bug.