glxgears (+ applications creating a new gl context) fail to launch in Simula
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 3.2k
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
Example:
$ DISPLAY=:1 glxgears
Error: couldn't get an RGB, Double-buffered visual
Duplicated by @lwneal in Discord chat:
As for the OpenGL-inside-SimulaVR question, I still haven't figured out whether it's something trivial (like an envvar set the wrong way) or something deeply structural. Basically, a program like glxgears or any hello-world program that initialized an openGL context, fails when run within Simula
After fixing a few things like LD_LIBRARY_PATH I can actually run something like DISPLAY=:1 glxgears from a terminal inside Simula, and it works- but it displays the OpenGL-rendered window on the monitor, not within the VR workspace
DISPLAY=:2 glxgearsresults in a segfault for me- maybe it's just a driver issue? are you usually running on an AMD card?
Pernosco trace: https://pernos.co/debug/7WwpVupHw-4kySWCKTw5xA/index.html
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.
Research direction
Start by reproducing the failure with DISPLAY=:1 glxgears inside Simula and review the linked Pernosco trace. Compare the behavior with DISPLAY=:2 and the reported LD_LIBRARY_PATH adjustment; done means OpenGL applications create their contexts and render inside the VR workspace rather than on the monitor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- computer-graphics, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100