Linux, turning off the only monitor causes crash

[wrab2]

Type

Crash to desktop

Bug description

If you turn off the only monitor game crashes immediately and leaves this error message

Unhandled exception. System.InvalidOperationException: Failed to get number of SDL displays. Return code: 0. SDL Error: 
   at osu.Framework.Platform.SDL2.SDL2Window.getSDLDisplays()
   at osu.Framework.Platform.SDL2.SDL2Window.fetchDisplays()
   at osu.Framework.Platform.SDL2.SDL2Window.handleDisplayEvent(SDL_DisplayEvent evtDisplay)
   at osu.Framework.Platform.SDL2.SDL2Window.HandleEvent(SDL_Event e)
   at osu.Framework.Platform.SDL2.SDL2Window.pollSDLEvents()
   at osu.Framework.Platform.SDL2.SDL2Window.RunFrame()
   at osu.Framework.Platform.SDL2.SDL2Window.RunMainLoop()
   at osu.Framework.Platform.SDL2.SDL2Window.Run()
   at osu.Framework.Platform.GameHost.Run(Game game)
   at osu.Desktop.Program.Main(String[] args)
/usr/bin/osu-lazer: line 2:  6568 Aborted                 (core dumped) env OSU_EXTERNAL_UPDATE_PROVIDER=1 /opt/osu-lazer/osu.AppImage "$@"

I found that starting the game with environmental variable SDL_VIDEO_X11_XRANDR=0 fixes the problem but I don't know if it has other drawbacks and it's mildly annoying to do

OS: Arch linux, kernel 6.12.6-arch1-1
tried on dwm and Hyprland, same thing happens on both

Screenshots or videos

No response

Version

2025.101.0-lazer

Logs

compressed-logs.zip

[peppy]

Looks like you're trying to get osu! working (or running into an ongoing issue keeping it running) on linux. Linux is a hard platform for us to support here due to the vastness of the distributions, libraries and hardware configurations people run it in that we would suggest you instead seek support over at this linux-friendly discord server:

https://discord.com/invite/thepoon

[whrvt]

This is an osu!framework issue. That is the conclusion. Just because you don't want to look into it doesn't mean the problem doesn't exist, which is what you're signaling by closing and locking the related issues.

[peppy]

Hey,

We can't handle linux issues right now due to the scope of linux, so this is our default handling. Sorry if this offended you.

You can continue discussion in this discussion thread. The "closing and locking" is just how github handles the conversion to discussion.

That said, at first sight, this sounds like an SDL or wayland issue since the underlying error is coming from SDL.

[wrab2]

The issue is unrelated to desktop environment or wayland, 0 displays counts as an error in SDL but can it be handled without closing the app? It will stop being 0 when display is reconnected.