Comment 92 for bug 19749

Hedley: I could only wish. :-) Considering Canonical's investment in this laptop and my time, I really assumed it would have been flagged as critical 2+ years ago. Apparently in spite of the fact that everyone knows what's wrong, no one has been able to fix it in that amount of time.

Leann: It'll probably be after the new year now before I can test it, but I will. My ongoing physical disability and lack of income is taking it's toll on my stock of blank CDs. If anyone wants to donate some, I'd gladly accept. :-)

Out of curiosity - It's been said many times that the misbehaving bit of software we're dealing with has been updated/fixed and it hasn't. This may be a silly question, but is someone actually trying to fix this issue or is development just pushing forward and hoping it'll get ironed out in the process? A apologize if I sound a bit jaded, but literally - we've known what's wrong and how to fix it for over two years now and it just never seems to get done. Perhaps what sounds simple to a non-developer is really a big issue in an area that's difficult to mess with - which would obviously explain why the fix is taking so long. Again - not mad or irritated or anything - just curious. Ubuntu is still my beloved distro and I promote it locally every chance I get! :-)

P.S. - would adding the current development name in the bug's title/subject make it a little more visible after all these years? I opened the bug, but I'm never sure which bits I should be adding/changing.