[Stable Update] 2023-07-27 - Kernels, Nvidia, Virtualbox, Thunderbird, LibreOffice, Pipewire

oh, ok then.

I am even more embarrassed now. Tons of pacnew files did build up. Unbelievable that I never thought of that. Senior SWE, using Linux for more than 20 years. This is probably my biggest embarrassment yet.

Going to be fun when I get back from holiday and merge all my pacnew files on ubuntu.


There’s a first time for everything. :wink:


my font size have become smaller everywhere (KDE) also applications like Chromium, Firefox
… missing fonts?
any idea?

Operating System: Manjaro Linux
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Kernel Version: 6.4.6-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-6700 CPU @ 3.40GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 530
Manufacturer: Dell Inc.
Product Name: OptiPlex 7040

th ISO builds are failing on github

1 Like

4 posts were split to a new topic: I’ve updated to 6.4.21 and my system still reports ZenBleed

A post was merged into an existing topic: I’ve updated to 6.1.41 and my system still reports ZenBleed

Well, Microsoft reduced disk space on their VMs … However there are hacks available.

1 Like

Apparently kernel 6.1.41-1 is still affected by this issue below… :arrow_down:

I don’t think it would be an actual CPU load of 100% on that particular core, though, because if that were the case, then the temperature readout for that particular core would be a lot higher than can be seen in the second screenshot here-above.

On my system, that particular core always runs just a tad hotter than the other cores anyway, but its current temperature readout of 36°C is not consistent with a core that’s genuinely stuck at 100% — in that case, the temperature readout would probably be somewhere in the 40-50°C range.

So whatever’s causing this apparent 100% load is most likely a bug in the kernel code reporting the core temperatures, and according to the 2023-07-25 Testing update thread, the issue was apparently fixed in 6.4.6. I guess no one thought of backporting it to 6.1 as well. :frowning_face:

Oh, and on account of mariadb being the cause — which I doubt, although it may be the trigger — replacing it by postgresql is not an option here because I’m running Plasma, and akonadi requires mariadb. I don’t know whether it would be possible to replace mariadb by mysql proper — I’ll have to investigate that — but mysql is an AUR package, and I would rather not replace an essential component for my desktop environment by an AUR package.


pacnew (and pacsave, etc) are a product of ALPM (pacman, pamac, etc) … you wont have them on Ubuntu. But then you cant roll the same Ubuntu install for years and years. Frozen vs Rolling.
(and a care to preserve user configurations)
So a bit of consolation maybe :slight_smile:

Its triggered by akonadi (used by Kalendar) … but mariadb is the culprit.

The kernel is doing what it should … reporting had changed slightly.
That said a proposed kernel patch circumvents the issue by narrowing the reports and squashing another unrelated bug.

1 Like

It is not fixed in 6.4.6. The Arch Linux Bug Report mentions a LKML thread (without a link) that suggests it is not a Kernel error. However, there is a patch that fixes the problem inside the kernel. The patch comment suggest the high iowait is just a cosmetic issue.

The patch is at the moment not merged, so it is also not backported to any version.

1 Like

If there is a patch that fixes it inside the kernel — and I already knew about this :wink: — then it is a kernel issue. :stuck_out_tongue:

Yes, that much is true, as I said in my previous post. If it were a genuine 100% load, then the temperature readout for that particular CPU core would be a lot higher, as would the total temperature be for the entire processor chip. :wink:

Still, cosmetic or not, it’s annoying. :stuck_out_tongue_closed_eyes:

Nvidia Flickering issue also still exist with the newest nvidia driver version on Turing and Pascal GPU’s, related to high refresh TFT’s.

1 Like

Will the CPU peaks affect the 6.1.38-1 kernel?

We’ve skipped 6.1.38 in Stable, but yes, that was was where the problem was introduced in Unstable and Testing.

The NVIDIA update solved some issues for me.

The one thing that didn’t work after the update was my xbox controller. It still connected to bluetooth but it no longer rumbled on connect, and it was no longer recognized by any Steam games.

I simply rebuilt xpadneo-dkms, restarted, and its working again.

Yeah, it is just cosmetic but as Linus once said (very loudly and with a lot of swearing)

If a change results in user programs breaking, it’s a bug in the kernel. We never EVER blame the user programs.

1 Like

I have a strange bug with hanging keystokes after a few hours uptime. I think it started with the 10.7.23 or 17.7.23 update.

All applications seem to open the search bar searching for tabs in a loop and meta key is not working anymore. Nothing special to see in journalctl. The only thing that helps is a reboot.

I see a new error in journal after this update:

kernel: ucsi_ccg 0-0008: failed to get FW build information