work right yet. This needs other eyes to look at in order for me to figure
out what's going on here. Help, please?
Basically, the current situation is this: You can hack the startkde
script to make KDE2 start all the way through, which basically consists of
simply replacing the kdeinit line with "kcminit". However, at certain
points after KDE is done setting things up, processes named "kdeinit" that
are in charge of certain apps go crazy and hit infinite loops somewhere. I
haven't been able to determine where exactly, and if this is related to
threads at all, or if a critical app or similar somehow doesn't get compiled
with threads. Or something like that. *sigh*
Konqueror can startup and seems to work okay in a different window manager,
but it seems to randomly set off a kdeinit proc as above.
Anyhow, this is 2 weeks' worth of debugging on a 4-month-old problem. If
you're using XFree86 4.0.2, I caution against trying this stuff out unless
you're going to help me out and are willing to help me figure out exactly
where the heck things are going awry. Things should still compile and work
just fine for those on XFree86 3.3.6. I decided to leave out these hacks
in nonessential stuff (like kdenetwork et al) because kde2 itself needs to
work with threads first. =)
I guess I can thank my lucky stars JKH's decided to stick with 3.3.6 until
some point in the future when 4.0.x becomes more stable...
3c4896e2d7