Comment 28 for bug 1907706
Revision history for this message
|
|
#28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
(In reply to Dave Lovelace from comment #25)
> I'm hesitant to just upgrade to 7.anything at this point. Maybe I'll have
> to, but a working program shouldn't just stop working in the middle of an
> edit!
The bug is only seen when you are using backspace to delete inserted text, while there is no problem deleting text otherwise. Perhaps this difference makes it seem like it "just stop working"? Or perhaps you are seeing some behaviour not earlier covered. However, the 6.4.x line has had its last release and officially expires by the end of this month. https:/
So as Aaron says, testing 6.4.6 (or 6.4.7) won't have much point. A fix was applied to the 7.0-line (unfortunately to late to make it to the 6.4.x-line). If that fix was not enough, it needs demonstration in the 7.0-line, and will only be fixed in the 7.0-line. It is too bad that this regression happened, but given that there will not be a 6.4.8 release, you have two choices: Take a step backward or take a step forward.
A step backward: The regression was introduced in 6.4.6 (as a side effect of the fix for bug 127635), so you could go back to 6.4.5. At the bottom of the official download page, there is a link to the archive of old versions.
A step forward: Upgrade to 7.0.3. It is already the fourth official release (counting 0, 1, 2, 3), so it is not that much of a newcomer, even if it is still the "fresh" version on the download page.