openai / openai/codex

Linux/Wayland: floating Voice overlay creates oversized transparent window with visible border/shadow

Open
#45,514 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app bug Linux
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Linux/Wayland: floating Voice overlay creates oversized transparent window with visible border/shadow

What version of the Codex App are you using (From “About Codex” dialog)?

26.901.20858, verified from installed desktop package metadata (not the About dialog).

What subscription do you have?

Not provided.

What platform is your computer?

Linux 7.1.9-arch1-2 x86_64 unknown. Arch Linux/Omarchy, Hyprland 0.56.2, native Wayland. One 3840 × 2160 display at scale 2, giving a 1920 × 1080 logical desktop. The desktop has local Omarchy customizations.

What issue are you seeing?

During a Voice conversation, the detached voice orb intermittently appears inside a much larger transparent surface with a visible border/shadow. The user reports that this makes other windows difficult to select.

A screenshot and read-only compositor snapshot taken while the symptom was present confirmed:

  • A new floating window belonging to the same desktop app process as the main window.
  • Class/title: chatgpt / ChatGPT.
  • Native Wayland (xwayland: false).
  • Position (574, -508) and size 772 × 2129, in logical pixels, extending above and below the 1080-pixel-high logical display.
  • The window was mapped, visible, active, and reported acceptsInput: true.
  • A small voice orb and controls were visible within the oversized transparent rectangle.

The snapshot confirms window ownership, geometry, and focus. It does not measure the surface input region or prove where individual clicks were delivered. Click blocking is the user's observed symptom, not an instrumented reproduction.

What steps can reproduce the bug?

  1. Run the desktop app on native Wayland under Hyprland with the environment above.
  2. Start a Voice conversation and use other desktop windows while it remains active.
  3. When the detached voice orb appears, observe the transparent surface surrounding it.

This occurred intermittently and was captured once while present. The exact transition that triggers it has not been isolated; these are observation conditions rather than a guaranteed reproduction sequence.

What is the expected behavior?

The detached Voice UI should not draw a large desktop-spanning border/shadow or prevent interaction with unrelated windows through visually empty areas. Its own voice controls should remain usable.

Additional information

No ChatGPT-specific size rule was found in the inspected Omarchy/Hyprland configuration, and Hyprland reported no configuration errors. The captured overlay subsequently disappeared. No window resizing, input injection, or configuration changes were performed during diagnosis.

No screenshots or raw logs are attached because they include unrelated private desktop content. The geometry and state above are the relevant sanitized observations. Root cause remains unconfirmed; this could involve the app's overlay implementation and its interaction with native Wayland/Hyprland.

Related reports, not confirmed duplicates or a shared cause:

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the detached Voice overlay under native Wayland on Hyprland and observe its geometry, visibility, focus, and input behavior. Trace the overlay implementation from the desktop app once the oversized surface is reproduced; done means the orb remains usable without a large visible border, shadow, or input-blocking transparent area.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.