Linux/Wayland: selecting external display leaves Omarchy bar unresponsive until shell restart

Offen
#4,119 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
desktop

Rechercherichtung

Start by reading the capture target overlay and hotkey paths, guided by the cap_gpui::target_overlay and cap_gpui::hotkeys log entries. Then investigate how external-display capture interacts with the clean-capture prompt and the desktop environment; the issue does not establish a cause. Done when selecting and finishing a capture no longer leaves the external display's bar unresponsive, with behavior verified on a two-display Wayland setup.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Description

Selecting the external display for capture in Cap makes the entire Omarchy top bar on that display unresponsive. The laptop display's bar and tray remain usable, so recording can be started and stopped from there. Quitting Cap completely does not restore the external bar; running omarchy restart shell does.

Expected: selecting a capture display should leave both monitors' desktop bars interactive, and ending capture or quitting Cap should release any capture-related UI state.

The trigger and recovery were observed by the user. The underlying cause has not been established: this may be an interaction between Cap's picker/clean-capture UI, Hyprland and Omarchy's Quickshell bar. No claim that an invisible overlay or input grab is the cause has been verified.

Reproduction
  1. Run Cap on Omarchy/Hyprland with an integrated laptop display and an external display.
  2. Choose Studio mode and select the external display for recording.
  3. The external display's entire top bar stops responding to interaction.
  4. Cap presents the clean-capture prompt asking to activate its Stop tray icon before recording starts.
  5. Use the integrated display's tray icon to start and stop recording. Recording works, but the external bar remains unresponsive.
  6. Quit Cap completely: the external bar still does not respond.
  7. Run omarchy restart shell: the external bar responds again.
Additional Context

Installed versions, read from pacman:

  • Cap: cap-bin 1:0.6.3-1 (official Arch download)
  • Omarchy: 4.5.0-3
  • Hyprland: 0.56.2-4
  • Quickshell: 0.3.2.r7.g2b4501a-1
  • xdg-desktop-portal: 1.22.1-2
  • xdg-desktop-portal-hyprland: 1.4.1-2
  • Linux x86_64, Wayland
  • GPUs: NVIDIA GeForce RTX 3050 Mobile and AMD Radeon 680M; which GPU drives each output was not verified.

Configured outputs:

hl.monitor({ output = "eDP-1", mode = "1920x1080@144", position = "0x0", scale = 1.6 })
hl.monitor({ output = "HDMI-A-1", mode = "preferred", position = "-1920x0", scale = 1 })

Relevant Cap log excerpts (timestamps omitted):

INFO cap_gpui::target_overlay: overlay start pressed target="Display"
INFO cap_gpui::hotkeys: Using the recording Stop tray instead of GlobalShortcuts error=The portal did not describe the granted Stop shortcut
INFO cap_gpui::hotkeys: recording Stop control ready label=Activate the Cap Stop tray icon to start. Activate the same icon again to stop. Recording will not start until you use that control.

Screenshot attempts in the same two-display setup also fail with:

ERROR cap_gpui::screenshot: screenshot capture failed: capturing the screenshot: Wayland screenshot portal cannot safely isolate the selected display

It is not established whether the screenshot error and stuck bar share a cause. Related tray-label report #3959 does not cover the persistent external-bar failure described here.

Desktop behavior above is user-observed; package versions, configuration and log excerpts were inspected locally. No recording attachment or independent automated desktop reproduction is available.

Vorherrschende Sprache
Rust
Sterne
25k
Forks
2.4k
Ø Merge
1 T. 8 Std.
Gemergte PRs (30 T.)
676

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus CapSoftware/Cap

Alle Issues in CapSoftware/Cap

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.