I would say this is a bug in kdm, where the functionality of Xwilling is not finished, yet. It might be save to remove the Xwilling line from kdmrc in /opt/kde(2)/share/config Op woensdag 19 september 2001 21:21, schreef Tracer Bullet:

This is my error, but the Xwilling file is there and kdmrc calls for it properly! I don't get the errors or problems Steven speaks of either. All seems to work well, but why the error? Could this be part of my problem that the new NVIDIA update will not work?

Sep 19 11:44:16 linux kdm_config[459]: Unrecognized key 'Xwilling' at /opt/kde2/share/config/kdm/kdmrc:26

end of line Tracer --------------------------

On Wednesday 19 September 2001 01:56 pm, Greg Kondrasuk, you wrote:

...

Change "Xwilling" to "willing" in kdmrc and it should work. Apparently there was a token name change in the KDE 2.2.x parser, but the config files weren't adjusted.

On Tuesday 18 September 2001 02:07 pm, Steven T. Hatton wrote:

...

I have these in my /var/log/warn on two systems:

Sep 18 04:27:13 baldur kdm_config[8452]: Unrecognized key 'Xwilling' at /opt/kde2/share/config/kdm/kdmrc:26 Sep 18 04:27:13 baldur kdm_config[8452]: Invalid boolean value '' at /opt/kde2/share/config/kdm/kdmrc:41 Sep 18 04:27:13 baldur kdm_config[8452]: Invalid option value 'NoStars' at /opt/kde2/share/config/kdm/kdmrc:47

Are they my fault? Are they why I can't get a window manager when I do X -query hostname :2.0?

TIA,

Steven

-- Richard Bos For those who have no home the journey is endless