The "X connection to :0.0 broken (explicit kill or server shutdown)." is normal
if you "kill" an app instead of "close". Neither should segfault. If we are
getting a fault, a backtrace with -sync should narrow it down rather quickly,
if it is related to the recent changes....
> On Thu, Jul 13, 2000 at 05:55:38AM -0400, Rick Scott wrote:
> > > BTW: I've compiled Grace 5.1.1 official release, which was
> > > running fine with a previous CVS version of LessTif. My
> > > conclusion is that in the last few days/weeks this bug has
> > > been introduced in LessTif.
> >
> > It wouldn't surprize me, with all the Vendor/BaseClass changes recently.
> > I suspect that it will be in the destruction phase of the dialog,
> > somewhere.
>
> Yes, of course.
> Well, perhaps our test/ tree is missing a suitable example.
>
> I get always some messages when trying to use 'Kill' or similar from
> my window manger on linux. So I'm not sure what crashes here.
> My fvwm2 on linux usually features 'Close' and 'Kill', but
> in difference to a remote xmgrace/motif 'Close' is not active
> on those dialogs. This seems to be different with earlier versions
> of LessTif.
>
> --
> Alexander Mai
> [EMAIL PROTECTED]
>
>
