figured it out... had something listening on port 6000. very stupid of me.
sorry for all the confusion.

thanks,

vasisht


On Tue, 10 Sep 2002, Vasisht Tadigotla wrote:

>
>
> > > hi,
> > >
> > > I just upgraded my fink for jaguar and XFree86 has stopped working.
> > > I'm using the XFree86 4.2.0.1 from the XonX site. I tried to reinstall
> > > X from fink but the tarball seems to be corrupted and bzip2 fails...
> Who knows? Your report is too vague to give any advice. You need to give
>
> attached below is the error message that I get..... I don't have an X
> server running  when I get this. I think this is more suitable to the XonX
> list than this list.
>
> thanks,
>
> vasisht
>
>
>
> XFree86 Version 4.2.0.1 / X Window System
>  (protocol Version 11, revision 0, vendor release 6600)
>  Release Date: 21 August 2002
>  If the server is older than 6-12 months, or if your hardware is
>  newer than the above date, look for a newer version before
>  reporting problems. (See http://www.XFree86.Org/FAQ)
>  Operating System: Darwin
>  Using keymapping provided in /System/Library/Keyboards/USA.keymapping.
>  _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
>  _XSERVTransMakeAllCOTSServerListeners: server already running
>  Fatal server error:
>  Cannot establish any listening sockets - Make sure an X server isn't
> already running
>  OsVendorFatalError
>  AbortDDX
>  Quitting XDarwin...
>  giving up.
>  xinit: No such file or directory (errno 2): unable to connect to X server
>  xinit: No such process (errno 3): Server error.
>
>

---------------------------------------------------------------------
ce .sig n'est pas une .sig




-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners

Reply via email to