if you read through pacman.log and have mariadb installed, you’ll notice the following TODO:
# systemctl restart mariadb.service && mariadb-upgrade -u root -p
With the addition of 5.18 and 5.19-rc1, have the recommended kernels updated as well? The app under settings manager still lists 5.15, 5.10, 5.4, and 4.19 as the recommended kernels (currently running 5.15 myself).
The recent update made my machine unbelievably LOUD. It used to be whisper quiet under moderate load, now fans are running full throttle in the same situation. The noise is unbearable. I’d be grateful for any suggestions on how to fix this. My machine has an X570 AORUS ELITE (rev. 1.0) with an Ryzen 7 (Pinnacle Ridge).
The only problem I’ve seen so far is that some Perl modules I installed from CPAN (I think, using compiled C code though I haven’t dug into it yet) come up with “undefined symbol” errors.
The fix seems to be to re-install them. There’s probably a way to identify them without waiting for Perl scripts to fail, but I don’t know what that would be.
Probably something like: pacman -Qoq /usr/share/perl5
amd_pstate error
To confirm: ignoring the error worked here, too, at least on kernel 5.18.3. Back on amd_pstate now. Far, far too lazy to try other kernels right now.
Seeing 590Mhz on cores again is a bit of a relief.
Hmmm… I suspect not. That returns a long list of packages, at least some of which were updated today. And others which were installed from AUR and haven’t been touched for some time (but still work).
I can’t see it helping with modules installed from CPAN either. But thanks for the suggestion.
Ah, never mind. I thought you were looking for packages depending on perl.
Thanks for finding that fix! 
Why would they? I think it would require extraordinary circumstances for a non-LTS kernel to get the “recommended” label.
I see, then it’s my own lack of knowledge about kernel designations.
After this update the below message shows on tty at KDE GUI Shut Down (the word poweroff is replaced by reboot on Restart) when clicking the button in the KDE Application Launcher.
I did some research and I believe this is caused by the updated systemd issuing commands to poweroff and reboot without the --no-wall argument (a new requirement?). Is there a way to correct locally or would it need to be patched upstream?
I do not get the beep from the pc speaker that others are reporting, maybe because I am on a laptop.
^@^@^@
Broadcast message from xxx@xxx-pc (day date time):The system is going down for poweroff NOW!
_
Kernel missing, please load the kernel first
same here
Cannot boot Manjaro anymore. I’m not linux expert so… Please help!
How do I restore kernels or I how can I restore from Timeshift?
Timeshift made a backup before upgrade.
I fixed it myself. I booted from Manjaro Live USB.
I run Timeshift. It found the last backup before upgrade!!! So I was able to restore it to previews fully working state.
Manjaro and Timeshift are great! So I boot up my system again without the update.
I had done the last update with pacman -Syuu.
This time I made the update with pamac-manager. Update worked ok.
I don’t know why it replaced kernel real time 5.17rt for 5.18rt. It didn’t upgrade 5.17 normal to 5.18.
I’ll try to manually install normal 5.18 kernel with pamac-manager.
Two more broken items:
After the update, ffmpeg4.4 came up as an orphan, and I don’t know why. I know Audacity needs this because without it an error message pops up at the start of Audcity. (This may not happen to everyone. I typically go beyond the norm with Audacity)
- Easy fix, just reinstall ffmpeg4.4.
Gnome-Boxes is now unusable. Any virtual systems created before the update still work fine, but now it will not boot and create a new virtual system. I downloaded and tried 4 different Linux distros. No luck.
I have Manjaro Xfce on another desktop that never had Gnome Boxes installed, so, I installed it just to see what would happen. Same result on a fresh install…It will not boot/create a new virtual box.
after login my desktop stuck at splash screen. here is my journald log
I am waiting to update, but wow, so many broken itens…
I think I will wait a little more… ¯_ (ツ)_/¯
Any news about VirtualBox?
It’s the only thing that I am really concerned in this update
2 Likes
From what I’ve read, the VirtualBox instability issues are due to a kernel regression:
3 Likes
I am using 5.15 LTS and saw some problems with that too… Any way to fix, or it’s better wait?
1 Like
I am temporarily using an earlier version of the 5.15 kernel and VirtualBox kernel modules to avoid the instability issues. If you are not comfortable downgrading or holding packages, it might be better to wait until a patched kernel is released :).
Does anyone know which kernel versions have fixes for the regressions?
1 Like