From: Eli Zaretskii <eliz@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: luangruo@yahoo.com, 56528@debbugs.gnu.org
Subject: bug#56528: 29.0.50; Emacs lucid segfaults when X dies
Date: Wed, 13 Jul 2022 20:54:11 +0300 [thread overview]
Message-ID: <83o7xsvqyk.fsf@gnu.org> (raw)
In-Reply-To: <87o7xs7wgy.fsf@gmail.com> (message from Visuwesh on Wed, 13 Jul 2022 22:59:01 +0530)
> From: Visuwesh <visuweshm@gmail.com>
> Cc: luangruo@yahoo.com, 56528@debbugs.gnu.org
> Date: Wed, 13 Jul 2022 22:59:01 +0530
>
> [புதன் ஜூலை 13, 2022] Eli Zaretskii wrote:
>
> >> Cc: luangruo@yahoo.com, 56528@debbugs.gnu.org
> >> Date: Wed, 13 Jul 2022 20:11:41 +0300
> >> From: Eli Zaretskii <eliz@gnu.org>
> >>
> >> I think we should close this bug as wontfix. It's unreasonable to
> >> expect a GUI program to stay in the air when its GUI infrastructure is
> >> forcibly killed.
> >
> > As a possible workaround, did you try to delete all the frames,
> > i.e. leave the daemon session without any live frame, before shutting
> > down X?
>
> Yes, that works. I forgot to check if I could do this in the second
> round of testing, sorry.
Then perhaps we should add a command delete-all-frames or something,
and call it a day.
next prev parent reply other threads:[~2022-07-13 17:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 4:32 bug#56528: 29.0.50; Emacs lucid segfaults when X dies visuweshm
2022-07-13 10:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 11:05 ` Visuwesh
2022-07-13 12:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-13 13:06 ` Visuwesh
2022-07-13 13:13 ` Eli Zaretskii
2022-07-13 13:15 ` Eli Zaretskii
2022-07-13 13:23 ` Visuwesh
2022-07-13 13:49 ` Eli Zaretskii
2022-07-13 14:18 ` Visuwesh
2022-07-13 17:11 ` Eli Zaretskii
2022-07-13 17:18 ` Eli Zaretskii
2022-07-13 17:29 ` Visuwesh
2022-07-13 17:54 ` Eli Zaretskii [this message]
2022-07-13 17:20 ` Visuwesh
2022-07-13 17:50 ` Eli Zaretskii
2022-07-14 1:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:41 ` Eli Zaretskii
2022-07-14 6:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 7:18 ` Eli Zaretskii
2022-07-14 1:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:39 ` Eli Zaretskii
2022-07-14 6:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 7:18 ` Eli Zaretskii
2022-07-14 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-15 16:17 ` Andrés Ramírez
2022-07-16 3:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 0:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:36 ` Eli Zaretskii
2022-07-14 6:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 3:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 4:24 ` Visuwesh
2022-07-14 4:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-14 5:37 ` Visuwesh
2022-07-14 6:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7xsvqyk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56528@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=visuweshm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).