T.R | Title | User | Personal Name | Date | Lines |
---|
9079.1 | | SEPPLT::MARK | Mark Garrett | Mon Mar 10 1997 04:55 | 24 |
| xhost as you know opens a connection with the current display
so find out what that display is
echo $DISPLAY
then get some info on what display we are talking to
xdpyinfo
I have never seen xhost dump core other may have. Can I see the
core file that was produced?
I is most likely something odd about the DISPLAY variable or the display
in question that it points at. Was xhost being used to change access or with no
paramaters to display the current access. Maybe the current access info has been
stuffed so also do the following
xauth
xauth> list
Hope this helps
Cheers
Mark :)
|
9079.2 | try this | HYDRA::DONSBACH | Jeff Donsbach, Software Partner Engineering, DTN 297-6862 | Mon Mar 10 1997 12:49 | 12 |
|
If the machine is a workstation, look to see the special device
/dev/esl is NOT there (unless they have a E&S Freedom graphics board
which is very unlikely). If the special device file is there, remove
it and try again. The presence of this device special file when
you don't have an E&S boards causes lots of weird core dumps related
to programs that use X depending on what they try to do. I'm not
totally sure it will solve this particulat problem, but it can't hurt
to try...
Jeff D.
|
9079.3 | not the same bug | GERUND::WOLFE | I'm going to huff, and puff, and blow your house down | Tue Mar 18 1997 22:21 | 5 |
| The bug mentioned in .2 is only seen when running dxsysinfo
on systems with the E&S device driver. It is in not a general issue
that effects other apps - especially not xhosts.
Pete
|