Skip to content

Codex starts on KDE Wayland but never shows a window; X11 path crashes in EGL #25

Description

@NtrpyDev

Codex starts on KDE Wayland but never shows a window; X11 path crashes in EGL

Summary

On a KDE Plasma Wayland session, codex-app starts from its desktop launcher and shows a dock icon briefly, but no usable Codex window appears.

The packaged app forces Electron to use X11 on Linux:

process.platform === `linux` && (
  process.env.ELECTRON_OZONE_PLATFORM_HINT = `x11`,
  app.commandLine.appendSwitch(`ozone-platform`, `x11`)
);

On this machine, that path crashes while Electron creates its graphics surface. Removing the forced-X11 code starts the renderer on native Wayland and stops the EGL crash. It still does not create a visible window.

Steps to reproduce

  1. Log in to KDE Plasma on Wayland.
  2. Install and launch am-will/codex-app v26.707.31428 from its desktop entry.
  3. Wait about 10–15 seconds.

Expected: a visible Codex window that can receive input.

Actual: the dock icon appears, but no Codex window is visible or usable. With the shipped X11 forcing enabled, Codex writes GPU-process failures and then creates a core dump.

Environment

  • OS: CachyOS Linux
  • Kernel: 7.1.1-2-cachyos
  • Desktop session: KDE Plasma 6.7.1 on Wayland
  • Window manager: KWin 6.7.1
  • GPU: AMD Radeon RX 9070 XT (Navi 48)
  • Kernel GPU driver: amdgpu
  • Mesa: 26.1.2-arch3.1
  • OpenGL renderer: AMD Radeon RX 9070 XT (radeonsi, gfx1201, ACO, DRM 3.64, 7.1.1-2-cachyos)
  • App: am-will/codex-app v26.707.31428, installed from the GitHub release published 2026-07-10
  • Bundled Electron: 42.1.0

Relevant logs

ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:285] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
ERROR:content/browser/gpu/gpu_process_host.cc:999] GPU process exited unexpectedly: exit_code=139
Recoverable Chromium child process gone exitCode=139 name=null processType=GPU reason=crashed serviceName=GPU
ERROR:ui/base/x/x11_software_bitmap_presenter.cc:147] XGetWindowAttributes failed for window 1

The user-session coredump points at EGL_CreateWindowSurface:

Process ... (Codex) of user 1000 dumped core.
#4 EGL_CreateWindowSurface (libGLESv2.so)
#5 eglCreateWindowSurface (libEGL.so)

What I tried

Test Result
Launch the unmodified desktop entry No visible window; GPU helper crashes and Codex later dumps core.
--disable-gpu Codex exits with GPU access not allowed; it cannot use this mode.
--disable-gpu-compositing No visible window.
LIBGL_ALWAYS_SOFTWARE=1 while using the shipped X11 path No visible window.
Remove the hard-coded X11 forcing and let Electron use Wayland Renderer runs with --ozone-platform=wayland and the EGL crash stops, but no visible window appears.

The modified archive was restored after testing. No workaround is currently applied.

Request

Please test the Linux X11/Ozone patch on a KDE Wayland session, especially with recent AMD/Mesa drivers. The package needs a supported way to select its display backend. It should not always force --ozone-platform=x11.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions