@911jason: That's the new randomizer. Unless I did something very dumb, I assume you already had the "random" file if it did this! :P
@joblack: Restart in recovery mode, and kill the trigger file over USB MS, maybe? (holding [HOME] during boot). If you still can't remove it, craft a simple update file to remove the trigger file.
Quick update: I'm currently testing/debugging the K3 fonts hack. So far: I didn't break the K2 support. Classic system-wide fonts works. Browser handling is broken, and I'm currently trying to coerce fontconfig into submission to fix it.
Last edited by NiLuJe; 09-21-2010 at 07:16 PM.
|