Bug#446628: emacs: crashes after opening frame on a different display

Bug#446628: emacs: crashes after opening frame on a different display

[Rob Browning]

(If possible, please preserve the 446628-forwarded@bugs.debian.org
 address in any replies.)

Yair Yarom <irush@cs.huji.ac.il> writes:

> After opening a frame on a different display: make-frame-on-display,
> when the other display is shutdown (e.g. logout, or X crash), the
> emacs crashes over xcb assertion:
>
>   emacs: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed
>
> This happens even if the emacs window on the remote display was
> closed before the logout.

I can verify this with the current emacs22 (based on Emacs 22.1)
package via Xnest.

In order to reproduce:

  - Run "Xnest :2" or similar.
  - Launch emacs on the host.
  - Run make-frame-on-display and specify :2.
  - Within Xnest, issue a C-x 5 0.
  - Close Xnest.

Here at least, Emacs will then crash with a segmentation fault.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: Bug#446628: emacs: crashes after opening frame on a different display

[Richard Stallman]

Would someone please DTRT and ack?

To: bug-gnu-emacs@gnu.org
From: Rob Browning <rlb@defaultvalue.org>
Date: Fri, 23 Nov 2007 15:57:59 -0800
In-Reply-To: <20071014140940.8267.15697.reportbug@mantis.cs.huji.ac.il> (Yair
	Yarom's message of "Sun\, 14 Oct 2007 16\:09\:40 +0200")
Message-ID: <871wagfraw.fsf@raven.defaultvalue.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Yair Yarom <irush@cs.huji.ac.il>, 446628@bugs.debian.org,
	446628-forwarded@bugs.debian.org
Subject: Re: Bug#446628: emacs: crashes after opening frame on a different
	display

(If possible, please preserve the 446628-forwarded@bugs.debian.org
 address in any replies.)

Yair Yarom <irush@cs.huji.ac.il> writes:

> After opening a frame on a different display: make-frame-on-display,
> when the other display is shutdown (e.g. logout, or X crash), the
> emacs crashes over xcb assertion:
>
>   emacs: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed
>
> This happens even if the emacs window on the remote display was
> closed before the logout.

I can verify this with the current emacs22 (based on Emacs 22.1)
package via Xnest.

In order to reproduce:

  - Run "Xnest :2" or similar.
  - Launch emacs on the host.
  - Run make-frame-on-display and specify :2.
  - Within Xnest, issue a C-x 5 0.
  - Close Xnest.

Here at least, Emacs will then crash with a segmentation fault.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: Bug#446628: emacs: crashes after opening frame on a different display

[Jan Djärv]

IMHO, TRT is to do nothing.  The xcb-xib binding is not used much.  And I 
think if xcb-xlib are to be a drop in replacement for libX11, then errors that 
don't happen with libX11 should not happen in the xcb-xlib binding.

	Jan D.


Richard Stallman skrev:
> Would someone please DTRT and ack?
> 
> To: bug-gnu-emacs@gnu.org
> From: Rob Browning <rlb@defaultvalue.org>
> Date: Fri, 23 Nov 2007 15:57:59 -0800
> In-Reply-To: <20071014140940.8267.15697.reportbug@mantis.cs.huji.ac.il> (Yair
> 	Yarom's message of "Sun\, 14 Oct 2007 16\:09\:40 +0200")
> Message-ID: <871wagfraw.fsf@raven.defaultvalue.org>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Cc: Yair Yarom <irush@cs.huji.ac.il>, 446628@bugs.debian.org,
> 	446628-forwarded@bugs.debian.org
> Subject: Re: Bug#446628: emacs: crashes after opening frame on a different
> 	display
> 
> (If possible, please preserve the 446628-forwarded@bugs.debian.org
>  address in any replies.)
> 
> Yair Yarom <irush@cs.huji.ac.il> writes:
> 
>> After opening a frame on a different display: make-frame-on-display,
>> when the other display is shutdown (e.g. logout, or X crash), the
>> emacs crashes over xcb assertion:
>>
>>   emacs: xcb_xlib.c:41: xcb_xlib_lock: Assertion `!c->xlib.lock' failed
>>
>> This happens even if the emacs window on the remote display was
>> closed before the logout.
> 
> I can verify this with the current emacs22 (based on Emacs 22.1)
> package via Xnest.
> 
> In order to reproduce:
> 
>   - Run "Xnest :2" or similar.
>   - Launch emacs on the host.
>   - Run make-frame-on-display and specify :2.
>   - Within Xnest, issue a C-x 5 0.
>   - Close Xnest.
> 
> Here at least, Emacs will then crash with a segmentation fault.
>