X server fails to start after 2026/02/13 update

Hello,

xlibre fails to start after I updated this morning. Didn’t see the notice in time.

I cannot start X client applications from a VT, either. Trying results in a “no X server or specified display” message.

OpenMandriva Lx version:

OpenMandriva Lx release 26.02 (ROME) Rolling for x64_64

Desktop environment (KDE, LXQT…):
XFCE

Description of the issue (screenshots if relevant):
X server fails to start. fpaste is attached. Let me know if you need more.

Relevant informations (hardware involved, software version, logs or output…):

fpaste.txt (34.8 KB)

First, welcome and thank you for making a post.

The pertinent part appears to be this:

* Xorg errors (grep '^\[.*(EE)' /var/log/Xorg.0.log ~/.local/share/xorg/Xorg.0.log | cut -d ':' -f 2- ):
     [2026-02-13 18:14:38] (EE) AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC0. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC1. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC2. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC3. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(G0): Failed to initialize color management property DEGAMMA_LUT on CRTC0. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(G0): Failed to initialize color management property DEGAMMA_LUT on CRTC1. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(G0): Failed to initialize color management property DEGAMMA_LUT on CRTC2. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) AMDGPU(G0): Failed to initialize color management property DEGAMMA_LUT on CRTC3. Property value may not reflect actual hardware state.
     [2026-02-13 18:14:38] (EE) modeset(G1): drmSetMaster failed: Device or resource busy
     [2026-02-13 18:14:39] (EE) Server terminated with error (1). Closing log file.

Check that the following is installed:

dnf list x11-driver-video-amdgpu

If not, please install it and reboot.

Installed packages
x11-driver-video-amdgpu.x86_64 25.1.0-1 rolling-x86_64

Package was already installed, so that’s not it.

@NiveusLuna
welcome1

Thanks for the clarification. It sounds like the install was aborted via doing the upgrade while xorg was running. We do have some guidance to repair that in some of the pinned topics. You could try:

sudo dnf reinstall xlibre*

Otherwise, @bero knows how to possibly repair it without having to reinstall. It’s up to you how you would like to best spend your time on this.

The X server remained running during the update. There was rather more output than usual, but I wasn’t able to read it before it ran off the screen. I had no idea there was an issue until I rebooted.

reinstalling xlibre as prescribed has not fixed the issue.

Tomorrow morning, I think, I’ll reinstall from my previous XFCE ISO and update. It’s 8 PM and I don’t need this machine until Monday. I’ll post here whether it breaks or not.

1 Like

Keep us posted.

I don’t think you can use rollback, but you might be able to get a list of what it tried to update and see if they succeeded:

dnf history --help

Reinstalled, ran dnf distro-sync –-allowerasing. It removed xfce4-session and xfdesktop because of broken xapp dependencies. Apparently xapp still needs python 3.11 as currently packaged. Disabling the -testing repos allowed installation of older packages that were not dependent on xapp. Not sure why they were enabled to start with; must be an XFCE spin thing.

X server still won’t start. Starting manually via startx still fails. Same log output.

I can log into GNOME now, so whatever is happening is specifically an xlibre issue.

I was able to do a dsync on my older notebook with ROME and could not reproduce the issue. The difference is probably that I did the dsync in a VT and not logged into Plasma.

During the dsync, xlibre, systemd, and possibly sddm were updated. Since using a GUI terminal to update may result in some programs terminating, the problem is most likely related to one or all of the mentioned programs stopping and terminating the dnf process.

As a general rule (for any distro release upgrade) it’s best to:

  • Backup
  • Do the upgrade in the TUI
  • Confirm there were no errors via any logs created from your update command
  • Reboot and verify

Could we communicate this better? Probably, but it may still get missed.

Forgot to mention: After the reinstall, I ran the distro-sync from a tty in console mode. X was not running.

would the errors be stored in DNF history, or would I need to pipe STDERR into a file for that?

This will probably be the best method. Otherwise it may be in the location for dnf5 logs.

A fresh install from today’s XFCE spin build works. I’m choosing not to question it.

This means the issue was something in the upgrade process. But I need this machine working, so I’m not going to try to isolate it further.

1 Like

I understand. Please mark as Solution, then.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.