Comment 32 for bug 43745

Bert Hekman (bert-demontpx) wrote :

I'm getting my laptop back this night, so I'll also be testing it with the newest kernel 2.6.15-25-686.

But what is the next step? Is someout going to figure out where the error occured? Are we just going to leave this bug, because it seems to be resolved in the newest kernel? Anyone got any ideas about this?