[Stable Update] 2026-01-04 - Manjaro 26.0, Mesa, Firefox, LibreOffice, COSMIC

Second issue (empty wayland desktop): After I did right click → edit mode → add dock/panel everything was working again. Before it seemed quite broken: right clicl → display settings showed an error of kscreen-backend not avaivable.

First issue (autologin): This couldn’t be changed with sddm or log out to sddm, what needed to be changed was settings → colors → sddm → behaviour → autologin to Plasma (X11)

Thanks so much for a quick reply and the guidance. The updates went just fine and no video, or any other issues. :smiley:

2 Likes

Thanks to @6x12, I was able to switch to the 575 driver, and perform the update without issue.

Since I still didn’t know what the difference between the hybrid-intel vs nvidia drivers was, I decided to play it safe and switch to the 575 variant of the hybrid-intel driver using Manjaro Settings Manager.

To do so, I needed to first fix the misconfiguration inside the mhdw config file by using…

sudo rnano /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-575xx-prime/MHWDCONFIG

…and changing line 3 from…
NAME="video-hybrid-intel-nvidia-prime"
to…
NAME="video-hybrid-intel-nvidia-575xx-prime"

This made the entry for the hybrid-intel 575 driver show up in the Hardware Configuration menu inside the Manjaro Settings Manager, after which…

  1. Right click video-hybrid-intel-nvidia-prime, and select uninstall.
  2. Right click video-hybrid-intel-nvidia-575xx-prime, and select install.
  3. Reboot
  4. Install Manjaro update using pacman -Syu
1 Like

A bit of a mixed bag here. On my laptop (Dell Latitude 5310) things went over smoothly as I was already running Wayland for quite some time.

On my Desktop however (Asus B350 MB with 16Gb memory and a GeForce GTX 1060 6Gb GPU) which was still running Xorg - due to a previous issue with Wayland, Nividia and dual monitor setup - I ended up in a terminal after reboot with no clear way to get my displays up.

Of course the one time I did not read the update notes I panicked and ran through 2 hours of ChatGPT-misguided crapshoots. This sorry excuse for any kind of intelligence, let alone artificial intelligence even made me install a different nvidia driver version and messed up almost all of my desktop configs, one thing I swore years ago I’d never allow myself to do again voluntarily.

In the end I ignored AI and read the notes about the removed X11 session support on Plasma (should have started there from the beginning), set up Wayland, removed all legacy desktop configs and massaged my dual screens back to a recognizable state.

All well that ends well and it’s the first time in many years I’ve had any serious issue TBH so I won’t hold it against anyone.

3 Likes
sudo pacman -S linux612-nvidia-575xx                             ✔ 
resolving dependencies...
searching for conflicting packages...
:: nvidia-575xx-utils-575.64.05-3 and nvidia-utils-580.82.09-1 are in conflict (nvidia-libgl). Remove nvidia-utils? [y/n] y
error: failed to prepare transaction (could not satisfy dependencies)
:: removing nvidia-utils breaks dependency “nvidia-utils=580.82.09” required by lib32-nvidia-utils
:: removing nvidia-utils breaks dependency “nvidia-utils=580.82.09” required by linux612-nvidia

Good instructions, thanks. I had a few other dependencies on linux612-nvidia that needed to be removed and installed anew, and I didn’t have video-nvidia in mhwd so did this instead which I believe is related to laptops with more than one graphics card:

sudo mhwd -r pci video-hybrid-intel-nvidia-prime
sudo mhwd -i pci video-hybrid-intel-nvidia-575xx-prime

I’ve currently got the linux612 kernel with linux612-nvidia-575xx graphics driver - does anyone know whether I’ll need to manually intervene when I next update my kernel, or will it know to automatically install e.g. linux618-nvidia-575xx?

My partner’s Xfce system with GTX 970 GPU now has 575xx legacy drivers installed using pamac:
linux612-nvidia-575xx
nvidia-575xx-settings
nvidia-575xx-utils
lib32-nvidia-575xx-utils
libxnvctrl-575xx

