FYI: I’m running a Core5 2nd generation(2011) with kernel 6.18
@philm the link is broken. It is showing 404 not found :).
Maybe you or someone can correct/fix it.
Thanks!
Since the wiki software got renewed the links won’t work. the new one is: System Maintenance - Manjaro
2 Likes
One still needs to compile and distribute so in practical terms the eol date may come sooner, see [Unstable Update] May 2026 - #24 by philm
4 posts were merged into an existing topic: Cannot boot after Stable 2026-05-27 update
Discord didn’t start after the update. A combination of re-installing re-starting helped. I wonder if it’s related to Can't launch Discord (1.0.137 | CachyOS) · Issue #633 · flathub/com.discordapp.Discord · GitHub
(which I had on a different device - on Manjaro, I installed the discord package directly from the Manjaro sources)
Discord is known to force specific versions and cause trouble on occasions.
You best bet is to use their flatpak version.
flatpak install flathub com.discordapp.Discord
1 Like
You can set discord to skip the forced update:
1 Like
Exact same issue here, with two applications: MS Edge and Discord.
fc-cache -f
says it succeeded (with the --verbose flag), but it does not change behavior, even after reboot. I tested some kernels, 6.18, 7.0, 7.1 - issue persists.
maybe some info on my system here:
fabitanker@FaTa-T420
--------------------
OS: Manjaro Linux x86_64
Host: 4236Y1W (ThinkPad T420)
Kernel: Linux 7.1.0-rc5-1-MANJARO
Uptime: 25 mins
Packages: 1711 (pacman)[stable]
Shell: bash 5.3.9
Display (AUO313C): 1366x768 in 14", 60 Hz
WM: i3 4.25.1 (X11)
Theme: KvAdaptaMaiaDark [Qt], Adapta-Nokto-Eta-Maia [GTK2/3]
Icons: Papirus-Adapta-Nokto-Maia [Qt], Papirus-Adapta-Nokto-Maia [GTK2/3]
Font: Noto Sans (10pt) [GTK2/3]
Cursor: --help
Terminal: rxvt-unicode 9.31
CPU: Intel(R) Core(TM) i5-2520M (4) @ 3.20 GHz
GPU: Intel 2nd Generation Core Processor Family Integrated Graphics Controller @ 1.30 GHz [Integrated]
Memory: 5.28 GiB / 11.46 GiB (46%)
Swap: 0 B / 12.00 GiB (0%)
Disk (/): 71.36 GiB / 233.67 GiB (31%) - ext4
Disk (/mnt/ext): 177.26 GiB / 292.35 GiB (61%) - ext4
Local IP (enp0s25): 10.44.1.106/24
Battery (42T4763): 62% [AC Connected, Charging]
Locale: en_US.UTF-8
I believe the problem has something to do with graphics acceleration (GPU) in Intel drivers. I use an Electron-based application (a cursor based on VSCode) that started displaying correctly when I started it with the --disable-gpu parameter.
The wallpaper on my desktop has vertical lines and the window titles look strange in some applications that don’t use native GNOME rendering (like Cursor).
1 Like
Thanks for the update, guys! No issues here.
2 Likes
Strange - because I no issues with these browsers.
I have Lenovo Legion with Intel/Nvidia in hybrid mode.
I use it to test stable branch - no issues.
I will test stable branch on an old Clevo machine with Intel only.
This seems to point to an issue specific to your hardware - making it extremely difficult to diagnose.
Yes - this is a known issue if the module is not loaded at the time you run the script.
I suggest you remove the generated list - connect to your vpn and run the script with the desktop profile.
You may also reference the forum guide for modulejail
When the effort required to back-port and compile kernels with mitigations for various new vulnerabilities becomes a burden - then old hardware becomes an annoyance.
Manjaro is suffering from lack of manpower so when something becomes a burden rather than fun - it will be ditched - you know that from your personal life - right?
Many users expect that when vulnerabilities are exposed they are also patched but this may not always be an option.
Even old hardware can run on the latest kernel - there is really no reason to stay behind.
So the general recommendation is to use the latest LTS Linux 6.18 (2026-05-28T22:00:00Z).
2 Likes
Gnome extensions were disabled by default - had to enable them.
I’ve tried to troubleshoot myself out of this by going to other branches, but it seems right now they aren’t futuristic enough to solve the problem.
Trying Intel-only configuration is a step into right direction, but it maybe much too broad measure anyway, since this doesn’t even consistently affects computers from one era.
I’ve got 3 computers running Manjaro in my house which are:
Dell Optiplex 390 (HD Graphics 2000 (SNB GT1)
Dell Optiplex 780 (listed in system info as Unknown)
Lenovo IdeaPad U330 Touch (HD Graphics 4400 (HSW GT2)
All running on Intel’s integrated GPUs, mostly from same time, but only first computer in my humble sample is being affected by this, the rest are doing just fine with this update. I could switch SSDs between them and that would transfer the issue between them, since this display corruption isn’t caused by broken system files, filthy font caches. If that would be the case, USB-Manjaro stick for Lenovo would probably misbehave after putting it in problematic machine. But no, it glitches only on this one computer.
So, I guess to solve it, we need to be more specific, which Intel configurations are prone to this.
1 Like
I did have an issue after this update: my wifi broke. After doing some basic common troubleshooting such as restarting NetworkManager, I had to do some research on what to do next.
I checked dmesg and it turns out that somewhere, the firmware related to the wireless adapter was corrupted at some point during the update. I did notice that, during the removal of AUR packages prior to the update, one linux-firmware-meta package was listed as an alien package. It didn’t stop my uninstallation of AUR packages and didn’t give me any warning messages that I saw, so I didn’t think anything was wrong until I rebooted and couldn’t get online.
Anyways, to fix the issue, I had to find an alternate method of connecting to the internet. I used USB tethering on my phone but ethernet works fine for this purpose. Once I did, first, I ran an update on the firmware:
sudo pacman -Syu linux-firmware
Next, I reloaded the drivers using modprobe:
sudo modprobe -r [driver name]
sudo modprobe [driver name]
Then, I restarted NetworkManager:
sudo systemctl restart NetworkManager
After I did all of those, the wifi returned. I rebooted and things worked fine as if nothing ever happened. Not sure exactly what went wrong or where it went wrong, but things are working just fine now. I’m back up and running as normal!
2 Likes
Which is why I prefer to remove foreign packages after, not before, an update:
6 Likes
Gotcha, thanks for the context. I only remove them before because that’s what the best practices post recommends. I generally follow that to the letter before every update. I might stop doing so if the community thinks after is a better idea, though!
EDIT: Ah man, didn’t realize you already told me this. I feel pretty dumb now haha
2 Likes
Regarding this display problem, I downgraded Mesa from version 1:26.1.1-2 to 1:26.0.6-1 using the command:
sudo manjaro-downgrade mesa
(If the manjaro-downgrade command is not installed, use sudo pacman -Syu manjaro-downgrade first).
The problem was resolved until a version that fixes the problem is released.
7 Likes
You should always remove your orphans after updating everything, i.e. the repo packages and the AUR packages — Snaps, FlatPaks and AppImages are containerized packages, so they’re irrelevant in this regard.
If you remove your orphans after updating, then you don’t have to worry about them anymore when performing your next update. If you remove them before updating, then you’ll have loads of unused junk on your system every time until you update again, and then those orphans may get updated as well, just because you have them installed.
4 Likes