Description of problem: Frequent error messages when using Wayland Version-Release number of selected component (if applicable): mscore-3.4.2-2.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. Open A session in Wayland (not X11) 2. Launch MuseScore in a console 3. Observe the error messages in the console Actual results: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() qt.qpa.wayland: Wayland does not support QWindow::requestActivate() ... Expected results: No error messages Additional info: No error message if using $ export QT_QPA_PLATFORM=xcb $ musescore
In the Flatpak version they use "QT_QPA_PLATFORM=xcb" https://github.com/flathub/org.musescore.MuseScore/blob/master/org.musescore.MuseScore.yaml " # Enable Wayland but keep X11 default for now - --socket=wayland - --env=QT_QPA_PLATFORM=xcb "
(I'm on Debian so this comment is not specific to RH) This issue is also causing a crash in the Zoom client (v5.4.7, the videoconferencing proprietary software). My workaround is to install the xwayland package. I feel that QT are not yet ready for a Wayland-without-xwayland experience, I have tried using `QT_QPA_PLATFORM=wayland-egl` or `QT_QPA_PLATFORM=wayland` but it crashes. graphic card and MESA video driver: qt.scenegraph.general: GL_VENDOR: Intel qt.scenegraph.general: GL_RENDERER: Mesa Intel(R) UHD Graphics 620 (KBL GT2) qt.scenegraph.general: GL_VERSION: 4.6 (Compatibility Profile) Mesa 20.2.6
Qt doesn't consider this a bug in their stuff. https://forum.qt.io/topic/90639/comparing-qt-widgets-app-under-gnome-wayland-using-platform-wayland-egl-to-xcb/7 "...This means your window tried to grab focus in the compositor, which is not allowed in wayland. Don't create a bug for it, there's nothing we can do."
That was in 2018. Maybe in 3 years things could change a bit ? In anycase, I would be interested to know what could e done on developer side to avoid "grabing the focus in the compositor". At least we could push for some practices that would avoid triggering this issue.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. 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 '32'. 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 32 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.
Still a problem in F34.
Still in Fedora 35 with digikam.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 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. Thank you for reporting this bug and we are sorry it could not be fixed.