On Thu, Apr 21, 2005 at 06:24:03AM -0500, David D. Hagood wrote:
> IF this happens when using SSH, something to check is what the actual
> settings of DISPLAY are:
>
> Normally under SSH, DISPLAY will be set to something like:
>
> DISPLAY=localhost:10
>
> and SSH will forward TCP port 6010 on t
David D. Hagood wrote:
To test this hypothesis, try setting the DISPLAY environment variable to
point directly to the computer you are using as the display (and making
sure that machine is set to allow the remote machine to use the
display), and see if the problem continues.
If it does, then my
IF this happens when using SSH, something to check is what the actual
settings of DISPLAY are:
Normally under SSH, DISPLAY will be set to something like:
DISPLAY=localhost:10
and SSH will forward TCP port 6010 on the remote machine to the local
machine's X server on port 6000.
It *could* be tha
Le jeu 21/04/2005 à 05:11, Andreas Mohr a écrit :
> Hi,
>
> On Thu, Apr 21, 2005 at 10:35:54AM +0200, Michael Riedel wrote:
> > Hi,
> >
> > I compiled wine20050419 under slackware 10.1 via tools/wineinstall.
> >
> > After starting a xterm window on a remote X11 terminal (via properly
> > initia
Hi,
On Thu, Apr 21, 2005 at 10:35:54AM +0200, Michael Riedel wrote:
> Hi,
>
> I compiled wine20050419 under slackware 10.1 via tools/wineinstall.
>
> After starting a xterm window on a remote X11 terminal (via properly
> initialized DISPLAY environment variable) I tried to start several wine
>
Hi,
I compiled wine20050419 under slackware 10.1 via tools/wineinstall.
After starting a xterm window on a remote X11 terminal (via properly
initialized DISPLAY environment variable) I tried to start several wine
progs (wcmd, winefile ...) and Windows applications (wine c:\\...) but
each time I
