[APP BUG] "No available displays" error when running headless x11 on linux
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp, linux
- Domain
- desktop, operating-systems
Research direction
Start by locating the SDL2 rendering-window initialization and the project's SDL dependency configuration. Reproduce the failure on headless Debian 12 with X11, then compare behavior with SDL_VIDEO_X11_XRANDR=0 and the referenced upstream SDL fix. Done means the standalone frontend handles this environment without the reported error, or the supported workaround is clearly documented.
Written by the indexing model from the issue text.
Description
Please confirm the following points:
- This report is NOT about the Android apps in the Play Store
- I have searched the project page to check if the issue was already reported
Affected Application
projectM Standalone SDL2 Frontend (includes the Steam app)
Affected Version
No response
Operating System
Linux (Desktop)
Additional Application Details
Application version: 2.0.0
Built/running with projectM4 version: 4.1.0 / 4.1.0
Built against SDL version: 2.26.5 (running with 2.26.5)
Type of Defect
Graphical issue (rendering glitches, black screen, heavy flickering)
Log Output
Initializing subsystem: SDL2 Rendering Window
Could not create SDL rendering window. Error: No available displays
Exception: Could not create SDL rendering window. Error: No available displays
Describe the Issue
Debian12, running headless X11, SDL gives an error that there are "No available displays"
An effective workaround is to set the enviornment variable SDL_VIDEO_X11_XRANDR=0
Fixed in SDL 3.1.10+
https://github.com/libsdl-org/SDL/commit/71099149b8fc062ea0ece232ccdd9f0ee9b3588b
- Dominant language
- C++
- Stars
- 116
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from projectM-visualizer/frontend-sdl-cpp
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
projectM-visualizer/frontend-sdl-cpp#134 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
A delete command to remove visualizations that are buggy, don't work, or are just not good looking. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
projectM-visualizer/frontend-sdl-cpp#120 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
projectM-visualizer/frontend-sdl-cpp#118 · 2 comments ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 28/100
projectM-visualizer/frontend-sdl-cpp#110 · 6 comments ·
All issues in projectM-visualizer/frontend-sdl-cpp
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·