Buggy on plasma 6.1 (black background)

[dgudim]

Describe the Bug

Upon effect activation the window turns black and that black rectangle is animated

Steps to reproduce the behavior:

1. Install effect from kde store
2. Use it
3. See error

System

Please complete the following information:

• Linux distribution: Arch
• Burn-My-Windows version: Latest from kde store
• Plasma 6.1.0, Qt 6.7.1, frameworks 6.3.0

Screencast_20240620_133957.webm

[Schneegans]

Hi there! Thanks for the report. Does this happen with all applications? Or just with specific ones? And did you observe this with older Plasma versions as well?

I would assume that this is an issue in KWin and not something we can fix on the effect side of things...

[dgudim]

Sorry for the delay. Yeah, after some tinkering I think this is a kwin bug, this happens after wake from sleep/hibernate in about 10% of the cases (on amd and nvidia, but not on intel it seems). I am not able to consistently reproduce this though :(

[nask0]

Sorry for the delay. Yeah, after some tinkering I think this is a kwin bug, this happens after wake from sleep/hibernate in about 10% of the cases (on amd and nvidia, but not on intel it seems). I am not able to consistently reproduce this though :(

I had a similar issue while ago, was persistent on my old machine at some point. Creating a new user fixed the issue than, IIRC it was some messy configuration on ~/.config/ somewhere but was unable to narrow down further.

[KR3C1K]

My case is similar.
Wayland has a issue with this, on X11 works fine.
But when on wayland in the terminal I type:
dbus-run-session startplasma-wayland
The window with the wayland session opens, and here all effects work correctly.
How to get the same effect in the session to which he logs in after the start of the computer .

[yuyuyak]

I think perhaps you adjusted the config and the config gets written improperly in kwinrc. I installed it on plasma 6.1 also, here's an example mod on the config it wrote for me:

[Effect-kwin4_effect_fire]
3DNoise=true
Gradient1=invalid
Gradient2=invalid
Gradient3=invalid
Gradient4=invalid
Gradient5=invalid

It doesn't like the Gradient[1-5]=invalid entries and I get exactly the same results described above. If you simply remove those it works properly again after logging out and back in, no need for complete reboot. A bit of a nuisance if you want to play with the config and I have no idea what to do with the gradient settings (color picker?), but it's no problem after that's done.

[yuyuyak]

Also, when starting kwin manually, it complains that $HOME/.local/share/kwin/effects/kwin4_effect_fire/metadata.json has a string setting for EnabledByDefault, when it should be boolean, so I changed this line in the file:
EnabledByDefault": "false",
to
EnabledByDefault": 0,
Maybe my imagination, but seems to work smoother now.

[nask0]

Also, when starting kwin manually, it complains that $HOME/.local/share/kwin/effects/kwin4_effect_fire/metadata.json has a string setting for EnabledByDefault, when it should be boolean, so I changed this line in the file: EnabledByDefault": "false", to EnabledByDefault": 0, Maybe my imagination, but seems to work smoother now.

I believe this is fixed in the latest relase (changelog)