From: Dan Nicolaescu <dann@gnu.org>
To: Wolodja Wentland <babilen@gmail.com>
Cc: 9895-done@debbugs.gnu.org
Subject: bug#9895: 24.0.90; Daemon crashes when client frame is closed
Date: Mon, 31 Oct 2011 16:22:50 -0400 [thread overview]
Message-ID: <yxqfwi83o85.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20111031114637.GA7226@asasello.local> (Wolodja Wentland's message of "Mon, 31 Oct 2011 11:46:38 +0000")
Wolodja Wentland <babilen@gmail.com> writes:
> On Fri, Oct 28, 2011 at 14:32 -0400, Dan Nicolaescu wrote:
>> Wolodja Wentland <babilen@gmail.com> writes:
>>
>> > Hi all,
>> >
>> > the emacs daemon crashes every time I am closing a client frame. The
>> > behaviour can be consistently reproduced with the following steps:
>> >
>> > 1. emacs --daemon
>>
>> When you do this, do you get a warning like:
>>
>> Warning: due to a long standing Gtk+ bug
>> http://bugzilla.gnome.org/show_bug.cgi?id=85715
>> 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.
>>
>> If yes, then you quite likely hit the Gtk+ bug mentioned above.
>
> Indeed I do. Does this imply that I cannot use the daemon functionality until
> the GTK bug has been resolved or if I recompile Emacs with
> --with-x-toolkit=lucid?
You can use it at your own risk... It is only a problem when the X11
connection dies, or when you use xkill or the window manager to kill
emacs frames, if you use C-x 5 0 it should be fine.
IMVHO people that make heavy use of --daemon should stay away from Gtk+
(and try to lobby to the Gtk+ people to fix this bug).
I am closing this bug, there are a few other instances of this bug in
the database...
prev parent reply other threads:[~2011-10-31 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 14:45 bug#9895: 24.0.90; Daemon crashes when client frame is closed Wolodja Wentland
2011-10-28 18:32 ` Dan Nicolaescu
2011-10-31 11:46 ` Wolodja Wentland
2011-10-31 20:22 ` Dan Nicolaescu [this message]
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=yxqfwi83o85.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=9895-done@debbugs.gnu.org \
--cc=babilen@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 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.