Dear KDE developers, I greet you with lots of love and gratitude.
I just discovered a bug. When we change the screen scaling—in my case to 125%—Dolphin’s transparency feature disappears! This is very frustrating because I love the transparency effect! From what I saw on Reddit, this bug has existed for “three years”, three years!
And before discovering this bug, I spent hours trying to install and configure qt5ct, qt6ct! I even tried to install picom. I almost messed up my system—my existing themes, you know! Do you get what I mean??
Could you please help?
Update: I forgot to mention — I’m using Kvantum Manager to make Dolphin transparent, and I’m using the Kvantum-compatible Lavandasea-dark theme.
I didn’t understand what you meant. Other than setting the scale to 100%, there is no solution, is there? It’s almost impossible for there to be a solution anyway, because this is a KDE bug.
This looks like the three-year-old bug may have been in Kvantum (a third party theme thing), not Plasma? It may not be at all relevant today, depending on the distro/Plasma version you use.
You’re right about Kvantum — I was actually editing the topic just before I saw your message. You’re saying the issue might have been caused by Kvantum. If the developers also confirm that the scaling issue is not a KDE bug, then the topic can be closed. I will also post the same issue on Kvantum’s GitHub page.
What I thought that KDE that fails to provide proper transparency, and Kvantum just tries to apply and display it but can’t because of the underlying problem. Because I guess Kvantum only applies the theme; it doesn’t directly provide transparency. If KWin effects aren’t working, transparency won’t be visible either.
Sure, it could be Plasma related as well, since kwin is doing the work that Kvantum tells it to do, so you still might be directed to report this on KDE’s bugzilla if the Kvantum devs think it belongs there. This is a user discussion forum, so bug reports aren’t really visible if they are posted here instead of the official tracker.
Thank you very much. I’ll keep this in mind for next time. But I’m glad I opened it here, because it turns out it wasn’t a bug after all! The issue was just a simple checkbox ticked in Kvantum-manager—can you believe that??
Those interested can read the issue on GitHub:
I’m glad the problem wasn’t related to KDE. In every way, this experience was a valuable lesson!
Long live Linux, long live Free Software, long live FREEDOM!
"I’ve done my best to avoid/circumvent Qt’s bugs in Kvantum. This is only one example.
But if it’s proven that the bug is fixed in Qt, I’ll change the default. The last time I checked, that wasn’t the case: the were rare situations where the bug still showed up."