This bug should definitely be reopened... I have this problem on both a machine with a fresh install and a machine which has had feisty reinstalled from a build on 8th April...
This bug should definitely be reopened... I have this problem on both a machine with a fresh install and a machine which has had feisty reinstalled from a build on 8th April...