What I did until:
a) Renaming and by that resetting the .config files by hand
b) -Rcns latte-dock and reinstall
c) Looking into the Latte settings.
I see two latte-dock in the repositories.
One in garuda and one in community. I see no repo being used in -Qi, but since garuda is listed above community in the pacman.config, I assume this is used.
Not today, just restore.
I lost transparency often but after next reboot it work, so ask the developer, wait he stop maintaining latte. So wait for KDE developer.
I remember that switching between transparent and opaque didn't work properly on Xorg for me, you can try switching to Wayland to see if things changes.
I've had this same problem for a long time: before using latte-dock-git and after moving to garuda/latte-dock. I tried resetting the config with Garuda Assistant before, and also played a little with the configs: both didn´t help. I reboot every day, and aproximately half the times the top panel transparency works, the other half it won´t.
I had the same issues and it seems to have to do with gpu driver issues.
I solve my driver issues by reinstalling all my driver packages since my blender didn't work as well.
(I need HIP for AMD GPU's on blender).
After I solved all those issues and blender was running properly it also resolved the issue with the transparency which is rooted in the compositor.
Reset the compositor b/c it will turn down features if it recognizes driver issues or driver related issues (which can pseudo-appear due to updates).
Hence: Check your compositor and reset it It solved my transparency issue with Garuda and Docker
All the best,
Bruce
P.S.: I'm currently rendering a short little abstract animation with the Garuda logo
If you mean with "compositor" the setting in KDE, which allows you to switch between OpenGL2, OpenGL3 and XRender: That setting is gone. They removed it a few versions ago
Nope, 1. you need to do a right click on your desktop background 2. and click on screen settings. 3. Choose compositor and then on the bottom of the window
you might get an information box which tells you that the compositor has deactivated some functions b/c it has detected issues. (This also counts if you have tearing issues additionally to transparency issues). But it isn't necessary to restore the compositor as I'll show you now:
Deactivate compositing click apply and then activate compositing and click apply.
You also can check your vsync and scaling methods if you want to. If satisfied click apply and restart.
There is no option about any render API.
Example Window (I use german btw but you might recognize the window anyways by design):
This solved it for me. It seems, it was a driver issue. I guess it would make sense to put a notification about that in the KDE notifications. There is one for lots of pretty minimal cases, why not one for such a significant one. Getting this to KDE bugs, thanks a ton.
I'm pretty happy this worked out for you and I'm super glad I could help!
True, that little information box definitely needs to be in the notifications!
I was annoyed it isn't myself!
Yep getting it to the KDE bugs you'd help a ton of ppl with that issue!