From owner-freebsd-questions@FreeBSD.ORG Tue Jul 17 13:46:37 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD26116A401 for ; Tue, 17 Jul 2007 13:46:37 +0000 (UTC) (envelope-from andrewgould@yahoo.com) Received: from web35308.mail.mud.yahoo.com (web35308.mail.mud.yahoo.com [66.163.179.102]) by mx1.freebsd.org (Postfix) with SMTP id 9949513C4A6 for ; Tue, 17 Jul 2007 13:46:37 +0000 (UTC) (envelope-from andrewgould@yahoo.com) Received: (qmail 45057 invoked by uid 60001); 17 Jul 2007 13:46:36 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=MzjtR1QVomBhU70RIijws9APXvc+RHKx52TnWyK/muqLGKbaTQJOB3dR3m1EK9o2ZKZV/Vc5tol3ho/YPqRHn8DUfnMNmS7/RDH66uPS6ySdb4Coa+KqB/3MT4ASN8x8KbtGKM3xHUpQcysWmN6/GI+whv2H8Ye9iII0IHTsuSs=; X-YMail-OSG: N77s8AQVM1motN9zOxbzSnFQxHfQ8.aVM6it71C5ZZ6GK2_NoY4KqMnZpfLjSLdFoUvvufdUCw-- Received: from [204.115.94.51] by web35308.mail.mud.yahoo.com via HTTP; Tue, 17 Jul 2007 06:46:36 PDT X-Mailer: YahooMailRC/651.41 YahooMailWebService/0.7.41.16 Date: Tue, 17 Jul 2007 06:46:36 -0700 (PDT) From: Andrew Gould To: FreeBSD Questions Mailing List MIME-Version: 1.0 Content-Type: text/plain; charset=ascii Message-ID: <853508.44670.qm@web35308.mail.mud.yahoo.com> Subject: tightvnc trouble X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jul 2007 13:46:37 -0000 Approximately 2 weeks ago, I performed a fresh installation of FreeBSD 6.2, updated to STABLE world and kernel, deleted all packages and installed up-to-date versions of packages. The upgrade to xorg 7.2 was uneventful. (whew) After using tightvnc, the user that started vncserver is unable to access an X window locally, even after killing vncserver and rebooting. All I get is a grey screen with a black crosshair until xinit gives up with the messages below. The first section is repeated several times before the program gives up. #####messages begin##### AUDIT: Tue Jul 17 08:34:12 2007: 853 X: client 1 rejected from local host (uid 1002) Xlib: connection to ":0.0" refused by server Xlib: No protocol specified .. giving up. xinit: unable to connect to X Server waiting for X server to shut down ..FreeFontPath: FPE "/usr/local/lib/X11/fonts/misc" refcount is 2, should be 1, fixing. xinit: Server error. #####end of messages##### After this happened, I had to remove and recreate the user to get X working again. Root, who never executed vncserver, was able to use X before and after tightvnc was used. To recreate this scenario, I created a new user, "vncguest", with a .xinitrc file containing only one line: "startkde". Vncserver was started using the default options (twm, etc). After remote access was opened and closed, vncguest has been unable to use X. My normal user can still use X (kde). Any advice? Thanks, Andrew