GNU bug report logs - #17975
24.3.92; assertion failure deleting frames with varying names for the same display (and, using multiple X11 connections in that case too)

Previous Next

Package: emacs;

Reported by: Ken Raeburn <raeburn <at> permabit.com>

Date: Wed, 9 Jul 2014 01:57:01 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3.92

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 17975 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Antipov <dmantipov <at> yandex.ru>
To: Ken Raeburn <raeburn <at> permabit.com>
Cc: 17975 <at> debbugs.gnu.org
Subject: Re: 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: Wed, 09 Jul 2014 09:37:49 +0400
[Message part 1 (text/plain, inline)]
On 07/08/2014 11:59 PM, Ken Raeburn wrote:

> This is a simplified version of a crash I got using emacsclient, daemon
> mode, and desktop-save-mode. My saved desktop configuration somehow has
> frames with different names for the same local display, perhaps because
> window manager buttons I use to invoke emacsclient cause ":0.0" to be
> used, and my xterm shells have DISPLAY set to ":0".
>
> Emacs is compiled with "--enable-checking --with-x-toolkit=lucid".
>
> Recipe:
>   1. emacs -Q --daemon
>   2. DISPLAY=:0 emacsclient -c -n
>   3. DISPLAY=:0.0 emacsclient -c -n
>   4. Use	a window-manager button	to delete the first Emacs window.
>   5. Emacs crashes with an assertion failure.

Reproduced. The whole thing looks like a mystery (perhaps Xlib makes a
difference between :0 and :0.0 somewhere in its innards), but this
workaround works for me. Can you please try it too?

Dmitry


[bug17975.patch (text/x-patch, attachment)]

This bug report was last modified 4 years and 252 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.