[7499] in Athena Bugs

home help back first fref pref prev next nref lref last post

dash: BadWindow

daemon@ATHENA.MIT.EDU (Craig Fields)
Wed May 1 15:03:55 1991

Date: Wed, 1 May 91 15:03:39 EDT
From: cfields@nanga-parbat.LCS.MIT.EDU (Craig Fields)
To: bugs@MIT.EDU, lnp@MIT.EDU
In-Reply-To: [7498]

Thank you... This is a known bug. It happens because dash is trying to
find out if there is already another dash running. If there is, it tells
that dash to do things rather than doing them itself, so that you don't
run multiple copies of dash.

Anyway, the way it finds another dash is to get a list of windows from
the X server, and look at them one by one to see if they belong to a
dash. If one of the windows in the list is destroyed before it looks
at it, X returns the error that that window no longer exists, and it
is this error that is not trapped. What is probably happening is you
are doing a config_console or something (which destroys a window that
dash thinks exists) more or less at the same time, and sometimes it
just doesn't quite work out right.

In your case, you know there is no prior existing dash, so looking for
another one not only occasionally causes a crash, but is also a waste
of time. So, a workaround for you until the next release (Chris
VanHaren should have this fixed for it) would be to start up with:

	(dash -run -menus /mit/lnp/dash.menus -rv &)

The -run option causes dash not to bother looking for another running
dash, avoiding the bug altogether.

Craig

home help back first fref pref prev next nref lref last post