App crashes (main process trap int3) when dragging or pasting files from Nautilus on Linux X11

Aperta
  • Qualcosa non va?
#3,585 0 commenti 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
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
electron, go, linux
Ambito
backend, desktop

Direzione di ricerca

Start by tracing Electron's clipboard and drag-and-drop handling for Nautilus file data, especially text/uri-list and x-special/gnome-copied-files, then reproduce on Linux X11 with the steps in the issue. The crash appears in the Electron main process, but the payload names no source files or tests. Done when dragging and pasting a file path inserts it or is safely ignored without crashing Wave.

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

Descrizione

Description

Wave crashes completely (the window disappears) when I drag a file from the file manager (Nautilus) into a Wave terminal block. Copying the file in Nautilus (Ctrl+C) and pasting it into Wave (Ctrl+V) crashes the same way.

The crash happens about 1 second after the Wave window gets focus back from Nautilus. It is repeatable: both crashes stopped at the same instruction offset.

Steps to reproduce
  1. Open Wave with a terminal block (in my case it was running Claude Code).
  2. In Nautilus, select a document file.
  3. Either drag it onto the terminal block, or press Ctrl+C in Nautilus, switch to Wave and press Ctrl+V.
  4. Wave crashes.

Expected: the file path is inserted into the terminal (or the drop/paste is ignored).
Actual: the whole Electron app exits.

Environment
  • Wave: 0.14.5 (202604161535), snap, revision 204, latest/stable, classic confinement
  • Electron: 41.1.0
  • OS: Zorin OS 18.1 (Ubuntu 24.04 base), kernel 7.0.0-42-generic
  • Desktop: GNOME on X11 (not Wayland)
  • File manager: Nautilus 46.4
Evidence

Kernel log, one line per crash. Both show the same offset (59c0810) inside the waveterm binary, which looks like a Chromium/Electron CHECK/NOTREACHED failure in the browser (main) process:

kernel: traps: waveterm[9089] trap int3 ip:631fa0506810 sp:7ffd6d34fde0 error:0 in waveterm[59c0810,631f9d1d5000+9705000]
kernel: traps: waveterm[1601014] trap int3 ip:55da10da3810 sp:7ffe3a3140c0 error:0 in waveterm[59c0810,55da0da72000+9705000]

waveapp.log shows nothing at the moment of the crash. The last entries before the second crash are a window focus, then the app restarting:

20:26:21.027 focus win e7cfa4ad-...
20:26:21.032 [service] client.FocusWindow | 5ms
   (crash at 20:26:22 per kernel log)
20:26:28.321 waveterm-app starting, ... electron=41.1.0

wavesrv itself did not report any error. Only the Electron process died. No Crashpad dump was written.

Other log noise at startup, probably unrelated:

ERROR:media/gpu/vaapi/vaapi_wrapper.cc:1640] vaInitialize failed: unknown libva error
Notes
  • When copied from Nautilus, the clipboard/drag data carries files (text/uri-list / x-special/gnome-copied-files), not plain text. My guess is that handling this file data is what crashes. Normal terminal use is otherwise stable: there were no other crashes in the last 30 days.
  • Workaround: type the file path instead of dragging or pasting the file.
Lingua principale
Go
Stelle
22.7k
Fork
1.2k
Nessuna PR unita negli ultimi 30g

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 wavetermdev/waveterm

Tutte le issue di wavetermdev/waveterm

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.