From: Glenn Morris <rgm@gnu.org>
To: Damien Cassou <damien.cassou@gmail.com>
Cc: 9674@debbugs.gnu.org
Subject: bug#9674: 24.0.90; Closing an emacsclient frame always kills daemon
Date: Wed, 05 Oct 2011 13:54:48 -0400 [thread overview]
Message-ID: <pesjn7e32v.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CA+y5gghArP_6BbEO8KHnNi0NWKSjZ50YyGM=1AgqUuidfbsCLQ@mail.gmail.com> (Damien Cassou's message of "Wed, 5 Oct 2011 14:24:53 +0200")
Damien Cassou wrote:
> - I also compiled with --with-x-toolkit=lucid, but I must have made
> something wrong as I also got the "Warning: due to a long standing
> Gtk+ bug..." error message when I started emacs.
This seems rather backward. I would have expected the issue that message
refers to to be the actual problem that you are seeing. There's no way
you can get that message in a non-GTK build. Maybe your system was
lacking the necessary libraries for a Lucid toolkit build and defaulted
to gtk? (I don't even know if that can happen.)
Please try a fresh Lucid build again, paying attention to the configure
output. Check in src/config.h that USE_GTK is not defined.
If that works, then I think it might be the same old gtk problem that
the message refers to.
If this issue affects gtk3 as well (I seem to recall it does?) then
emacs.c should also give that message for gtk3 (if it does not already).
next prev parent reply other threads:[~2011-10-05 17:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 12:24 24.0.90; Closing an emacsclient frame always kills daemon Damien Cassou
2011-10-05 15:57 ` Richard Riley
2011-10-05 16:26 ` Glenn Morris
2011-10-05 17:54 ` Glenn Morris [this message]
2011-10-06 11:28 ` bug#9674: " Damien Cassou
2011-10-06 15:17 ` Chong Yidong
2011-10-06 16:22 ` Damien Cassou
2011-10-05 21:45 ` Chong Yidong
2011-10-08 18:35 ` Michael Welsh Duggan
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=pesjn7e32v.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=9674@debbugs.gnu.org \
--cc=damien.cassou@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.