Michael,
> > The most embarrassing thing for me is that all other users can run VNC
> > with the same configuration files...
>
> That's pretty strange unless you have a problem with your XAUTHORITY
> environment variable or .Xauthority file. Perhaps one of these is
> getting modified by your s
On Thu, Feb 28, 2002 at 09:22:30AM -0800, Alexey Koptsevich wrote:
>
> Yes, xstartup triggers script, but exactly the same occurs when I replace
> xstartup with the default one. I think the problem is in the strings like
>
> AUDIT: Thu Feb 28 20:19:24 2002: 76400 Xvnc: client 1 rejected from lo
Hello,
> It looks like the xstartup script is triggering a login script of some
> kind. Perhaps there is a shell rc file which includes stty and such
> (that probably ought to only be executed by a login shell). Try using
> Xvnc directly (rather than the vncserver script) and see if that works.
On Tue, Feb 26, 2002 at 07:58:34PM -0800, Alexey Koptsevich wrote:
>
> 27/02/02 06:51:28 Xvnc version 3.3.3r2
> 27/02/02 06:51:28 Copyright (C) AT&T Laboratories Cambridge.
> 27/02/02 06:51:28 All Rights Reserved.
> 27/02/02 06:51:28 See http://www.uk.research.att.com/vnc for information on VNC
>
> > Hello,
> >
> > I have a problem which I cannot attribute to anything. I myself cannot run
> > vncserver on a particular host, whereas all other users can. Login
> > procedures are highly standardized on this host, so I cannot imagine the
> > source of the problem. I attach the beginning of th
On Wed, 27 Feb 2002 16:08:21 -0800 (PST)
Alexey Koptsevich <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a problem which I cannot attribute to anything. I myself cannot run
> vncserver on a particular host, whereas all other users can. Login
> procedures are highly standardized on this host, so
