Bug 1759490

Summary: Fedora 33: Wayland: qtwebengine-based applications cannot be full screened
Product: [Fedora] Fedora Reporter: Ankur Sinha (FranciscoD) <sanjay.ankur>
Component: qt5-qtwaylandAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 33CC: awilliam, fmuellner, fzatlouk, gmarr, gnome-sig, jadahl, jgrulich, jreznik, kde-sig, kevin, kparal, lkundrak, mboddu, otaylor, pasik, philip.wyett, pierluigi.fiorini, rdieter, robatino, than
Target Milestone: ---Keywords: CommonBugs, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: RejectedBlocker RejectedFreezeException https://fedoraproject.org/wiki/Common_F31_bugs#qtwebengine-no-fullscreen
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-11-30 17:55:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ankur Sinha (FranciscoD) 2019-10-08 10:20:11 UTC
Description of problem:
QT applications running in Gnome shell using Wayland cannot be full screened.

Version-Release number of selected component (if applicable):
$ rpm -qa \*gnome-shell\* \*qgnome\* \*falkon\* \*qutebrowser\*
gnome-shell-3.34.0-3.fc31.x86_64
qutebrowser-1.8.1-1.fc31.noarch
qgnomeplatform-0.5-13.fc31.x86_64
falkon-3.1.0-2.fc31.x86_64


How reproducible:
Always

Steps to Reproduce:
1. Run a QT application in Gnome shell using Wayland
2. Press F11 to full screen (or click the full screen button in a youtube video)
3.

Actual results:
The application can no longer be seen. The application behind it is shown.

Expected results:
Should full screen normally.

Additional info:

Comment 1 Ankur Sinha (FranciscoD) 2019-10-08 10:25:06 UTC
Just tried VLC, works there. Does not work in Qutebrowser/Falkon, though.

Comment 2 František Zatloukal 2019-10-08 10:38:19 UTC
VLC is using XWayland, so it looks like this issue is affecting all QT apps that don't force XWayland under Wayland session.
If you run falkon with forced XWayland, it works in fullscreen just fine. You can do that by setting QT_QPA_PLATFORM=xcb .

So, "QT_QPA_PLATFORM=xcb falkon" works just fine.

I don't think it's blocker worthy, but proposing it as blocker won't hurt anything.

Comment 3 Jan Grulich 2019-10-08 11:05:08 UTC
Looks like https://bugreports.qt.io/browse/QTBUG-63748. There is even a PR which was not merged https://codereview.qt-project.org/c/qt/qtwayland/+/199123. I asked in the PR so let's see what is the status and whether we can backport it to Fedora if it gets merged.

Comment 4 Jan Grulich 2019-10-08 11:42:13 UTC
Ok, based on the comment it should be already implemented. I will try to look why it doesn't work once I find some time.

Comment 5 Jonas Ådahl 2019-10-08 15:14:10 UTC
Moving to qt5-qtwayland then.

Comment 6 Jan Grulich 2019-10-09 10:21:58 UTC
Opened upstream bug: https://bugreports.qt.io/browse/QTBUG-79106

Comment 7 Kamil Páral 2019-10-09 11:17:03 UTC
Proposing for a blocker discussion.

Comment 8 Jan Grulich 2019-10-09 11:36:35 UTC
I don't think this should be considered as a blocker, this issue affects only applications using qtwebengine and those are only Falkon and Qutebrowser. Those are not even installed by default on Fedora Workstation.

Comment 9 Kamil Páral 2019-10-10 16:29:19 UTC
-1 blocker per comment 8. If this affects just 2 applications, this is a very niche problem.

Comment 10 Kevin Fenzi 2019-10-10 17:35:34 UTC
note that calibre (as of 4.0.0) is also using qtwebengine.

I'm -1 blocker, +1 FE

I also don't see this on rawhide...

Comment 11 Mohan Boddu 2019-10-10 17:36:07 UTC
I agree with Jan here and -1 Blocker.

Comment 12 Ben Cotton 2019-10-10 17:37:53 UTC
-1 blocker since it doesn't affect default packages. +1 FE

Comment 13 František Zatloukal 2019-10-10 17:47:03 UTC
-1 Blocker, +1 FE

Comment 14 Adam Williamson 2019-10-10 18:00:14 UTC
That's -5 blocker, so rejecting as a blocker. +3 FE, but I think I'd want to make the case for -1 FE; this shouldn't really affect anything out of the box, and I'm not sure I'd want to poke the release Qt package during a freeze just to fix this. I think I'd actually be happier with this as a zero-day update than an FE. So I'm gonna say we're at -1/+3 FE and leave that status open for now.

Comment 15 Geoffrey Marr 2019-10-14 19:15:07 UTC
Discussed during the 2019-10-14 blocker review meeting: [0]

The decision to classify this bug as a "RejectedFreezeException" was made as we don't see any convincing benefit to granting an FE here, the only case it would really help is someone installing a qtwebengine-based app in a Workstation live session, which seems like a pretty unusual scenario. We think it's fine for this to go as a regular update.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-10-14/f31-blocker-review.2019-10-14-16.01.txt

Comment 16 Ben Cotton 2020-11-03 15:38:27 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 17 Ben Cotton 2020-11-24 17:38:35 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 18 Ankur Sinha (FranciscoD) 2020-11-24 17:49:49 UTC
Still a bug in F33, reopening.

Comment 19 Ankur Sinha (FranciscoD) 2021-02-04 12:06:16 UTC
Hello,

Any updates here? If there's any testing etc. that I could help with, please do let me know. 

Cheers,
Ankur

Comment 20 Rex Dieter 2021-02-04 13:05:03 UTC
Upstream bug has nothing recent,
https://bugreports.qt.io/browse/QTBUG-79106

Comment 21 Ankur Sinha (FranciscoD) 2021-02-04 15:00:06 UTC
Oh :(

Thanks for checking Rex. I'll try to keep an eye on it myself too.

Comment 22 Ben Cotton 2021-11-04 16:08:41 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 23 Ben Cotton 2021-11-30 17:55:04 UTC
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.