$ inxi -Ga
Graphics:
  Device-1: NVIDIA GM204 [GeForce GTX 970] vendor: Micro-Star MSI
    driver: nvidia v: 575.64.05 alternate: nouveau,nvidia_drm
    non-free: 550-580.xx+ status: current (as of 2025-11; EOL~2026-12-xx)
    arch: Maxwell code: GMxxx process: TSMC 28nm built: 2014-2019 pcie: gen: 1
    speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s ports:
    active: none off: HDMI-A-1 empty: DP-1,DVI-D-1,DVI-I-1 bus-ID: 01:00.0
    chip-ID: 10de:13c2 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.21 compositor: xfwm4 v: 4.20.0 driver:
    X: loaded: nvidia gpu: nvidia,nvidia-nvswitch display-ID: :0.0 screens: 1

  Info: Tools: de: xfce4-display-settings gpu: nvidia-settings,nvidia-smi
    x11: xdpyinfo, xprop, xrandr

A note for anyone who uses Darktable. As of this new release it frequently fails to start properly. Seems to be about one attempt in two that fails and it just hangs.
The (bizarre) cause is having the splash screen disabled. If you can get it to start, you can re-enable the splash screen in the “miscellaneous” section of settings. If you can’t get it to run, edit ~/.config/darktable/darktablerc and change
show_splash_screen=FALSE
to
show_splash_screen=TRUE
There are already bugs raised about this, so the developer is aware.

If you want, you can get rid of the splash screen with a window rule (at least, in KDE). Create a rule to match window title “darktable starting”, with minimised set to “apply initially”.

1 Like

I seem to be having this issue with Gnome:

After this update Loading Steam crashes to Login screen, Has the fix above been added to Manjaro Stable?

The fix will be available with either the next Mutter 49.X release or with GNOME 50 in March.

I was hoping for a quick fix as I’m now looking into any other Distro that do not use Gnome or KDE and still have/will support X-Server/X11 as Wayland is very broken on Nvidia (RTX40XX) and also my old 1st Gen Ryzen 3 with Vega Graphics Laptop.

I have a GTX-1070 and running KDE Plasma with my Manjaro. After updating to nvidia-590 version, I cannot enter desktop. I solved this problem by entering console ui(Ctrl+Alt+F2), then reinstall 575 version:

sudo pacman -S linux612-nvidia-575xx
1 Like

Are you aware of the existence of the Manjaro Xfce Edition, or possibly of the Manjaro Cinnamon Community Edition? Both are using X11.

3 Likes

I also had problems with polkit (not alble to authenticate). I had to run the following to fix the issue (as suggested here):

sudo systemctl stop polkit-agent-helper.socket
sudo systemctl mask polkit-agent-helper.socket
1 Like

Im wondering why 6.18 isn’t marked as LTS Kernel yet.
Do you guys wait till 6.19 become stable and 6.20 shows up as experimental?

I installed plasma-x11-session to restore X11 under KDE… that should work till atleast early 2027.

But if you want longer support then XFCE should be there for X11 support till 2032 if i remember correctly.

1 Like

I suppose because it’s not LTS oficially yet.

Strange, because on this page it shows 6.18 as LTS:

1 Like

It will be marked in the settings after the first stable release of 6.19. Not officially but in manjaro. So for the stable update that means on the next update cycle next month.

3 Likes

In fact, kernel 6.18 (LTS) was officially released on 2025-11-30. This type of question arises from time to time when an LTS kernel isn’t displayed as such in the Manjaro Settings Manager (MSM).

MSM typically isn’t updated to coincide with the release of a new LTS kernel and it can take a while for the “LTS” description to be updated in MSM.

Remember that Manjaro doesn’t dictate when a kernel (LTS or otherwise) will be released (or when it might reach EOL).

The status of any kernel can be easily found:

https://endoflife.date/linux

1 Like

If you install new kernels through “Manjaro settings manager > Kernel”, I believe it installs the drivers stuff too. I just tried installing Kernel 6.18 and the pop-up says this:

The following packages will be installed:
linux618
linux618-nvidia-575xx

edit: Yep, I just installed the 6.18 kernel that way and everything is working fine driver-wise after rebooting and switching kernel.

2 Likes