Xwin stackdump while logging into RH8 with KDE as window manager

[Joel Rosi-Schwartz]

Harold,

Gave it a shot but it still core dumps. Thanks for the idea though.

- joel

Harold L Hunt II wrote:

> Joel,
>
> We had some problems a long while back with 24 and 32 bit color and 
> KDE.  Try dropping your Windows color depth to 16 bits per pixel and 
> report your results.
>
> Thanks for testing,
>
> Harold
>
> Joel Rosi-Schwartz wrote:
>
>>
>>
>> Andrew Markebo wrote:
>>
>>> What happens if you pick away the export DISPLAY? 
>>
>> No effect, it behaves the same either way. The thing is that it all 
>> works fine if the kde environment of the user logging in is virgin. 
>> Something in the KDE environment that has been configured at some 
>> point in the past is now causing a core dump on the new machines.  
>> Our old machines continue to function normally.  The ultimate 
>> solution is to simply remove our existing .kde directories and 
>> reconfigure our desktops from scratch. That is real boring work but 
>> in the end may be the simplest solution.
>>
>> - joel
>>
>>>     /Andy
>>>
>>> / Joel Rosi-Schwartz <Joel.Rosi-Schwartz@Etish.org> wrote:
>>> | I do not understand why, but both times that I attached my startX 
>>> file
>>> | it seems be unreadable. Here are the contents:
>>> |
>>> | export PATH="/usr/X11R6/bin:$PATH"
>>> | export DISPLAY=127.0.0.1:0.0
>>> |
>>> | cd c:/tmp
>>> | nohup /usr/X11R6/bin/XWin -query athena -from `hostname` 2>/dev/null&
>>> |
>>> | # I have also tried the following
>>> | # /usr/X11R6/bin/XWin -screen 0 1024 768 -engine 4 -query athena 
>>> -from
>>> | `hostname`
>>> |
>>> | - joel
>>> |
>>> |
>>>
>>>  
>>>
>>
>>
>
>