i think herd 5 didnt correct the problem, it got resolved later. the current feisty does not have that problem, as reported by multiple users. but herd 5 has it. wait for the next developer version of feisty to test again
i think herd 5 didnt correct the problem, it got resolved later. the current feisty does not have that problem, as reported by multiple users. but herd 5 has it. wait for the next developer version of feisty to test again