Subj : Re: DISPLAY vble: problem in Debian linux X To : comp.os.linux,comp.os.linux.x From : Saul Lubkin Date : Sun Aug 22 2004 08:41 pm You're absolutely right! Worked like a charm. :) On Sun, 22 Aug 2004, Sybren Stuvel wrote: > ["Followup-To:" header set to comp.os.linux. - please don't crosspost] > > Saul Lubkin enlightened us with: > > Now, for X-windows, running, e. g., > > > > DISPLAY=:0.0 xlogo& > > > > should -- assuming, e.g., that you're xhost commands are right, etc > > -- run xlogo on the local machine, with the window coming up on > > Computer X. Doesn't work. > > Probably because X isn't listening on a TCP port. Look for the > "-nolisten tcp" option in whatever config file you're using when > starting X, and remove it. Just do 'ps awx | grep X' and you'll see > the 'nolisten' option. > > > E.g., even on the LOCAL machine, running > > > > DISPLAY=:0.0 xlogo& -- > > > > or > > > > DISPLAY=localhost:0.0 xlogo& > > > > or various modifications thereof all fail, with the error message > > "Unable to open display". > > Indeed, sounds like it. > > > > to the newsgroup -- I read the group less often than I should, due > > to time constraints. I'll post a summary of all relevant answers -- > > including the eventual solution that works -- to the group, no > > matter what> > > Nope. If you ask a question in public, read the answer in public. If > you can't be arsed to come back here and read the answer someone is > giving you in their spare time just out of kindness, you're in the > wrong business. > > Sybren > -- > The problem with the world is stupidity. Not saying there should be a > capital punishment for stupidity, but why don't we just take the > safety labels off of everything and let the problem solve itself? > .