Date: Sun, 25 Mar 2007 12:14:01 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: "Scott I. Remick" <scott@sremick.net> Cc: freebsd-gnome@freebsd.org Subject: Re: Upgraded Gnome to 2.18, once again Vino stops authenticating Message-ID: <1174839241.68048.9.camel@shumai.marcuscom.com> In-Reply-To: <pan.2007.03.23.06.20.08@sremick.net> References: <pan.2007.03.23.06.20.08@sremick.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-vUPemi+8HK3WERUU9WdM Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2007-03-23 at 06:20 +0000, Scott I. Remick wrote: > Ugh, I have the worst luck with Vino, and it seems to happen every time I= =20 > upgrade Gnome. :( Except my fixes for last time aren't working this time.= =20 >=20 > Just upgraded Gnome from 2.16 to 2.18 on FreeBSD 6.2-PRERELEASE (it was a= =20 > late prerelease, haven't gotten around to doing -RELEASE yet). All of=20 > Gnome is upgraded to 2.18 except Ekiga since ffmpeg won't update for some= =20 > reason (so the gnome2 metaport is still at 2.16.2 but that should be fine= =20 > since all component ports are otherwise updated). >=20 > Last time part of my trouble was I was remote when I discovered the=20 > problem, which made solving things difficult but once I was local it was=20 > easy. Tonight I'm not remote, and all the standard stuff isn't working.=20 > The problem is that although the VNC client (TightVNC on a Windows XP=20 > laptop) prompts for a password (which means it's detecting vino-server=20 > running on the FreeBSD host), the password doesn't work. I've tried the=20 > following: >=20 > - portupgrade -Rf vino > - disabling then re-enabling Remote Desktop > - re-entering and changing the password > - logging out of Gnome & X and starting back up > - rebooting > - confirming in Notepad that I'm typing the correct password Besides the IPv6-only socket in the beginning, I have had no problems using vino. I, too, rely on it for accessing my amd64 machine. After the upgrade from 2.16, I didn't have to do anything (besides compile with IPv4 support) to get vino to recognize my client, and authenticate me. My /desktop/gnome/remote_access tree looks like: alternative_port : 5900 authentication_methods : [vnc] enabled : TRUE local_only : FALSE mailto : prompt_enabled : FALSE require_encryption : FALSE use_alternative_port : FALSE view_only : FALSE vnc_password : *ELIDED* Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-vUPemi+8HK3WERUU9WdM Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGBp/Jb2iPiv4Uz4cRAly0AJ9ERTvX5aIrXI0UvDh1rdA77SB0vACeMwbE N+TwwCeSF6AkqHlrWNdlL0M= =QEX5 -----END PGP SIGNATURE----- --=-vUPemi+8HK3WERUU9WdM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1174839241.68048.9.camel>