I *think* (hope) you're running into what I've worked on before. It's in the archives...
http://archives.neohapsis.com/archives/openbsd/2007-11/0691.html -----Original Message----- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of Dr. Harry Knitter Sent: Wednesday, March 04, 2009 3:39 AM To: misc@openbsd.org Subject: Problems with vnc on OpenBSD 4.4 Hello, I have successfully set um an OpenBSD machine (amd64) in an Virtualbox using X and KDE as desktop. So far everything works fine, KDE is starting after boot. tightvnc is installed. However I cannot start vncserver. <log> The log file shows: Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb' Getting interface configuration (4): Device not configured 04/03/09 11:05:13 Xvnc version 3.3.tight1.2.9 04/03/09 11:05:13 Copyright (C) 1999 AT&T Laboratories Cambridge. 04/03/09 11:05:13 Copyright (C) 2000-2002 Constantin Kaplinsky. 04/03/09 11:05:13 All Rights Reserved. 04/03/09 11:05:13 See http://www.uk.research.att.com/vnc for information on VNC 04/03/09 11:05:13 See http://www.tightvnc.com for TightVNC-specific information 04/03/09 11:05:13 Desktop name 'X' (openbsd.mydomain.com:1) 04/03/09 11:05:13 Protocol version supported 3.3 04/03/09 11:05:13 Listening for VNC connections on TCP port 5901 04/03/09 11:05:13 Listening for HTTP connections on TCP port 5801 04/03/09 11:05:13 URL http://openbsd.mydomain.com:5801 xrdb: Can't open display ':1' xset: unable to open display ":1" xsetroot: unable to open display ':1' startkde: Starting up... ksplash: cannot connect to X server :1 xprop: unable to open display ':1' usage: xprop [-options ...] [[format [dformat]] atom] ... where options include: -grammar print out full grammar for command line -display host:dpy the X server to contact -id id resource id of window to examine -name name name of window to examine -font name name of font to examine -remove propname remove a property -set propname value set a property to a given value -root examine the root window -len n display at most n bytes of any property -notype do not display the type field -fs filename where to look for formats for properties -frame don't ignore window manager frames -f propname format [dformat] formats to use for property of given name -spy examine window properties forever kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. kded: cannot connect to X server :1 kded: ERROR: KUniqueApplication: Registering failed! kded: ERROR: Communication problem with kded, it probably crashed. kcminit_startup: cannot connect to X server :1 ksmserver: cannot connect to X server :1 startkde: Shutting down... klauncher: Exiting on signal 1 sound server terminated startkde: Running shutdown scripts... xprop: unable to open display ':1' usage: xprop [-options ...] [[format [dformat]] atom] ... where options include: -grammar print out full grammar for command line -display host:dpy the X server to contact -id id resource id of window to examine -name name name of window to examine -font name name of font to examine -remove propname remove a property -set propname value set a property to a given value -root examine the root window -len n display at most n bytes of any property -notype do not display the type field -fs filename where to look for formats for properties -frame don't ignore window manager frames -f propname format [dformat] formats to use for property of given name -spy examine window properties forever startkde: Done. </log> starting xhost from a Terminal within KDE as ordinary user shows: <xhost> access control enabled, only authorized clients can connect <xhost> environment variable DISPLAY is set to :0.0 xauth shows MIT_MAGIC_COOKIES_1 for localhost and the fqdn of the machine. However, vncserver cannot connect. Trying to call xhost within a ssh-shell (as ordinary user) also xhost cannot connect to X, regardless what command line argument I use. What the hell ist going wrong? Thanks for any answers that can solve the problem. Greetings Harry
