I have a Que - Do kernels auto update when the series reach EOL to next LTS kernel?
I see that text at every Stable update announcement post, and this time I looked a little further into it, saw that I was on 6.12 series kernel but did notice changes between updates to that ‘xx’ in 6.12.xx-manjaro (64 bit) meaning minor updates…
So I just installed 6.18 LTS Series so that I don’t forget about it at 6.12 EOL.
My current kernel is - 6.18.18-1-MANJARO (64 bit) (I did not remove 6.12)
But I wanna know about this more and why its doesn’t by default update to latest LTS.
When I boot from manjaro-kde-26.0.4-minimal-260327-linux618.iso I choose tz=Europe/Copenhagen and keytable=dk and leave lang=en_US, but when I reach the live desktop and open konsole the keyboard is not what I chose, and locale is en_US.
Have issues with the NetworkManager 1.56 update. Can not open websites. Pings with IP addresses are possible. Obviously a DNS problem. Going back too 1.54.3-1 solves the problem.
The kernels that go EOL will get updated if the user does nothing and disregards the notifications that newer kernels are available. (if I read this wrong, please correct me)
Yes and no. The linux-lts-meta package will only upgrade to the next oldest LTS kernel still in the repo.
So if you’re still running 5.15 LTS and 5.15 goes EOL in December 2026, then it will install — if you don’t have it already — 6.1 LTS, which goes EOL in December 2027. But it will not install any later LTS kernel, let alone the newest one.
It does for me, but I was not the one with the issue — I keep my panels locked.
I have 6.5 three computers. The Lenovo my partner now uses, the old Dell, and the Starlite Tablet.
I have 6.6.3 on my Slimbook, running testing.
All seem pretty stable. I guess there will be issues, but I have not noticed any.
The upgrade, on the Slimbook was uneventful. I am also running the 7.0 kernel on the Slimbook.
Everything seems pretty stable. Other than the Sliimbook not sleeping, last night. But I have had that happen before, multiple times, over the years, probably because I have too many Applications loaded. So I never worry about it.
Most likely not but our current stable release of Manjaro 26.0 is focusing on the Plasma 6.6 and GNOME 49 series. Since we have Manjaro also on several computers in a department of one of our commercial customers, we simply can’t rush any DE updates without consulting them on possible update issues. People who want to have newer packages can simply switch to our testing branch and help out on reporting issues they may find there.
The one I noticed (after responding to a bug) was that panel items were stuck on 6.5.6, and in edit mode, you couldn’t get the context menu to show up or move them… hardly a deal-breaker.
That just disappeared moving from 6.5 to 6.6.3 - otherwise there’s nothing that I can spot for the moment.
No, it doesn’t. But at least for my part this doesn’t have any priority. I don’t need to modify my panel. I was told about this bug by other user and I only confirmed it and asked about this issue here as I have found nothing about it anywhere.
The user that informed me about this has change to unstable in the meantime.
You could just go to testing, it just cleared up for me, or simply have a go at editing the file yourself… not like you need to move stuff all that often.
Hi, I’m running Manjaro KDE plasma Wayland on an Intel Lunar Lake laptop with CPU: Intel Core Ultra 7 258V, iGPU: Intel Arc Graphics 130V / 140V.
The last update seems to have broken hardware acceleration (in firefox at least). And also the overall GPU usage : didn’t get used by supertuxkart anymore (nvtop and KDE showed 0% GPU usage and CPU spiked really bad, fps was low).
Rolling back to 26.0.3 with timeshift solved the issue, I don’t know precisely which package caused the issue… I am curious tho because I don’t wand to end up doing too much partial upgrades…
Hard to tell… but two areas to look first might be:
kernel - you never mentioned what kernel you’re using… but if Intel drivers are like AMD (baked into the kernel) then swapping/updating/downgrading kernels could provide some insight
mesa - could try downgrading it as a troubleshooting step if kernel swapping doesn’t yield any fruit.
Note: the output of vulkaninfo --summary may highlight something