-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capacity bar style is broken #69
Comments
I'm using breeze dark color scheme, the same thing happens with lightly color scheme too. Is there any way I could debug this? |
Hm I'm not sure. Maybe it has something to do with your Plasma/KDE Frameworks version. |
How do I update Plasma and Frameworks? I tried as described here, from the backports repository: |
Even after updating to KDE Frameworks to 5.79.0 and KDE Plasma to 5.21.0, then uninstalling and rebuilding Lightly, the issue persist. |
Same error. Tested on KDE NEON with plasma 5.21, 5.20.5 and on KUBUNTU with Plasma 5.19.5 |
I'll try to reproduce this in a KDE Neon vm. Meanwhile, the Kde people could really change the default look of the KCapacityBar to something more pleasant, it looks so out of place. |
Weirdly this issues is only present on openSUSE Tumbleweed. I have tested on Arch, Kubuntu, Neon, Fedora, KaOS... None of them had this issue. Only openSUSE Tumbleweed. |
Until the issue is fixed, can we as users modify something to make KCapacityBar not look out-of-place? |
@SayanChakroborty Can you try if this package fixes your problem? |
I just tried the package you linked on openSUSE Tumbleweed snapshot 20220409 but the capacity bar is still broken. |
I managed to fix this issue on two of my installs of Kubuntu 21.10. On Ubuntu's repository they are called This is happening because in the cmake file the KF5FrameworkIntegration package is marked as optional. |
Can you try install |
Yes, installing those packages solves the issue. Thank you so much. |
In case someone does not know, as mentioned by Voltstro, installing |
I'm using latest master branch
The text was updated successfully, but these errors were encountered: