Re: emacs --daemon and GDK default display

[Jan Djärv]

Ulrich Mueller skrev:
> > > > > > On Tue, 17 Mar 2009, Jason Rumney wrote:
> > > While I think that the blame is with libcanberra, I'm confused
> > > about the fact that the segfault only happens during the second
> > > request from a client. Does it mean that there is a GDK default
> > > display at the time of the first request, but not for the second
> > > one? Why?
>
> > Just a guess without looking at libcanberra, but could the bug be
> > that libcanberra remembers the default display created during the
> > first request and tries to reuse it after it is closed?
>
> It doesn't remember it. libcanberra just calls a GTK function, which
> in turn asks the GDK display manager for the default display. And that
> returns a valid display for the first request, but a null pointer for
> the second one.

If I remember correctly, the display manager does not set a new default 
display when the old is closed.  There is some code for that case i gtkutil.c.

But there was a bug in it.  I don't know if that fixes anything, but please 
try again.  Note that closing displays under Gtk+ is generally buggy in 
itself.  If you can capture a stack trace in the debugger we should be able to 
tell if it is Gtk+ or Emacs that is doing the wrong thing.

        Jan D.