Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Oct 2007 09:14:14 -0400
From:      Lisandro Grullon <lisandrogrullon07@hotmail.com>
To:        David van Kuijk <dj.vankuijk@chello.nl>, <freebsd-questions@freebsd.org>
Subject:   RE: Problem with VNC on AMD64
Message-ID:  <BAY116-W51416FEAB63AF96DFC140A99F0@phx.gbl>
In-Reply-To: <4718A0EE.6030804@chello.nl>
References:  <4718A0EE.6030804@chello.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi David,
I have been experiencing some issues with VNC myself and after a few tries =
I decided to give up on it, I am stock back into shell mode, but that's fin=
d hence the machie most of the time is close to me. in any way, i am confid=
ent someone here would be able to help you, yet the problems I experience i=
f i recall correctly were similar to the ones you outline in your log. Lisa=
ndro Grullon



> Date: Fri, 19 Oct 2007 14:19:58 +0200
> From: dj.vankuijk@chello.nl
> To: freebsd-questions@freebsd.org
> Subject: Problem with VNC on AMD64
>=20
> Hi
>=20
> I have been using FreeBSD for several years now on intel32. Now I=20
> installed it on my new server which is a AMD64. Most things go well, but=
=20
> I can't get a Window Manager working under VNC anymore. Here you find=20
> the VNC log:
>=20
> ---------------------------------------------------
> Xvnc Free Edition 4.1.2 - built Oct 21 2006 03:26:51
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
> Underlying X server release 40300000, The XFree86 Project, Inc
>=20
>=20
> Fri Oct 19 08:13:28 2007
>   vncext:      VNC extension running!
>   vncext:      Listening for VNC connections on port 5901
>   vncext:      Listening for HTTP connections on port 5801
>   vncext:      created VNC server for screen 0
> Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/,=20
> removing from list!
> Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing=
=20
> from list!
> wmaker fatal error: it seems that there is already a window manager runni=
ng
> --------------------------------------------------------
>=20
> So VNC server will run, and I can connect to it from a VNC-client, but=20
> the window manager fails to start correctly.
>=20
> I've tried a different window manager (TWM), but here a similar error=20
> message occurs:
> twm:  another window manager is already running. on screen 0?
> twm:  unable to find any unmanaged video screens.
>=20
>=20
> Anybody suggestions how I can solve this?
>=20
> Greetings,
> David
>=20
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o=
rg"

_________________________________________________________________
Boo!=A0Scare away worms, viruses and so much more! Try Windows Live OneCare=
!
http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=3Dwl_hotma=
ilnews=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY116-W51416FEAB63AF96DFC140A99F0>