Date: Thu, 22 Jun 2006 16:04:34 +0300 From: "Alex Savovski" <savovski@gmail.com> To: greg.lane@internode.on.net Cc: amd64@freebsd.org, questions@freebsd.org Subject: Re: Does anyone run VNC with 64-bit FreeBSD (amd64)? Message-ID: <10a002530606220604m5de5d7b0lfa1e779a16096cb7@mail.gmail.com> In-Reply-To: <20060622075236.GA95258@router.lane.family> References: <20060622075236.GA95258@router.lane.family>
next in thread | previous in thread | raw e-mail | index | archive | help
I have the same ,problem,But I have never run on other version,I use RELENG_6_1, AMD64 On 6/22/06, Greg Lane <greg.lane@internode.on.net> wrote: > > G'day everyone, > > I recently had to replace a disk and took the opportunity to > upgrade from 5-stable to 6-stable. I also changed from the > 32-bit to the 64-bit version. I have a dual Opteron server. > > VNC installed from ports (4.2.1) doesn't work on the 64-bit machine. > The same version installed on my home machine (32-bit) with the .vnc > directory copied over exactly from my work 64-bit machine runs fine. > So in what sense does it fail.... > > If I create a blank .vnc/xstartup, then I get the usual grey screen. > Then if I try and run X commands on that display, some work, like > xsetroot -solid blue, but others, xterm, icewm, twm, etc don't. > > 130>~/.vnc$ icewm -display :9 > IceWM: using /home/xxxxxx/.icewm for private configuration files > X Error of failed request: BadValue (integer parameter out of range for > operation) > Major opcode of failed request: 2 (X_ChangeWindowAttributes) > Value in failed request: 0x0 > Serial number of failed request: 9 > Current serial number in output stream: 10 > > 131>~/.vnc$ xterm -display :9 > X Error of failed request: BadValue (integer parameter out of range for > operation) > Major opcode of failed request: 1 (X_CreateWindow) > Value in failed request: 0x21 > Serial number of failed request: 41 > Current serial number in output stream: 49 > > If they are in the xstartup file they give the exact same errors in > the vnc log file. I was only running them interactively above > to troubleshoot it. Google has failed me for once, so I seek > your experience and advice... > > Greg > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10a002530606220604m5de5d7b0lfa1e779a16096cb7>