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

Ouverte
  • Quelque chose ne va pas ?
#3,585 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
electron, go, linux
Domaine
backend, desktop

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Go
Étoiles
22.7k
Forks
1.2k
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de wavetermdev/waveterm

Toutes les issues de wavetermdev/waveterm

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.