From: Dmitry Antipov <dmantipov@yandex.ru>
To: Ken Raeburn <raeburn@permabit.com>
Cc: 17975@debbugs.gnu.org
Subject: bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too)
Date: Mon, 14 Jul 2014 11:23:36 +0400 [thread overview]
Message-ID: <53C38578.7020207@yandex.ru> (raw)
In-Reply-To: <F994ADA9-E2B2-440A-BCFB-F717B56EECC4@permabit.com>
On 07/14/2014 09:13 AM, Ken Raeburn wrote:
> Would it not be enough to do a similar canonicalization of $DISPLAY
> and the make-frame-on-display argument, if that was enough in emacsclient?
Probably no - the following example also crashes:
./src/emacs -Q --eval '(let ((f (selected-frame))) (make-frame-on-display ":1.0") (delete-frame f))'
where :1.0 is Xnest running on the same machine.
> I don't think it would be practical for me to run a patched X11 at work. I was going to run a test at home,
> but my home GNU/Linux setup (Debian "wheezy" distro) seems to have a newer X11 package (1.5.0, with patches
> including ximcp/imLcPrs.c and imTrX.c but not imInsClbk.c) than the one at work (Ubuntu "precise" distro,
> 1.4.99.1 with patches), and I haven't been able to reproduce the problem yet.
I tried both stock Fedora 20 libX11-1.6.1 and 1.6.2 recompiled from rawhide,
and was able to reproduce with both.
This mess raises up an old question: should Emacs treat localhost:0/unix:0/:0.0/:0 etc.
like the same display and has the only connection for all of them? It was discussed a long
time ago, at least at http://lists.gnu.org/archive/html/emacs-devel/2011-10/msg00363.html.
Dmitry
next prev parent reply other threads:[~2014-07-14 7:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 19:59 bug#17975: 24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too) Ken Raeburn
2014-07-09 5:37 ` Dmitry Antipov
2014-07-11 21:22 ` Ken Raeburn
2014-07-13 5:43 ` Dmitry Antipov
2014-07-13 10:49 ` Dmitry Antipov
2014-07-13 10:56 ` Dmitry Antipov
2014-07-13 15:04 ` Eli Zaretskii
2014-07-13 15:54 ` Dmitry Antipov
2014-07-13 16:35 ` Eli Zaretskii
2014-07-13 18:01 ` Dmitry Antipov
2014-07-13 18:28 ` Eli Zaretskii
2014-07-14 5:20 ` Dmitry Antipov
2020-09-09 11:35 ` Lars Ingebrigtsen
2020-09-09 11:28 ` Lars Ingebrigtsen
2020-09-11 10:11 ` Dmitry Antipov
2020-09-11 12:54 ` Lars Ingebrigtsen
2020-09-11 13:01 ` Eli Zaretskii
2014-07-14 5:13 ` Ken Raeburn
2014-07-14 7:23 ` Dmitry Antipov [this message]
2014-07-14 8:10 ` Jan Djärv
2014-07-14 10:19 ` Dmitry Antipov
2014-07-14 18:58 ` Ken Raeburn
2016-04-13 18:19 ` Ken Raeburn
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=53C38578.7020207@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=17975@debbugs.gnu.org \
--cc=raeburn@permabit.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 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).