(no subject)
Rick Stevens
rstevens at vitalstream.com
Mon Dec 29 21:48:01 UTC 2003
Darkf0x wrote:
> Putty and SecureCRT bothe give this error:
>
> Using authority file /root/.Xauthority
> Writing authority file /root/.Xauthority
> Using authority file /root/.Xauthority
> Writing authority file /root/.Xauthority
>
>
> XFree86 Version 4.3.0 (Red Hat Linux 9 release: 4.3.0-2.90.43)
> Release Date: 15 August 2003
> X Protocol Version 11, Revision 0, Release 6.6
> Build Operating System: Linux 2.4.21-2.ELsmp i686 [ELF]
> Build Date: 07 November 2003
> Build Host: porky.devel.redhat.com
>
> Before reporting any problems, please make sure you are using
> the most
> recent XFree86 packages available from Red Hat by checking for
> updates
> at http://rhn.redhat.com/errata or by using the Red Hat Network
> up2date
> tool. If you still encounter problems, please file bug reports
> in the
> XFree86.org bugzilla at http://bugs.xfree86.org and/or Red Hat
> bugzilla at http://bugzilla.redhat.com
>
> Module Loader present
> OS Kernel: Linux version 2.4.20-24.9 (bhcompile at porky.devel.redhat.com)
> (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Mon Dec 1
> 11:35:51 EST 2003
> Markers: (--) probed, (**) from config file, (==) default setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> (==) Log file: "/var/log/XFree86.0.log", Time: Mon Dec 29 13:15:49 2003
> (EE) Unable to locate/open config file
> (EE) Error from xf86HandleConfigFile()
>
> Fatal server error:
> no screens found
>
> If you encounter a server crash, please report the problem by filing a
> bug
> report in the XFree86.org bugzilla at http://bugs.xfree86.org and/or Red
> Hat
> bugzilla at http://bugzilla.redhat.com/bugzilla. When filing your
> report, it
> is very important that you explain your problem in as much detail as
> possible,
> and include a complete description on how to reproduce the problem.
> After
> submitting the bug report, attach the following files as uncompressed
> individual file attachments using the bugzilla file attachment feature:
> - X server log file: /var/log/XFree86.0.log
> - Kernel log file: /var/log/messages
>
> XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> after 0 requests (0 known processed) with 0 events remaining.
You must have an X server running on your windows box, too.
Alternately you can use vncd on the Linux box and use tightVNC on your
Windows box to connect to it.
----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer rstevens at vitalstream.com -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- I.R.S.: We've got what it takes to take what you've got! -
----------------------------------------------------------------------
More information about the fedora-list
mailing list