Sure it does. Use a compatible theme like Adw-dark. Also install the Legacy (GTK3) Theme Scheme Auto Switcher (gnome-shell-extension-legacy-theme-auto-switcher) GNOME Shell Extension and both Libadwaita and legacy applications will automatically switch themes.
I can reproduce this issue in testing branch: Use gnome-shell-extension-legacy-theme-auto-switcher and try to switch the dark theme Matcha-dark-aliz or other dark theme. But it shows white theme in evolution except other apps.
but the old version of evolution 3.44.1-1 has no issue.
Fps in minecraft dropped twice after update, also got some graphical bugs, reverting to stable fixed the problem, maybe some issue with graphical drivers
I’m at a bit of a loss which CPU frequency metric is accurate, if any… /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq shows all cores being at 2.9 GHz or above, whether I have an active watch or just reading the text files at a single point in time. htop gives similar results as watch -n1 grep "MHz" /proc/cpuinfo, but if I start running watch -n1 cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq, htop starts to show nearly identical results to it in about a minute instead, while /proc/cpuinfo stays the same
Current frequency of the CPUs belonging to this policy as obtained from the hardware (in KHz).
This is expected to be the frequency the hardware actually runs at. If that frequency cannot be determined, this attribute should not be present.
Yup, I don’t have this option for my 5600X. So it’s guesswork, I guess?
I’m not believing any CPU frequency metric the system tells me right now, that’s for sure!
My temps and power consumption at idle dropped a bit, a few degrees and 150-200 mV, respectively, with this new driver. Nothing really major or even meaningful, but I’ll take it.