Bug 1768033 - Qt Wayland programs are missing window shadow
Summary: Qt Wayland programs are missing window shadow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: qgnomeplatform
Version: 33
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-01 22:41 UTC by Christian Rauch
Modified: 2022-08-31 15:44 UTC (History)
14 users (show)

Fixed In Version: qgnomeplatform-0.8.4-12.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-30 19:09:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Qt application on GNOME Shell (114.45 KB, image/png)
2019-11-01 22:41 UTC, Christian Rauch
no flags Details
Qt application on KDE Plasma (56.78 KB, image/png)
2019-11-01 22:44 UTC, Christian Rauch
no flags Details

Description Christian Rauch 2019-11-01 22:41:32 UTC
Created attachment 1631702 [details]
Qt application on GNOME Shell

Description of problem:

All Qt applications that run via Wayland on GNOME Shell are missing shadows and do not respect the window titlebar settings for minimise and maximise buttons.

The missing shadows make it difficult to distinguish a Qt application from the background. Since the window border is very thin, it is very difficult to hit the border to resize the window. 


Steps to Reproduce:
1. start any application that used the Qt toolkit (e.g. qterminal)
2. activate maximise and minimise titlebar buttons in GNOME tweak tool


Actual results:
1. no window shadows are shown
2. window button changes are not applied to Qt application


Expected results:
1. shadows are shown to distinguish Qt application from background
2. minimise and maximise buttons are shown


Additional info:

Comment 1 Christian Rauch 2019-11-01 22:44:54 UTC
Created attachment 1631703 [details]
Qt application on KDE Plasma

Qt application via Wayland on KDE Plasma shows window shadows

Comment 2 klaussemmler 2021-09-18 23:52:51 UTC
I can confirm this issue on fedora 34 with the latest updates.

This makes it hard to use qt based apps on wayland. As a workaround I set the environment variable QT_QPA_PLATFORM=xcb. This however makes flatpaks fail to launch if X11 Support or X11 fallback support is disabled for the app. In this case, I use the flatseal app to fix this.

It would be great if this issue could be further investigated and fixed. Just using the x11 backend for qt based apps is not a sustainable solution as wayland will be the default in the future and x11 support will be deprecated over time.

Comment 3 Ben Cotton 2021-11-04 13:43:33 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 4 Ben Cotton 2021-11-04 14:13:03 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 5 Ben Cotton 2021-11-04 15:10:40 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 6 Ben Cotton 2021-11-30 19:09:15 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.

Comment 7 Fedora Update System 2022-08-25 11:31:42 UTC
FEDORA-2022-69bf07b7ea has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-69bf07b7ea

Comment 8 Fedora Update System 2022-08-26 11:56:34 UTC
FEDORA-2022-69bf07b7ea has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-69bf07b7ea`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-69bf07b7ea

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2022-08-30 09:05:13 UTC
FEDORA-2022-69bf07b7ea has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 klaussemmler 2022-08-31 15:44:42 UTC
Thanks for the update! I'm finally able to resize windows of qt-based applications without losing my mind in the gnome wayland session. 
But I have found one issue. If the window gets resized or if it loses focus, the shadow of the window is not visible. The size of the resize area stays the same though so it is still easy to resize the window. When the window has focus, the shadow gets rendered correctly.


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