Created attachment 1948661 [details] journalctl --no-pager |grep kwin_wayland Description of problem: Visual artifacts and intermittent interface freezes when applying a particular theme with transparency enabled. I’ve noticed a transparency option in KDE settings (workspace behaviour - Desktop effects - Translucency), but it only makes windows translucent during dragging. I tried to attempt making everything transparent and see how it goes. After some searches it appears you have to apply a theme that has it in settings. There was one amoung several available called “Spectrum Spite”, which made the taskbar and the rest of the windows transparent. Around then the problems started: 1) several GUI applications installed into a toolbox, in particular this one: doublecmd-common.x86_64 1.0.10-1.fc38 @rawhide doublecmd-gtk.x86_64 1.0.10-1.fc38 @rawhide When i ran them no matter inside the toolbox (or outside with toolbox run), their GUI and mouse froze intermittently (for several seconds I can't type, move windows or cursor, or type, then everything goes back to normal for several seconds; repeat). Intermittent total freezes (very annoying!) lasted until the app was running outside the toolbox. 2) at least one app installed outside the toolbox - VLC flatpak - had visual artefacts - flickering and distorted title bar - while playing videos. Several others did not (MPV). When I’ve applied the standard Breeze theme (without transparent effects), all the issues disappeared - even VLC window is without artifacts, and GUI programs that I launch out of the toolbox no longer cause freezes (at least it seems). Version-Release number of selected component (if applicable): Fedora-Kinoite-ostree-x86_64-Rawhide-20230306.n.0 with KDE Plasma 5.27.2 How reproducible: Always Steps to Reproduce: 1. install Fedora-Kinoite-ostree-x86_64-Rawhide-20230306.n.0 and make an external monitor primary with 150% or 200% fractional scaling (not sure if it's important). Create a toolbox and dnf install doublecmd-gtk inside the toolbox. 2. install VLC 3.0.18 from Flathub in Discover. 3. in KDE settings (Workspace behaviour - Desktop effects) enable translucency option; 4. in KDE settings (Appearance - Global Theme), select Get New Global Themes 5. select, download and apply “Spectrum Spite” 6. play a video file in VLC placed on an external monitor; the titlebar and window border should flicker; and the title bar possibly be distorted. 7. run doublecmd from inside or outside of toolbox: the GUI will show up and frezees will start until the app will be closed. Actual results: 1) several applications (like VLC) have their window border and title bar distorted and flickering. 2) several GUI applications, at least in a toolbox, like doublecmd, cause severe systemwide freezes, making the system unusable. Expected results: All applications have their GUI without artifacts or flickering. all GUI applications (including those in toolboxes) run without casing any freezes. Additional info: 1) Fractional scaling enabled: 150% on one screen and 200% on another. 2) VLC titlebar artefacts were the worst on the usb-c display chained through thunderbolt. 3) several wayland-related errors in the logs (see the attached text file) 4) $ glxinfo | grep OpenGL: OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2) OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.0.0 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.0.0 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.0.0 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions:
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
Perhaps this is related? Currently in Fedora Kinoite 40, toolbox containers fail to resolve their own hostname "toolbox". This seem to cause all X11-based applications to completely hang kwin/wayland for few seconds on KDE. During the hang no application updates display and mouse cursor is frozen in place. The doublecmd-gtk mentioned earlier causes freezes when the application starts or menus are opened and closed. The issues stop if the container hostname is changed to localhost ("sudo hostname localhost").
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 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 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.