Bernd Busse

> BTW, I am trying to rebasing this PR. Okay. I would do that myself, but I'm still quite limited on time. If you need any hints, let me know....

> I am thinking adding a `create_shader` backend API, and let frontend track path -> shader. As long as we keep this consistent across backend destruction and recreation, this might...

This file is not actually read by picom. It only contains an example window shader to be used with `--glx-fshader-win` option. This option takes a shader string as the parameter...

This is not specific to any blur method — it is just easily visible with the high blur levels that `dual_kawase` efficiently supports. Neither of the supported blur methods currently...

It seems your `picom` binary is stripped. Can you build picom yourself with debug symbols (see last paragraph [here](https://github.com/yshui/picom/wiki/Reporting-issues#get-a-stack-trace)) and post a backtrace of the crash using that binary?

> * Apply the blur when and only when the window is inactive and focus mode is enabled If I am not mistaken, similar logic to opacity is needed that...

> Edit: Also, sorry, what would the behavior of `inactive-blur-exclude` be? Analogous to the other `*-exclude` options, windows that match the rules in there should not be affected by the...

These color bands are especially apparent at large blur-radii which results in very fine gradients. More noticeable on darker images (usually the case with transparent background). - Are we okay...

Ping @yshui: - Are we okay with an implementation only in the experimental backends? *(I think yes)* - Are we okay with only implementing noise dithering for the glx backend?...

Most likely a duplicate of https://github.com/yshui/picom/issues/728 (i.e. a driver issue with VMware).