[Gllug] "X connection to :0.0 broken"

[Qingning Huo]

On 9/27/05, Rev Simon Rumble <simon at rumble.net> wrote:
>
> On 27/9/2005, "Qingning Huo" <qingninghuo at gmail.com> wrote:
>
> >Did you mean killed by a signal?  I think the window manager (fluxbox
> >here) should send some X event to the X clients.  And, strace does not
> >show any signal received.  What strace does show is:
>
> I don't think the window manager sends a signal, I think it just closes
> the socket to the client.

As I understand, the socket is a connection to the X server, instead of
the window manager.

> >It seems that fd=3 (a unix stream socket to /tmp/.X11-unix/X0) is
> >closed.  That's why it said "X connection to :0.0 broken".  But why
> >does it happen randomly?
>
> I don't think it's random, I think it's when you use the WM's close
> button rather than the one inside the application.

The X client here is xclock.  There is no button inside the application,
nor any menus.  Try this:

xclock && echo ok

I get different results randomly.

> But I'm no X guru.  Maybe there's one around?
>

Anybody?
-- 
Gllug mailing list  -  Gllug at gllug.org.uk
http://lists.gllug.org.uk/mailman/listinfo/gllug