From: "Espen Wiborg" <espenhw@grumblesmurf.org>
To: "Dan Nicolaescu" <dann@ics.uci.edu>
Cc: 1310@emacsbugs.donarmstrong.com
Subject: bug#1310: 23.0.60; Emacs daemon behaves strangely if client loses X connection
Date: Mon, 10 Nov 2008 20:48:33 +0100 (CET) [thread overview]
Message-ID: <51066.84.209.20.118.1226346513.squirrel@www.chrissearle.org> (raw)
On Mon, November 10, 2008 09:29, Dan Nicolaescu wrote:
> "Espen Wiborg" <espenhw@grumblesmurf.org> writes:
> > With the patch the behavior is less deterministic:
> >
> > Emacs usually survives the first X crash, and will at this point happily serve
> > clients and create frames.
> >
> > The second crash usually calls abort() with the following backtrace:
>
> Unfortunately, I am still not able to play with killing X, so I can only
> offer guesses, but no real debugging...
I test by starting the daemon under a different name (./emacs -Q --daemon=testing) and
then run a secondary X server serving just the client with
startx `which emacsclient` -c -s /tmp/emacs`id -u`/testing -- :1
I can then zap the secondary X, e.g. with C-M-Backspace, without affecting my real session.
This trick is also useful to test strange resolutions, color depths etc.
> Does the problem happen if you configure emacs without Gtk (i.e.
> --with-x-toolkit=lucid)?
No, it doesn't. Or at least it happens much less frequently; in 35-40 tries I could
only provoke something once, but that seems to have been a clean shutdown (which is
infinitely preferable to the hang I get with Gtk enabled).
> Also, can you try if the problem happens if you do:
> in a text console: emacs -Q -f server-start
> now start X, and run emacsclient -c to connect to the server
> and kill X
> (this is to verify if the problem is related to --daemon, I am guessing
> it should not be, and similar problems were fixed long time ago...)
Interesting. With the Gtk-enabled Emacs, I get the same behavior as with --daemon, but
when I try to open a new frame after killing X, my console is spammed with
(emacs:6078): GLib-WARNING **: g_main_context_prepare() called recursively from within a
source's check() or prepare() member.
ad infinitum.
So it definitely looks as if Gtk is the culprit (or at least part of the problem).
I'm running this on Ubuntu 8.10, Intrepid Ibex; I appeare to have Gtk 2.14.4-0ubuntu1
installed.
--
Espen Wiborg <espenhw@grumblesmurf.org> - Veritas vos liberabit
A twisted mind is a joy forever.
next reply other threads:[~2008-11-10 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 19:48 Espen Wiborg [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-05 22:39 bug#1310: 23.0.60; Emacs daemon behaves strangely if client loses X connection Espen Wiborg
2008-11-07 5:08 ` Dan Nicolaescu
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51066.84.209.20.118.1226346513.squirrel@www.chrissearle.org \
--to=espenhw@grumblesmurf.org \
--cc=1310@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.