[BUG] Having workspaces, dashboard, and unicode modules enabled causes client to segfault

Aperta
  • Qualcosa non va?
#92 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

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
emacs-lisp
Ambito
backend

Direzione di ricerca

The report narrows the crash to enabling the workspaces, unicode, and dashboard modules in init.el and launching emacsclient -c; it links info.txt for system details. Start by reproducing with those modules and compare which combination triggers the crash. Done means identifying and fixing the module interaction so the daemon survives client frame creation.

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

Descrizione

Describe your issue

When I call emacsclient -c (this does not happen with just emacs or emacsclient -nw), the emacs daemon crashes. With emacs --fg-daemon open in a terminal, I can see the following output:

stack trace (long output) 
Due to a limitation in GTK 3, Emacs built with PGTK will simply exit when a
display connection is closed.  The problem is especially difficult to fix,
such that Emacs on Wayland with multiple displays is unlikely ever to be able
to survive disconnects.
Starting Emacs daemon.
Doom loaded 21 packages across 6 modules in 0.068s
Gdk-Message: 11:24:36.346: Unable to load sb_v_double_arrow from the cursor theme
Gdk-Message: 11:24:36.346: Unable to load sb_h_double_arrow from the cursor theme
Gdk-Message: 11:24:36.365: Unable to load hand2 from the cursor theme
Gdk-Message: 11:24:36.365: Unable to load sb_h_double_arrow from the cursor theme
Gdk-Message: 11:24:36.365: Unable to load sb_v_double_arrow from the cursor theme
Fatal error 11: Segmentation fault
Backtrace:
emacs(+0x183616) [0x5a6e6a101616]
emacs(+0x4f7ca) [0x5a6e69fcd7ca]
emacs(+0x4fddd) [0x5a6e69fcdddd]
emacs(+0x4fde4) [0x5a6e69fcdde4]
emacs(+0x1812f1) [0x5a6e6a0ff2f1]
/nix/store/pqyiidz5mi73wv5f91d48s9plcqyj5bz-glibc-2.44-57/lib/libc.so.6(+0x429f0) [0x7ebddde429f0]
emacs(+0x2b165f) [0x5a6e6a22f65f]
emacs(+0x24e6ed) [0x5a6e6a1cc6ed]
emacs(+0x1fdd9e) [0x5a6e6a17bd9e]
emacs(+0x1fe3d9) [0x5a6e6a17c3d9]
emacs(+0x1fe3d9) [0x5a6e6a17c3d9]
/nix/store/yxmbl6xs6vz1ly49h8x8rd2s9f7lck46-emacs-pgtk-31.1/lib/emacs/31.1/native-lisp/31.1-e6359f46/cl-seq-f464c4e2-2e568bb4.eln(F636c2d72656d6f7665_cl_remove_0+0xaa3) [0x7ebdd3e88313]
emacs(+0x1fe3d9) [0x5a6e6a17c3d9]
emacs(+0x1fe967) [0x5a6e6a17c967]
/nix/store/yxmbl6xs6vz1ly49h8x8rd2s9f7lck46-emacs-pgtk-31.1/lib/emacs/31.1/native-lisp/31.1-e6359f46/cl-seq-f464c4e2-2e568bb4.eln(F636c2d72656d6f76652d69662d6e6f74_cl_remove_if_not_0+0x7f) [0x7ebdd3e88e1f]
emacs(+0x24e6ed) [0x5a6e6a1cc6ed]
emacs(+0x1fdd9e) [0x5a6e6a17bd9e]
emacs(+0x1fff4b) [0x5a6e6a17df4b]
emacs(+0x1fd222) [0x5a6e6a17b222]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x2008e2) [0x5a6e6a17e8e2]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x2008e2) [0x5a6e6a17e8e2]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x2008e2) [0x5a6e6a17e8e2]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x200079) [0x5a6e6a17e079]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x2008e2) [0x5a6e6a17e8e2]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fd739) [0x5a6e6a17b739]
emacs(+0x1fdac0) [0x5a6e6a17bac0]
emacs(+0x1fdeed) [0x5a6e6a17beed]
emacs(+0x1fff4b) [0x5a6e6a17df4b]
...
zsh: segmentation fault (core dumped)  emacs --fg-daemon
Steps to reproduce

I was able to find that this can be reproduced with just workspaces, unicode, and dashboard present in init.el and no other files present in ~/.config/doom/.

init.el 
;;; init.el -*- lexical-binding: t; -*-
(doom! :input
       :ui
       dashboard    ; a nifty splash screen for Emacs
       unicode           ; extended unicode support for various languages
       workspaces)        ; tab emulation, persistence & separate workspaces

Removing any of these allows the client to launch perfectly fine, though I suspect the problem is more around unicode, and having the dashboard & workspaces modules enabled just allows that bug to pop up on frame creation.

System information

info.txt

Disclosures
  • This issue was written with/by AI.
Lingua principale
Emacs Lisp
Stelle
69
Fork
47
Merge medio
8g 9h
PR unite (30g)
2

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 doomemacs/modules

Tutte le issue di doomemacs/modules

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.