Quote:
Originally Posted by tompe
I do not remember anybody having the bug confirming that it was fixed. People saying they do not see the bug and have never seen it is no confirmation. I read everything here and I do not remember you claiming that it had been fixed in January.
|
No, I didn't
know that it had been fixed in January (as I said, it would have been nice if Bookeen had informed people who'd reported the bug that it had been fixed!). The bug was fixed in build 538 of the firmware, which appears to have been shipped in new Gen3's since late December.
As you say, I only discovered myself that it had been fixed when I updated my firmware at the end of Feb.