Open RobQuistNL opened 3 months ago
have you tried following the instructions in the README? i did to no success, going to try reinstalling from ubuntuunity.org next
I did make it work on GTK 3.0 when it came over GTK 2.0 last time round. But now it happens again for going from GTK 3.0 to 4.0. So blame those stupid GTK maintainers for making their stupid 'production' so stupid in legacy compatibility. FYI, I am using my indicator-cpufreq
right now everyday because my MX-Linux (Debian Bullseye) is still on GTK 3.0.
Hi Wang, thanks for taking the time to reply- and yes, i will blame gtk based on my experiences as well.
https://github.com/xuancong84/indicator-cpufreq/commit/315af22216cc0ed19c586e20c2e6120c2efc1333 fixes it, I had the same issue with version from Ubuntu 22.04 repos and I just patched it accordingly
Thanks, @nazar-pc for the patch. Strangely speaking, even without patching, it works out right away on my Ubuntu 22.04 with KDE plasma desktop environment. Maybe Gnome uses a higher version GTK?
I'm using a custom DE, but with Gnome components and I do have GTK4 installed. Not sure if that is the default though, I did some development with GTK4 and might have installed something that would not be shipped out of the box, but since those can be pulled by some dependencies, I'd expect many users to be affected.
P.S. I should thank you, that is the latest commit in this repo :slightly_smiling_face:
See https://answers.launchpad.net/ubuntu/+question/327554