Hum, I triggered once more this bug, so it looks that it's a driver issue 
instead. hal may just be spontaneously triggering it before I would otherwise.
Not sure against which package it should be reassigned, kernel probably.



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to