"drmSetMaster failed: Device or resource busy" after updating from 2:25.1.6-1 to 2:25.2.1-1

[ChekeredList71]

Describe your issue

Hello,

yesterday, I updated my packages on my Linux Mint system. According to apt history log, XLibre packages has gotten updated: apt history

Today, when I booted my PC, it hanged on this:

[2026-07-18 19:17:17] (EE) modeset(1): drmSetMaster failed: Device or resource busy
[2026-07-18 19:17:17] 
Fatal server error:
[2026-07-18 19:17:17] AddScreen/ScreenInit failed for driver 1
[2026-07-18 19:17:17] 
[2026-07-18 19:17:17] 
Please consult the XLibre support: https://www.xlibre.net/
[2026-07-18 19:17:17] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[2026-07-18 19:17:17] 
[2026-07-18 19:17:17] (EE) Server terminated with error (1). Closing log file.

Full XLibre log

What I know for sure, is that XLibre broke after I upgraded apt and flatpak packages yesterday. I didn't do any tinkering on my PC. I just booted it yesterday to use Libreoffice Calc. Then I upgraded and shut my PC down.

Troubleshooting I did:

1. booting one version older kernel, I had in GRUB
2. checking if something already took control of my /dev/dri: sudo lsof /dev/dri/* - empty output
3. sudo journalctl -b -u sddm - only the error from XLibre appeared
4. looking for broken packages: sudo dpkg --audit - nothing
5. reinstalling xlibre packages
6. manual startx - same error as in the log above
7. switching to old XOrg - it works
8. removing the contents of /etc/X11/xorg.conf.d/ (though my only custom config was enabling TearFree)- it works with old X, same error with XLibre

Steps to reproduce

Unfortunately, I can't figure that out. XLibre just doesn't work after an update.

What I know for sure, is that XLibre broke after I updated yesterday. No issues before.

What did you expect?

XLibre to start as usual

Additional Information

• non-working XLibre ver. (extracted from APT history, so not sure if this is the correct): 2:25.2.1-1
• working XLibre ver. (extracted from APT history, so not sure if this is the correct): 2:25.1.6-1
• glxinfo -B (on old X):

name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: AMD (0x1002)
    Device: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 20.1.2, DRM 3.57, 6.8.0-136-generic) (0x73df)
    Version: 25.2.8
    Accelerated: yes
    Video memory: 12288MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 10943 MB, largest block: 10943 MB
    VBO free aux. memory - total: 7702 MB, largest block: 7702 MB
    Texture free memory - total: 10943 MB, largest block: 10943 MB
    Texture free aux. memory - total: 7702 MB, largest block: 7702 MB
    Renderbuffer free memory - total: 10943 MB, largest block: 10943 MB
    Renderbuffer free aux. memory - total: 7702 MB, largest block: 7702 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 12288 MB
    Total available memory: 20244 MB
    Currently available dedicated video memory: 10943 MB
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 20.1.2, DRM 3.57, 6.8.0-136-generic)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 25.2.8-0ubuntu0.24.04.2
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 25.2.8-0ubuntu0.24.04.2
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 25.2.8-0ubuntu0.24.04.2
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

• uname -r: 6.8.0-136-generic (Linux Mint 22.3)
• DE: KDE Plasma 5.27.12

Extra fields

• I have checked the existing issues
• I have read the Contributing Guidelines
• I'd like to work on this issue

[NexusSfan]

Disable modesetting if you already have the AMD driver enabled

[ChekeredList71]

Disable modesetting

I've tried searching how to do that in XLibre, but I couldn't find much.

Only the LLM resutlt summariser of Brave search came up with a generic response, that included this part:

XLibre Compatibility: XLibre is a fork of the X server that often includes experimental features like TearFree for the modesetting driver. Disabling modesetting means you lose access to these XLibre-specific optimizations.

Is this true? I prefer to not lose TearFree, though I don't really trust these summarisers. Also, what is the method of doing this?

if you already have the AMD driver enabled

I don't understand this part. Yes, I have the drivers enabled, otherwise I wouldn't see GPU output. Do you mean if I use the proprietary amdgpu-pro drivers? I have mesa.

Could you lead me in the right direction? I mainly use Linux for GPU-less servers, I'm not well versed in GUI-land.

[NexusSfan]

I've tried searching how to do that in XLibre, but I couldn't find much.

Try rename /usr/lib64/xorg/modules/drivers/modesetting_drv.so to /usr/lib64/xorg/modules/drivers/modesetting_drv.so.off

Is this true?

Probably not, if you want to enable TearFree just use Option "TearFree" "true" in your amdgpu.conf in xorg.conf.d

[fish4terrisa-MSDSM]

Huh this is weird why is amdgpu and modesetting both detecting and trying to load the same gpu here? Even with amdgpu enabled the user shouldnt be required to disable modesetting in a hacky way.
What's ur setup? Do u have an amd igpu and an amd dgpu or something?
That being said, is modesetting broken on ur gpu or something? Usually I'd recommand using modesetting instead of amdgpu if modesetting works fine on ur setup.
U can specify the driver to use and disable automatic gpu detection in Xorg.conf as a workaround.

[filipe-maia]

I'm having the same problem as @ChekeredList71 .

I have a pc with an AMD RX580 and Linux Mint 22.2 XFCE (kernel 6.8, but I've tried newer 6.x kernels and the problem remained, so I reverted to 6.8). A few days ago I decided to install xlibre, because all my other computers already have it (but they use intel graphics). After installing xlibre and rebooting the GRUB menu showed up, then the Mint logo and then just a black screen.

My xlibre came from here https://github.com/xlibre-debian/ubuntu (I'm assuming @ChekeredList71 used the same repo).

What I do to get to the desktop is: On the GRUB menu I choose to boot into recovery mode, I then select resume boot, and this way the desktop environment shows up and everything seems to be normal. But I can't change the monitor resolution, I can't change refresh rates and changing scale does nothing (check attached image). And I don't have audio through HDMI (with xorg I had audio).
Another way to get into desktop is: On GRUB, pressed "e" and added "nomodeset" to the end of the line that starts with "linux". This worked the same as entering recovery mode and selecting resume (no ability to select resolutions, select refresh rates and using HDMI audio).
Also, sometimes the screen goes completely dark for a fraction of a second and then returns to normal.

I'm sending my log as attachment.

From what I can gather, this is not related with linux distributions nor with desktop environments, it seems to be related with AMD and modesetting.
Here's some related issues:
#1565
#2140 (comment)
#3090

I've tried searching how to do that in XLibre, but I couldn't find much.

Try rename /usr/lib64/xorg/modules/drivers/modesetting_drv.so to /usr/lib64/xorg/modules/drivers/modesetting_drv.so.off

Is this true?

Probably not, if you want to enable TearFree just use Option "TearFree" "true" in your amdgpu.conf in xorg.conf.d

I wanted to try this, but I don't have any folder inside /usr/lib64/. I don't care if I loose TearFree. I don't have any custom settings set up.

Huh this is weird why is amdgpu and modesetting both detecting and trying to load the same gpu here? Even with amdgpu enabled the user shouldnt be required to disable modesetting in a hacky way. What's ur setup? Do u have an amd igpu and an amd dgpu or something? That being said, is modesetting broken on ur gpu or something? Usually I'd recommand using modesetting instead of amdgpu if modesetting works fine on ur setup. U can specify the driver to use and disable automatic gpu detection in Xorg.conf as a workaround.

I like to think that I'm an advanced user, but I don't know how to do a lot of things. I'm assuming I can configure here "/etc/X11/xorg.conf.d/", but I'm not finding any Xorg.conf.

Xorg.0.log

Thanks for your work.

[NexusSfan]

but I don't have any folder inside /usr/lib64

Check /usr/*/xorg/modules/drivers/modesetting_drv.so

