Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1758411

Summary: Qt5 applications no longer have window decorations
Product: [Fedora] Fedora Reporter: Dima Ryazanov <dima>
Component: qt5-qtwaylandAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 31CC: jgrulich, jreznik, kde-sig, lkundrak, pierluigi.fiorini, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-04 05:28:55 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 Dima Ryazanov 2019-10-04 04:59:33 UTC
Description of problem:
After installing today's updates - in particular, Qt5 - I tried running Qt5 examples, and saw that they're all missing window decorations.

Version-Release number of selected component (if applicable):
qt5-qtwayland-5.12.5-1.fc31.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Run /usr/lib64/qt5/examples/widgets/richtext/textedit/textedit (or any other example)
2.
3.

Actual results:
The window is missing decorations. There is an error message in the output:
"Could not create decoration from factory! Running with no decorations."

Expected results:
The window should display decorations.

Additional info:
Using Gnome 3.34.0

Comment 1 Jan Grulich 2019-10-04 05:28:55 UTC
Should be fixed with latest QGnomePlatform update, which is qgnomeplatform-0.5-17.fc31.

*** This bug has been marked as a duplicate of bug 1756024 ***