I'm not talking about a remote situation - I'm talking about local
root. I'll clarify with an example.
If you're logged into your Linux box as a non-root user running KDE, an
Ethereal window running as root (via sudo, su, whatever) will not appear
on the local display unless you make the change I described -- on SuSE
9.1 :).
Maybe it's a root thing - the connection is apparently being made via
TCP on the loopback. Or they're blocking the domain sockets, too,
although I doubt that.
Local apps run as the same user that owns the display are not a
problem. I only mention this because of the privileges required to run
Ethereal. Anyway, sorry to veer off-topic.
Guy Harris wrote:
Scott Lowrey wrote:
One caveat here: some Linux systems have port 6000 disabled by
default. If you're used to running X apps in "the usual way", you'll
go nuts wondering why nothing (including xhost) works.
If you're running the app locally, rather than running it on some
other machine with DISPLAY set to point to your desktop machine, if
DISPLAY is set to ":0.0" that shouldn't matter, as it'll be connecting
via a UNIX-domain socket rather than via a TCP connection to port 6000.
If you *are* running it on some other machine, of course, your
machine's X server has to be listening on port 6000 - and you might
have to use "xhost" locally to get it to accept connections from the
remote machine in question.
If you're running Ethereal locally as root (to enable capturing on
platforms where that's required), you might also have to use "xhost"
to allow connections from root.
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users
