Closed RaitaroH closed 3 years ago
Which compositor rendering backend do you use, and which others are available?
Here:
When I last tried OpenGL 2.1 and 3.0 in lieu of XRender, there were problems e.g. blacked-out areas in Waterfox Classic and some other apps.
According to the Compositor settings I have: Scale method: Smooth Rendering backend: OpenGL 3.1 vsync: Auto
Edit: I just tested it out and it happens on OGL 3.1, 2.0 and xRender too. For xRender it almost looks like the window is not even there at all.
I have discovered another way this happens.
I thought perhaps is happening only when the laptop is on AC, but happens even when on power (I notice this after a few experiments). I also thought perhaps it happens if on the 2nd desktop I change the power from AC to battery, or vice-versa. It might be possible that a combination of the above causes kwin to start hanging and maybe waterfox to react, I am not sure.
Edit: after logging out and back in, I can say the above still holds true, but I am not sure if the power status change affects anything.
Describe the bug Waterfox becomes transparent after waking the laptop from sleep.
To Reproduce Steps to reproduce the behavior:
systemctl suspend
, but the normal kde way of doing it with theApplication Launcher
>Leave
>Sleep
also causes this.loginctl unlock-session
instead of typing my password for the bug happen as long as step 1 is in check.Expected behavior Waterfox alpha becomes transparent for some odd reason.
Screenshots
Desktop (please complete the following information): Operating System: KDE neon 5.16 KDE Plasma Version: 5.16.2 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.3 Kernel Version: 4.15.0-54-generic OS Type: 64-bit Waterfox: 68.0a1 (2019-05-07) (64-bit)
Additional information I have almost all windows be transparent with a kwin rule. Waterfox is one of the windows that I make transparent. Making waterfox 100% transparent doesn't change anything if steps are reproduced, I tried. Also obviously this is the only application where this happens.