Re: Problem with VNC on AMD64
Hi Josh and others Has anybody been able to solve this problem yet? I pulled in a friend who has a zillion years of experience with BSD and was not able to solve the problem. It looks like it is not even possible to start the X when the machine has a monitor attched to it. I installed FreeBSD 7.0 Beta with xorg 7.3.1, but there the problem seems to be the same... Greetings, D ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with VNC on AMD64
> vnc-4.1.2_2 from ports. I wonder if this is related to it compiling > against ancient XFree86 source? The tightvnc port has the same problem, actually. Same message in the vnc log, but also another: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Value in failed request: 0x3c Serial number of failed request: 6 Current serial number in output stream: 8 Xlib: sequence lost (0x1 > 0x8) in reply type 0x0! X Error of failed request: 0 Major opcode of failed request: 0 () Serial number of failed request: 0 Current serial number in output stream: 8 Would it matter that the window manager itself is linked against/compiled against X.org, while these VNC ports use old XFree86? I wouldn't think so, unless Xlib is different enough. Perhaps this should be posted to freebsd-x11 instead? Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with VNC on AMD64
> What version of VNC are you running.. ? vnc-4.1.2_2 from ports. I wonder if this is related to it compiling against ancient XFree86 source? Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with VNC on AMD64
What version of VNC are you running.. ? Anyone here tried Ultra VNC ? Thanks Hakan http://dominor.com On 10/28/07, Josh Carroll <[EMAIL PROTECTED]> wrote: > > > So VNC server will run, and I can connect to it from a VNC-client, but > > the window manager fails to start correctly. > > I am having the same problem. My vnc log looks similar: > > *snip* > X Error of failed request: BadValue (integer parameter out of range > for operation) > Major opcode of failed request: 102 (X_ChangeKeyboardControl) > Value in failed request: 0x3c > Serial number of failed request: 7 > Current serial number in output stream: 9 > /usr/local/bin/wmaker fatal error: it seems that there is already a > window manager running > > Of course, there's no window manager running (I get the default X gray > screen with a generic X cursor). > > If I try to run wmaker against the VNC display, I get the same message: > > % wmaker -display localhost:1 > wmaker fatal error: it seems that there is already a window manager > running > > Like you, I've tried other window managers, but I have the same > problem. I'll wait to see if anyone has any ideas, otherwise I'm going > to go ahead and submit a PR for this. > > Josh > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem with VNC on AMD64
> So VNC server will run, and I can connect to it from a VNC-client, but > the window manager fails to start correctly. I am having the same problem. My vnc log looks similar: *snip* X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Value in failed request: 0x3c Serial number of failed request: 7 Current serial number in output stream: 9 /usr/local/bin/wmaker fatal error: it seems that there is already a window manager running Of course, there's no window manager running (I get the default X gray screen with a generic X cursor). If I try to run wmaker against the VNC display, I get the same message: % wmaker -display localhost:1 wmaker fatal error: it seems that there is already a window manager running Like you, I've tried other window managers, but I have the same problem. I'll wait to see if anyone has any ideas, otherwise I'm going to go ahead and submit a PR for this. Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Problem with VNC on AMD64
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 find hence the machie most of the time is close to me. in any way, i am confident someone here would be able to help you, yet the problems I experience if i recall correctly were similar to the ones you outline in your log. Lisandro Grullon > Date: Fri, 19 Oct 2007 14:19:58 +0200 > From: [EMAIL PROTECTED] > To: freebsd-questions@freebsd.org > Subject: Problem with VNC on AMD64 > > Hi > > I have been using FreeBSD for several years now on intel32. Now I > installed it on my new server which is a AMD64. Most things go well, but > I can't get a Window Manager working under VNC anymore. Here you find > the VNC log: > > --- > 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 4030, The XFree86 Project, Inc > > > 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/, > removing from list! > Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing > from list! > wmaker fatal error: it seems that there is already a window manager running > > > So VNC server will run, and I can connect to it from a VNC-client, but > the window manager fails to start correctly. > > I've tried a different window manager (TWM), but here a similar error > message occurs: > twm: another window manager is already running. on screen 0? > twm: unable to find any unmanaged video screens. > > > Anybody suggestions how I can solve this? > > Greetings, > David > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" _ Boo! Scare away worms, viruses and so much more! Try Windows Live OneCare! http://onecare.live.com/standard/en-us/purchase/trial.aspx?s_cid=wl_hotmailnews___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
