This bug needs to be re-opened since, I assume. it currently isn't flagged as an open bug against precise anywhere and therefore is unlikely to get fixed.
This bug needs to be re-opened since, I assume. it currently isn't flagged as an open bug against precise anywhere and therefore is unlikely to get fixed.