On 06/08/13 02:38, Ville Valkonen wrote:
Hi, did you compile the recent Xenocara too?

No, I didn't get that far. Just the kernel. That's how I know it wasn't the recent xenocara updates that caused the problem and believe this specific commit is the culprit.

However, you did get me thinking...

I'll skip using X and go console-only, build the new xenocara and see if the problem goes away. I'll bet that kernel commit requires the new X. I'll post the results in a bit.

--
Scott McEachern

https://www.blackstaff.ca

"Those who would give up essential liberty to purchase a little temporary safety 
deserve neither liberty nor safety." -- Benjamin Franklin

Reply via email to