GNU bug report logs - #56528
29.0.50; Emacs lucid segfaults when X dies

Previous Next

Package: emacs;

Reported by: visuweshm <at> gmail.com

Date: Wed, 13 Jul 2022 04:33:02 UTC

Severity: normal

Tags: moreinfo

Found in version 29.0.50

Done: Po Lu <luangruo <at> yahoo.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Visuwesh <visuweshm <at> gmail.com>
Cc: luangruo <at> yahoo.com, 56528 <at> debbugs.gnu.org
Subject: bug#56528: 29.0.50; Emacs lucid segfaults when X dies
Date: Wed, 13 Jul 2022 16:49:26 +0300
> From: Visuwesh <visuweshm <at> gmail.com>
> Cc: luangruo <at> yahoo.com,  56528 <at> debbugs.gnu.org
> Date: Wed, 13 Jul 2022 18:53:59 +0530
> 
> > Btw, what do we expect Emacs to do in this scenario?  If the X server
> > is killed, Emacs cannot display anything, so why an abort is not TRT?
> > What practically interesting use case does this emulate?
> 
> Emacs is running as a daemon, I expect it to survive the death of X.

"Survive" how? by closing all the frames?

IOW, you are saying that when this happens, Emacs should test whether
it has a running server, and if it does, unconditionally close all the
frames?  Is that really useful?

> Emacs dying on me because I killed X is an annoyance since sometimes I
> need to restart X.

Why not close Emacs before that -- this way you get to keep all your
edits, instead of relying on error handling to succeed in doing that.




This bug report was last modified 3 years and 5 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.