I can login as root but not any other user.
Would somebody confirm this behavior? Latest GIT.
SAK is disabled.
Darrell
On 03/29/2012 05:48 PM, Darrell Anderson wrote:
I can login as root but not any other user.
Would somebody confirm this behavior? Latest GIT.
SAK is disabled.
Darrell
Darrell,
I just tried with TDM from 3/26. I had to del the [ThirdPartyWM] code from .twinrc (unpatched build), but TDM let me log in just fine after.
HOWEVER - my damn laptop nearly exploded with 'tsak' and 'tdmtsak' taking over 96% of my cpu continually -- my palmrest is still HOT!
On 03/29/2012 06:08 PM, David C. Rankin wrote:
Darrell,
I just tried with TDM from 3/26. I had to del the [ThirdPartyWM] code from .twinrc (unpatched build), but TDM let me log in just fine after.
HOWEVER - my damn laptop nearly exploded with 'tsak' and 'tdmtsak' taking over 96% of my cpu continually -- my palmrest is still HOT!
Darrell,
I just updated my entire install to 'todays' build. I can still log in with TDM, but tsak and tdmtsak still cause my CPU to hit 96%.
I just updated my entire install to 'todays' build. I can still log in with TDM, but tsak and tdmtsak still cause my CPU to hit 96%.
Okay, thanks. Something goofy happening here then.
Regarding the SAK issues, I just updated the patch in bug report 906 for the latest GIT. Try the patch and let everybody know how things go.
http://bugs.pearsoncomputing.net/show_bug.cgi?id=906
Another interim debugging approach is to use -DBUILD_TSAK=OFF in the build options. I'm rebuilding now with that option. The last time I tried building that way things were worse because I never had access to the TDM and continually was prompted to press Ctl-Alt-Del. That should have happened only with SAK support enabled.
Darrell
I just updated my entire install to 'todays' build. I can still log in with TDM, but tsak and tdmtsak still cause my CPU to hit 96%.
I needed to reset the user's ~/.dmrc file by explicitly resetting the TDM login options to Trinity.
I can't (yet) test the updated patch in bug report 906 because I just rebuilt tdebase with -DBUILD_TSAK=OFF because I did not know where the TDM login problem was. I'll rebuild with the updated patch and test SAK.
Darrell
On 03/29/2012 10:06 PM, Darrell Anderson wrote:
I needed to reset the user's ~/.dmrc file by explicitly resetting the TDM login options to Trinity.
I can't (yet) test the updated patch in bug report 906 because I just rebuilt tdebase with -DBUILD_TSAK=OFF because I did not know where the TDM login problem was. I'll rebuild with the updated patch and test SAK.
Darrell
I'll test it, but I don't follow. I have it set to trinity in .dmrc already...
22:08 valkyrie:~> cat .dmrc [Desktop] Session=trinity
Do you want me to unset it and test?
I'll test it, but I don't follow. I have it set to trinity in .dmrc already...
22:08 valkyrie:~> cat .dmrc [Desktop] Session=trinity
Do you want me to unset it and test?
Oh no. My previous login problem through TDM was caused by not having dmrc correctly configured. Too many test setups here and insufficient brainage. That problem was not related to the updated patch.
The updated patch is to possibly resolve some SAK issues. There was a patch in the bug tracker (the bug tracker was not tagged as such). The patch was a tad old and needed to be updated to the latest GIT. All I was asking was to test the patch --- and ignore my statements about dmrc, which was a different topic.
Darrell
I'll test it, but I don't follow. I have it set to trinity in .dmrc already...
Uh, never mind about testing the patch. Tim just commented the patch defeats the purpose of SAK. I tagged the patch obsolete.
Hmm, perhaps we need a review team for the bug tracker...
Darrell
-
Darrell Anderson -
David C. Rankin