16 Sep
2010
16 Sep
'10
8:10 p.m.
<snip>
However, in addition to running my conky display from /root/.kde/Autostart, I realized that KPersonalizer was not running. That provides confirmation that Trinity starts out honoring $KDEHOME for root but then changes sometime after. Trinity must be reading the startupconfig file from /root/.kde in order to not run KPersonalizer. So although KDEROOTHOME helps avoid some of the problems I described, there remains something awry with the way Trinity starts out correctly and then veers off course.
I found an error in startkde that would result in no KDEHOME variable being set; you may want to update to revision 1176220 or higher and recompile, especially if you try to run Trinity as root!
Tim