SUMMARY In Konsole, I set the background to be 10% transparent and blurred. On X11 with Breeze, this setting does not affect Dolphins terminal panel which always stays opaque. On Wayland, however, it does become transparent (except for a glitchy looking opaque bar at the top). Also, the background is only transparent, not blurred. It looks rather broken. STEPS TO REPRODUCE 1. Enable background transparency in Konsole. Also enable blur. 2. Use the default Breeze application style (I used the Breeze Dark color scheme) 3. Open Dolphin on Wayland 4. Show the built-in terminal with F4. OBSERVED RESULT The terminal panel is transparent, but not blurred. A flickering bar at the top of the terminal panel is not transparent and seems to show parts of older frames of the terminal some of the time. EXPECTED RESULT The terminal inside Dolphin should either a) ignore the transparency setting and stay opaque like it does on X11, or b) it should be transparent AND BLURRED, without a weird glitchy bar at the top (like on X11 with some third party Application styles). SOFTWARE/OS VERSIONS Operating System: Fedora 34 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Graphics Platform: Wayland
This appears to be fixed as I cannot reproduce it on KDE Neon unstable.
Hi, this bug seems to be still present. I face it on archlinux with the latest updates on 3 different machines. SOFTWARE/OS VERSIONS Operating System: Arch linux with latest updates KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Graphics Platform: Wayland I face it on 2 machines with AMD graphics as well as 1 machine with Intel graphics.
(In reply to Nico Kümmel from comment #2) > Hi, > this bug seems to be still present. I face it on archlinux with the latest > updates on 3 different machines. > > SOFTWARE/OS VERSIONS > Operating System: Arch linux with latest updates > KDE Plasma Version: 5.27.5 > KDE Frameworks Version: 5.106.0 > Qt Version: 5.15.9 > Graphics Platform: Wayland > > I face it on 2 machines with AMD graphics as well as 1 machine with Intel > graphics. Yes, it seems to have returned. It was fixed for a while but now I can reproduce it again.