[filipe-maia]

Check /usr/*/xorg/modules/drivers/modesetting_drv.so

Thanks for guiding me in the right direction.
I searched in /usr/*/xorg/modules and found these:

/usr/lib/xorg/modules$ ls -LR
.:
drivers input xlibre-25

./drivers:
ati_drv.so intel_drv.so qxl_drv.so vesa_drv.so
fbdev_drv.so nouveau_drv.so radeon_drv.so vmware_drv.so

./input:
libinput_drv.so wacom_drv.so

./xlibre-25:
drivers input libfbdevhw.so libint10.so libshadow.so libwfb.so
extensions libexa.so libglamoregl.so libshadowfb.so libvgahw.so

./xlibre-25/drivers:
modesetting_drv.so video

./xlibre-25/drivers/video:
amdgpu_drv.so

./xlibre-25/extensions:
libglx.so

./xlibre-25/input:
inputtest_drv.so

I changed the name of /usr/lib/xorg/modules/xlibre-25/drivers/modesetting_drv.so and rebooted.
After rebooting everything is working great :)

Thank you.

If you need me to test anything to help you debug, let me know and I'll try it out.

Here's my successful log:
Xorg.0.log
Now I have 'Failed to load module "modesetting" (module does not exist, 0)', which is expected.
I also have the following errors, but maybe they don't matter:

AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC0. Property value may not reflect actual hardware state.
AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC1. Property value may not reflect actual hardware state.
AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC2. Property value may not reflect actual hardware state.
AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC3. Property value may not reflect actual hardware state.
AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC4. Property value may not reflect actual hardware state.
AMDGPU(0): Failed to initialize color management property DEGAMMA_LUT on CRTC5. Property value may not reflect actual hardware state.
...
AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter

[NexusSfan]

Alright