[Testing Update] 2022-06-03 - Linux 5.18, Systemd 251, GNOME 42.2, NVIDIA, Mesa, Pulseaudio, Perl

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.

That is neither necessary nor supported.

Yes

But it does not work for evolution 3.44.2-1

Why does it work for me then? Neither theme you mentioned are compatible with GNOME 42.

Are you using unstable branch?

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.

Yes, but that makes no difference as testing and unstable are very close right now.

Again, that theme is not compatible. Use Adwaita-dark or Adw-dark and remove your GTK_THEME environment variable.

Ok, I deleted the solution. But I wonder why the current evolution still supports GTK_THEME?

Did you disable overclocking or turbo feature in BIOS setting?

I tried, but it didn’t matter. Just had to stop watching those files. :joy:

I had to do Zesko’s tip to get amd_pstate working again on kernel 5.18.

1 Like

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 noticed my PC is beeping when I reboot. Just before the computer restarts, when the desktop closes, it beeps once.

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
:exploding_head:

Edit:
https://www.kernel.org/doc/html/v5.18/admin-guide/pm/cpufreq.html#policy-interface-in-sysfs

cpuinfo_cur_freq

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? :laughing:

I guess the driver needs some more development cycles. Maybe useful on 5.19?

acpi-cpufreq is still ok for me, temps are at 30°C (idle state).

I’m not believing any CPU frequency metric the system tells me right now, that’s for sure! :rofl:
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.

courtesy of systemd 251

This fixed it for me
echo “blacklist pcspkr” | sudo tee /etc/modprobe.d/nobeep.conf

Do you have more info? I don’t find any relevant line in the linked changelog above.

I don’t wish to disable the motherboard beeper.

It only disabled the shutdown beep on mine the beep at startup still works with the bios.

I prefer having the beep in case of fan fail warning, temperature reaching certain point, and features like that.

1 Like