[Gllug] "X connection to :0.0 broken"

[Qingning Huo]

On 9/28/05, Nix <nix at esperi.org.uk> wrote:
> This is peculiar: my xclock handles deletion requests fine; the ability
> to do so is wired into Xlib these days.

So, this is just me then.

> I'd expect a clean partitioning into two cases:
>
> - XKillClient()-style kill, exit code nonzero
> - clean shutdown, exit code zero

That is correct.

> It feels like fluxbox is failing to spot the Close-ability to me. This
> seems like a really rather big bug...
>
> Time to kick up an Xnest with a copy of fluxbox under a debugger :)))

I agree that this looks like a fluxbox bug.

> > This is not a problem for xclock, but for any serious application,
> > abnormal exit from inside xlib denies the program any change to do the
> > cleanup job.  This could be a big problem for some programs.
>
> Agreed.
>

Thanks a lot.

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