I have two (possibly related?) issues that seem to have cropped up with the new update.
The new kernel somehow bricks my ethernet port, rolling back to 6.8 fixes it. Not sure if this is a Manjaro issue or a kernel issue.
The kernel management GUI application seems to have entirely disappeared from my system, and I haven’t been able to figure out if that has to do with problem #1 or not. I’m still able to handle it from the command line just fine, so it seems the main app is working fine, but the GUI app is gone and I’m not sure if that’s intentional.
EDIT:
I have found solutions to both issues (in reverse order) -
As @cscs pointed out, the GUI application for kernel management is no longer searchable via the “Start” menu, nor is it available in the main System Settings, application, it resides exclusively in the Manjaro Settings Manager.
The linux69-r8168 kernel module was somehow not included in the update, bricking my Ethernet connection. Rolling back the kernel version, installing this kernel module manually, and then rebooting with the new kernel solves the issue.
It really astounds me this is a recurring topic.
(though I suppose to be fair it doesnt pop up from, ex, searching ‘kernel’ in kickoff)
Manjaro Settings Manager is the place for those things.
Its the GUI frontend for mhwd and mwd-kernel etc.
Somewhat recently, and until the plasma 6 update, a ‘kcm’ was added for the kernel part.
KCM’s are like plugins for systemsettings in plasma.
Well with plasma 6, systemsettings is changed, and so the MSM kcm is not present.
Just open Manjaro Settings Manager like every other desktop does.
It would take a lot more typing than I am willing.
Pretty much its poorly coded, requires extra hacky workarounds (like augmenting your DIsplay Manager, as already noted), and there are quite simply superior alternatives.
I personally dont see much use for those utilities in general outside of rather specific setups.
But if you really need one … no reason to use the worst version.
I don’t quite understand what that exactly means. If I use linux61, do I must switch to linux66 or something, or this information for me to actually ignore the linux-firmware update? Or I can do nothing?
p.s. my info command tells I am currently at 20240220.97b693d2-1 version
I’m now finding that Krusader lost its ability to use protocols like SMB. I do have the required kio-extras installed. It looks like through a web of dependencies kio5 and kio5-extras are still being required so both the newer kio/kio-extras and kio5/kio5-extras are installed.
Krusader is 2.8.1-1.
I was able to update in a term in a gnome session without any problem.
Gnome Boxes was not working before (unable to install on virtual disk), now, it is, yeah!
I could install Manjaro kde 23.1 and upgrade it to 24. No problem with this fresh installed system in Boxes.
I’m also at version 20240220.97b693d2-1 and on linux61 since my fresh install in Feburary of last year. I’ve always applied all updates up to this point (meaning pre 24.0) but ‘linux-firmware’ doesn’t seem to have been updated.
What’s the next step then? Will ‘linux-firmware’ be updated to version 20240409.1addd7dc-1.1 when running the 24.0 update or is some intervention needed before that?
I see 20240409.1addd7dc-1.1 being listed as an update in the Pamac Updates indicator. So do I get it right that it will be updated with 24.0 then (which I haven’t done yet)?
Sice the update I find the package microsoft-office-web-jak installed under foreign packages.
I can`t remember installing it and it is also not in AUR…
What is this package for? Do I still need it?
There is not really a “24.0 update” for running systems.
Manjaro is a rolling release.
Those numbers are for ISO’s.
As long as your mirror is synced you will get all the updates at the same time whenever you … do your updates.
I very much need it for building FreeCAD (citation: Compile on Linux - FreeCAD Documentation) and I would appreciate your not responding with uninformed speculation about what others “actually need”.
For anyone having the same problem with this update, these were my steps to resolve it:
After I uninstalled shiboken2, pacman -Syu was able to download and complete normally, and it reboots normally after that.
Now trying to run FreeCAD causes errors about missing libraries, so it needs to be rebuilt. As an experiment, I tried rebuilding FreeCAD without shiboken2. FreeCAD built properly but on running it, it gave some 6 to 8 errors about missing PySide2 functions and could not open my CAD files, so you can save some 20 minutes by not attempting this step. Instead, after rebooting, go to the next step directly.
Reinstalling shiboken2 is possible after the update because its recipe too has been upgraded to require Clang 17. I used the Pamac GUI for this. It takes a very long time (35 minutes) to build it along with pyside2; ironically, it uses GCC while building and not Clang, which had been the reason for this whole adventure. But when finally built, FreeCAD can be built and run properly.
