Debian 13 KDE Plasma, I found two different issues with the X11 isolation backend. bottles

Aperta
#79 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
go, linux

Direzione di ricerca

Inizia dai percorsi del broker relativi a cleanupX11Bridge(), ServerAlive() e ai messaggi WATCH_CLOSED/BONBON_STOP. Riproduci un titolo Unity con la patch di Xephyr raccogliendo al contempo i log del broker e gli alberi dei processi forniti, quindi stabilisci se il processo Unity o Xephyr termina per primo. Il lavoro è completato quando i giochi Unity continuano a essere eseguiti sotto Xephyr senza che la connessione X11 annidata venga chiusa.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

After testing cpak on Debian 13 KDE Plasma, I found two different issues with the X11 isolation backend.

Environment
  • Distribution: Debian 13 (Trixie)
  • Desktop: KDE Plasma (Wayland session)
  • Bottles installed through cpak
  • Xephyr available and used as the isolated X11 server
  • Reproduced multiple times
Issue 1: Xwayland backend

When cpak uses the Xwayland backend, some applications never reach a usable window state.

Observed behavior:

  • Application process starts.
  • Xwayland appears to start correctly.
  • The application hangs while creating its window.
  • No usable application window becomes visible.

This was the original reason I experimented with replacing the Xwayland backend.

Issue 2: Xephyr backend

I patched cpak to use Xephyr instead of Xwayland.

Results:

  • RPG Maker games run normally.
  • The isolated window appears correctly.
  • Clipboard integration appears functional.

However, Unity games behave differently:

  • The game starts.
  • The Unity window appears briefly (or begins opening).
  • The game exits immediately.
  • The failure occurs consistently with Unity titles.
Observations

While debugging the broker, I observed repeated messages such as:

TICK: windows=0 seenWindow=true primary=0x1200001

followed later by:

WATCH_CLOSED ... X11 connection closed
BONBON_STOP: nested endpoint error: X11 connection closed

I could not find evidence that the broker explicitly closes the game because no application window exists.

From the current code inspection:

  • cleanupX11Bridge() is only reached through container cleanup paths.
  • The broker receives ServerAlive() callbacks and stops when the nested X11 server disappears.
  • It is currently unclear whether the Unity process exits first and causes Xephyr shutdown, or whether Xephyr terminates first and causes the Unity process to exit.
Expected Behavior

Unity games should remain running under the Xephyr backend just like RPG Maker games.

Additional Information

I can provide:

  • Full broker debug logs
  • Process trees before and after the Unity game exits
  • A test title that reproduces the issue consistently
  • The Xephyr patch used for testing
Lingua principale
Go
Stelle
218
Fork
5
Merge medio
45m
PR unite (30g)
5

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Containerpak/cpak

Tutte le issue di Containerpak/cpak

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.