unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alejandro Benitez <benitezalejandrogm@gmail.com>
To: 11741@debbugs.gnu.org
Subject: bug#11741: 24.1; Daemon Dies When X Exits
Date: Fri, 3 Aug 2012 14:28:15 -0300	[thread overview]
Message-ID: <CAN9rHn-Kzqo1mjUx14smj4e5hT6rot+g4749LB=kTwMLnzpFAg@mail.gmail.com> (raw)
In-Reply-To: <87wr33igvm.fsf@volunteer.i-did-not-set--mail-host-address--so-tickle-me>

I'm posting this because the original message did not containt a subject.

Glenn Morris <rgm@gnu.org> writes:

> woddfellow2 wrote:
>
>> If I start an Emacs daemon, even outside of X, then open an emacsclient
>> frame in X, then C-x 5 0, then exit X, the daemon dies. This happens
>> even with emacs -Q. This appears to e a regression, as Emacs 23 did not
>> have this problem:
>>
>>   Connection lost to X server `:0'
>>   When compiled with GTK, Emacs cannot recover from X disconnects.
>>   This is a GTK bug: https://bugzilla.gnome.org/show_bug.cgi?id=85715
>>   For details, see etc/PROBLEMS.
>
> The above message seems pretty clear to me.
>
> Here's what the etc/PROBLEMS entry says:
>
>     ** When Emacs is compiled with Gtk+, closing a display kills Emacs.
>
>     There is a long-standing bug in GTK that prevents it from recovering
>     from disconnects: http://bugzilla.gnome.org/show_bug.cgi?id=85715.
>
>     Thus, for instance, when Emacs is run as a server on a text terminal,
>     and an X frame is created, and the X server for that frame crashes or
>     exits unexpectedly, Emacs must exit to prevent a GTK error that would
>     result in an endless loop.
>
>     If you need Emacs to be able to recover from closing displays, compile
>     it with the Lucid toolkit instead of GTK.

Hi,

Looks like this actually is a regression as the steps to reproduce
that described the OP are not the the same as the know problem.

1. I start an Emacs daemon, even outside of X
2. then open an emacsclient frame in X
3. then C-x 5 0
4. then exit X
5. the daemon dies

Step 3 means that the frame should be deleted before the X server
would supposedly crash or exit unexpectedly. The actual
problem is that the frame is not successfully deleted before exiting X,
although it looks like it does. Emacs 23.4.1 does delete the frame
successfully, so when I exit the X server I don't get a "there is
currently 1 client connected" message that when I get with Emacs 24.1.

I was able to reproduce this in Emacs 24.1 i686-pc-cygwin, GTK+.
Emacs 23.4.1 i686-pc-cygwin, GTK+ does not die after performing the
4 steps above.





  parent reply	other threads:[~2012-08-03 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-19 13:13 bug#11741: 24.1; Daemon Dies When X Exits woddfellow2
2012-06-19 16:18 ` Glenn Morris
2012-07-23  4:08 ` bug#11741: Alejandro Benitez
2012-08-03 17:28 ` Alejandro Benitez [this message]
2012-08-20  2:57 ` bug#11741: 24.1; Daemon Dies When X Exits Alejandro Benitez

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='CAN9rHn-Kzqo1mjUx14smj4e5hT6rot+g4749LB=kTwMLnzpFAg@mail.gmail.com' \
    --to=benitezalejandrogm@gmail.com \
    --cc=11741@debbugs.gnu.org \
    /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).