From: Benjamin Schwehn <bschwehn@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 66151@debbugs.gnu.org
Subject: bug#66151: 29.1.50; daemon crashing after X forwarding disconnects
Date: Fri, 22 Sep 2023 18:51:09 +0200 [thread overview]
Message-ID: <CA+CxCG_sR3=Av3XWF96J8yyVuS_igFwMziuKgD5ekE_nWY1+zA@mail.gmail.com> (raw)
In-Reply-To: <83msxe5jqy.fsf@gnu.org>
On Fri, 22 Sept 2023 at 17:07, Eli Zaretskii <eliz@gnu.org> wrote:
> I think this confirms what Po Lu was saying: Emacs cannot recover when
> you close the connection while some frame using that connection is
> still on display. You should close all such frames before
> disconnecting.
Ok, sounds like there is no easy fix, thanks for the explanation!
I am curious though, before switching to lucid, emacs logged this during startup
as systemd service:
Warning: due to a long standing Gtk+ bug
https://gitlab.gnome.org/GNOME/gtk/issues/221
Emacs might crash when run in daemon mode and the X11 connection is
unexpectedly lost.
Using an Emacs configured with --with-x-toolkit=lucid does not have
this problem.
Do you happen to know what (if any) difference using lucid or gtk does in this
use case?
> > It's not a terrible issue for me, but annoyingly happens every time the VPN
> > connection is lost (~twice a day) and I have emacs open (~all the time :)).
>
> Why is the VPN connection lost so frequently?
Well, it is a work provided setup I have no control over. Half the disconnects
are due to me missing the mandatory re-authentication every x hours, the other
half I don't know.
I had quickly experimented with xpra (https://github.com/Xpra-org/xpra), which
should keep a persistent X11 connection. But it increased latency too much for
my liking.
Ben
next prev parent reply other threads:[~2023-09-22 16:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 10:22 bug#66151: 29.1.50; daemon crashing after X forwarding disconnects Benjamin Schwehn
2023-09-22 12:22 ` Eli Zaretskii
2023-09-22 13:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-22 13:16 ` Eli Zaretskii
2023-09-22 14:28 ` Benjamin Schwehn
2023-09-22 15:07 ` Eli Zaretskii
2023-09-22 16:51 ` Benjamin Schwehn [this message]
2023-09-22 23:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 15:02 ` bug#66151: George P
2024-04-09 15:16 ` bug#66151: 29.1.50; daemon crashing after X forwarding disconnects George P
2024-04-09 17:28 ` George P
2024-04-10 2:02 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-10 15:42 ` George P
2024-04-11 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 2:03 ` George P
2024-04-13 1:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 7:46 ` George P
2024-04-13 11:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 17:56 ` George P
2024-04-18 10:40 ` Eli Zaretskii
2024-04-19 9:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-19 11:15 ` Eli Zaretskii
2024-04-19 12:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-27 8:37 ` Eli Zaretskii
2024-05-05 16:25 ` George P
2024-05-06 11:02 ` Eli Zaretskii
2024-05-07 0:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 20:36 ` George P
2024-05-07 20:26 ` Benjamin Schwehn
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='CA+CxCG_sR3=Av3XWF96J8yyVuS_igFwMziuKgD5ekE_nWY1+zA@mail.gmail.com' \
--to=bschwehn@gmail.com \
--cc=66151@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.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).