Re: Emacs daemon dies at Xorg crash

[Dan Nicolaescu]

Chong Yidong <address@hidden> writes:

  > Ulrich Mueller <address@hidden> writes:
  > 
  > > AFAICS Emacs only dies if there's no other connection open. I've
  > > tested it with another client open on a tty, and Emacs survived.
  > >
  > > The last thing it outputs is "Connection lost to X server `:0.0'", so
  > > it passes through x_io_error_quitter, which in turn will call
  > > x_connection_closed.
  > >
  > > In x_connection_closed there are two tests for the last terminal,
  > > where shut_down_emacs is called. Probably this should be modified for
  > > the daemon case?
  > 
  > I'm not sure this is the problem.  The two tests you mention are
  > 
  >   if (terminal_list->next_terminal == NULL)
  > 
  > where terminal_list points to the X terminal about to be deleted, and
  > 
  >   if (terminal_list == 0)
  > 
  > after the deletion of the terminal.  Unless the code has changed since
  > the last time I looked at it, Emacs uses an initial terminal, which
  > neither sends nor receives anything, when it is run as a daemon; the
  > existence of this initial terminal should prevent shut_down_emacs from
  > being called.

Agreed.
There wasn't enough context in the initial mail, but I suspect this is
an emacs compiled with Gtk+.  It works (and it has always done so)
perfectly well for me when using Lucid.

There's a long standing Gtk+ bug:
http://bugzilla.gnome.org/show_bug.cgi?id=85715
that creates problems with closing the display for Emacs from time to
time.  Jan has put in a few workarounds, but the bug in Gtk+ still
exists.