Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[MacOS] Recovery fails with IO error: File exists (os error 17) and cannot be retried

Aperta
  • Qualcosa non va?
#2,386 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
macos, rust
Ambito
desktop, operating-systems

Direzione di ricerca

Start with the attached debug log and trace the desktop recovery flow after fragmented segments are found, focusing on the finalization step that reports OS error 17. Reproduce the failure on macOS, identify the conflicting file-handling condition, and verify that recovery succeeds or reports a meaningful error without deleting the original recording.

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

Descrizione

bug
Description

After a recording unexpectedly enters the recovery state, attempting to recover it consistently fails with:
IO error: File exists (os error 17)

The error is reproducible on every recovery attempt. Restarting the recovery process does not help, and the recording remains unrecoverable through the UI.

The debug log shows that the recording pipeline finishes successfully, but finalization fails afterward:

Found 1 fragmented segments in "...cap" with estimated duration 0ns
Failed to finalize fragmented recording: Failed to finalize recording: IO error: File exists (os error 17)

This appears to be an internal file-handling or finalization issue. The recovery process may be attempting to create a file that already exists, but the exact conflicting path is unclear.

Expected behavior:
  • Recovery should successfully finalize the recording, or provide a meaningful error identifying the underlying problem.
  • Repeated recovery attempts should not get permanently stuck on the same error.
  • The original recording data should be preserved when recovery fails.
Actual behavior:
  • Recovery repeatedly fails with the same File exists error.
  • The only apparent alternative is Discard, which permanently deletes the recording.
Reproduction
  1. Record the screen for an extended period (approximately 30 minutes in my case).
  2. Let the recording finish.
  3. When Cap enters the recovery state, attempt to recover the recording.
  4. Recovery fails with IO error: File exists (os error 17).
  5. Retry recovery — the same error occurs again.
  6. The recording cannot be recovered through the UI.
Additional Context

Cap version: 0.6.0
Operating system, version: macOS 26.2 (25C56)
Device: MacBook Pro M1 Pro, 16 GB RAM

The recording was approximately 30 minutes long.

cap-desktop-2026-09-29.log

Lingua principale
Rust
Stelle
23k
Fork
2k
Merge medio
10h 41m
PR unite (30g)
89

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 CapSoftware/Cap

Tutte le issue di CapSoftware/Cap

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.