From: TsanChung on 20 Nov 2009 19:30
On Oct 8, 3:53 pm, Allen Kistler <ackist...(a)oohay.moc> wrote:
> TsanChung wrote:
> > On Oct 7, 7:51 pm, Allen Kistler <ackist...(a)oohay.moc> wrote:
> >> TsanChung wrote:
> >>> On the root shell of Konsole on ubuntu 8.04.
> >>> #DISPLAY=localhost:0.0
> >>> # xclock
> >>> Error: Can'topendisplay: localhost:0.0
> >>> [snip]
> >> [snip]
> > I followed your instructions to edit /etc/hosts as follows but the
> > problem still exists.
> > 127.0.0.1 localhost
> > ::1 localhost
> > 127.0.1.1 tc-desktop
> > # The following lines are desirable for IPv6 capable hosts
> > #::1 ip6-localhost ip6-loopback
> > ...
> > I am using gvim on the root shell of Konsole on ubuntu 8.04, I am not
> > using ssh. I experiment with xhost because I want to solve the
> > "cannotopendisplay" problem.
> Sorry. I missed your mention of Konsole the first time. I got
> distracted byDISPLAY=localhost:0.0.
> So now I'm wondering why you setDISPLAY. It should have already been
> :0.0 (i.e., no localhost hostname), which is the correct value for
> someone at the console.
> If you justopena terminal window and "echo $DISPLAY" then what do you
> get? If you don't setDISPLAYfirst, does xclock or gvim give an error
> then? They should just work without changingDISPLAY.
I use Konsole 1.6.6 on KDE 3.5.10 & kubuntu 8.04.
The regular (non-root) console on Konsole is ok:
$ echo $DISPLAY
The root console on Konsole cannot start xclock:
# echo $DISPLAY
Invalid MIT-MAGIC-COOKIE-1 keyError: Can't open display: :0