displayX11 requires Xephyr on X11 but nested display fails with MIT-SHM errors (black screen)

Open
#89 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, linux
Domain
backend, desktop

Research direction

Start at the code that handles the displayX11 and socketX11 overrides and sets up X11 access for cpak run; the issue does not name a file or test. Reproduce with Xephyr using the supplied mpv command, then trace the MIT-SHM errors and the missing /tmp/.X11-unix mount. Done when video renders in the nested display without those errors.

Written by the indexing model from the issue text.

Description

Summary

On a bare X11 session (Ratpoison, DISPLAY=:0.0, no Wayland), enabling displayX11 for a native package requires Xephyr. Even with Xephyr installed the nested display produces MIT-SHM errors and a black screen.

Environment
  • Host: Fedora bootc, Ratpoison (X11), ALSA (no Pulse/PipeWire socket)
  • cpak: 2.14.18
  • Package: github.com/containerpak/mpv
  • Xephyr: xorg-x11-server-Xephyr 21.1.25
Steps
  1. Install package and set override:
    • socketX11 / displayX11: true
    • deviceAlsa: true
    • filesystem: home/.config/mpv + home/Videos
  2. Install Xephyr
  3. Run:
    cpak run github.com/containerpak/mpv -- /usr/bin/mpv --vo=x11
Result
  • Audio works (ALSA)
  • Window opens via Xephyr
  • Video output fails:
[vo/x11/x11] X11 error: BadAccess
[vo/x11/x11] X11 error: BadShmSeg
[vo/x11] can't keep up! Waiting for XShm completion events...
  • Black screen. --vo=gpu and --vo=xv also fail to produce an image.
  • Direct X11 socket is never mounted (/tmp/.X11-unix does not exist inside the container).
Dominant language
Go
Stars
218
Forks
5
Avg merge
45m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Containerpak/cpak

All issues in Containerpak/cpak

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.