Re: XDM setup, revisited

Hauke Fath wrote:
> At 14:33 Uhr -0500 22.2.2007, <thelarsons3cox.net> wrote:
>> It simply doesn't use /etc/X11/Xresources at all.
> 
> No, it doesn't:
> 
> [haukefattie] /<1>X11/xdm > fgrep -i xresources
xdm-config
> DisplayManager*resources:      
/etc/X11/xdm/Xresources
> [haukefattie] /<1>X11/xdm >
> 
> -- xdm(1) has its own Xresources file, different from
the global one.
> 
>>  No, it's not using
>> /usr/X11R6/lib/X11/xdm/Xresources either.
> 
> What does your /etc/X11/xdm/xdm-config say?

You're right...somehow I managed to put the xdm Xresources
in the wrong 
place.  BUT xdm-config was pointed to it, so it still should
have worked 
- in theory.

Anyway, I moved the file to /etc/X11/xdm and changed the
xdm-config 
reference, so I'd have a "standard" setup again. 
Upon rebooting, I 
could no longer log in at all.  After entering the user/pass
I'd drop 
right back to the xdm screen.  There must be something else
that I 
changed a reference in because of the wrong file location,
that I need 
to change back now.

> Well, cpp has no business calling cc1 whatsoever, since
it's onla y
> preprocessor. I'd expect cc1 is called from cc which is
only a wrapper. You
> could change the first line of /etc/X11/xdm/Xsession
to

Hopefully I can ignore it then...

> #!/bin/sh -X
> 
> to get a script execution trace.

I'll have to give this a try.  Does it dump a file
somewhere?


Tim

-- 
Tim & Alethea
christtrek.org

Tim & Alethea Larson wrote:
> You're right...somehow I managed to put the xdm
Xresources in the wrong 
> place.  BUT xdm-config was pointed to it, so it still
should have worked 
> - in theory.
> 
> Anyway, I moved the file to /etc/X11/xdm and changed
the xdm-config 
> reference, so I'd have a "standard" setup
again.  Upon rebooting, I 
> could no longer log in at all.  After entering the
user/pass I'd drop 
> right back to the xdm screen.  There must be something
else that I 
> changed a reference in because of the wrong file
location, that I need 
> to change back now.

Got it back to the way it was, so I could log in.  Then
changed it back 
to "right" again, one step at a time, and it
worked.  Don't know what 
was different the 2nd time around, but oh well.


Tim

-- 
Tim & Alethea
christtrek.org