Random coloring on rounded corners

[psyleft]

First of all thanks for the awesome plugin, but I'm having a very strange issue. I'm on arch linux running wayfire compiled from source on the most recent master branch, using system wlroots. Likewise with firedecor, compiled from source on the most recent master branch. The problem is that there are strange gaps in the border near the top and bottom of the window, and when I add a corner radius these gaps become bright red instead. Also, you seem to be able to see the border color behind the outlines, in the corner.

Here is an image album of the problem in question.
https://postimg.cc/gallery/TXsFQ3L

[AhoyISki]

It is very likely that firedecor is installed in the wrong place. Because the plugin expects the user to download the wayfire-git package from the aur, it installs firedecor at /usr/lib/wayfire/libfiredecor.so. But since you installed wayfire manually, I think the actual plugin install for your build would be at /usr/local/lib/wayfire/. It may be the case that you're using an older version of firedecor, where I remember using those red colors for testing reasons, and before I changed things to install in the "expected" place. Can you check if there is a /usr/lib/wayfire/libfiredecor.so? If there is, try moving it to the /usr/local/lib/wayfire/ directory, since things in /usr/local/lib/ have priority over things in /usr/lib/.

[AhoyISki]

I still have to figure out how to have meson find the correct installation directory for both cases

[psyleft]

Hmm... libfiredecor.so seems to have been correctly installed to /usr/local/lib/wayfire.

I guess I should mention that I installed both wayfire and firedecor to /opt and then used gnu stow to place them in /usr/local. Firedecor recognizes this just fine and meson puts all the files in the right place. I tried recompiling and still had the same issue. The reason I didn't use the aur package in the first place was because there was a conflict with the standard wlroots, but on the wayfire-git page someone has posted an updated pkgbuild. I'll try doing this the "standard" way and see if it works. If so it was probably some strange issue specific to my system of the way I built the package.