Net Llama wrote:
Greetings,
I built XFree86-4.2.0 from source this morning. I had been running
XFree86-4.1.0 for several months. THe build went swimmingly in about 45
minutes.
However, something isn't quite right somewhere, and i can't figure out
why at the moment. If I attempt to
Had this too. found I had a typo in the /etc/profile file.
ALSO ONCE THE MONITOR SETUP IN THE
/ETC/ZX11/XFCONFIG-4 FILE
cheers
--
Rick Sivernell
Dallas, Texas 75287
972 306-2296
[EMAIL PROTECTED]
Caldera Open Linux eWorkStation 3.1
Registered Linux User
.~.
/ v \
/( _ )\
^ ^
In
--- Tim Wunder [EMAIL PROTECTED] wrote:
Net Llama wrote:
Greetings,
I built XFree86-4.2.0 from source this morning. I had been running
XFree86-4.1.0 for several months. THe build went swimmingly in
about 45
minutes.
However, something isn't quite right somewhere, and i can't figure
--- Rick Sivernell [EMAIL PROTECTED] wrote:
Had this too. found I had a typo in the /etc/profile file.
A typo that wouldn't effect XFree86-4.1.0, but XFree86-4.2.0? Also, i
haven't touched /etc/profile since 2/16/00.
ALSO ONCE THE MONITOR SETUP IN THE
/ETC/ZX11/XFCONFIG-4 FILE
This
Previously, Net Llama chose to write:
--- Tim Wunder [EMAIL PROTECTED] wrote:
Net Llama wrote:
Greetings,
I built XFree86-4.2.0 from source this morning. I had been running
XFree86-4.1.0 for several months. THe build went swimmingly in
about 45
minutes.
However, something
All of the files in /etc/X11/gdm (including gdmrc) have not been changed
in nearly a year. I just wish I had more of an error to go on than just
that stupid respawning one.
--- Tim Wunder [EMAIL PROTECTED] wrote:
Can you try xdm or maybe update gdm? Maybe something's wrong with gdm
(as I
I was thinking that your .xsession-errors file might contain a clue, but that
doesn't come into play until you log in, I think...
It IS possible that there's something specific to gdm and X 4.2.0 that's
causing the problem. Because a file hasn't changed doesn't mean that
something within it
--- Tim Wunder [EMAIL PROTECTED] wrote:
I was thinking that your .xsession-errors file might contain a clue,
but that
doesn't come into play until you log in, I think...
Correct.
It IS possible that there's something specific to gdm and X 4.2.0
that's
causing the problem. Because a