© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Ha! Sure enough, the quickest way to get a bug to manifest is to deny its existence. It is NOT fixed globally in Oneiric. I made 2 useage changes in the past few weeks that contributed to my not noticing any flaws: 1) switched primary browser from Firefox to Chrome, and 2) switched terminator shell's font from "Monospace 8pt" to "Ubuntu Mono 8pt". I just changed the terminator font back a day or two ago and yep, it's wrecked again.
Observations:
- bug manifests in terminator shell with "Monospace 8pt" font, but not with "Ubuntu Mono" at any size. After changing font sizes and faces for a while, the bug is completely gone from the font chooser, and does not appear in the shell after closing prefs --- buuuuut, after switching to another app for a while the font is once again damaged in a novel way. This happens with "Monospace" only, as far as I can see.
- bug does not manifest in Chrome 14.0.835.186 at all. (see zooming note below)
- bug manifests in Firefox 7.0.1 -- nb. compared same page [ http://
- bug manifests in Thunderbird 7.0.1 in html emails, but NOT in message lists, menus, etc.
- browser view zooming causes what? font re-rendering? In Firefox, zooming in and out repeatedly with ctl+, ctl- caused the bug to appear *almost* at random. Sometimes the fonts were damaged in the same way, but after a few passes the damage changed location, moving from letter to letter and line to line. No *pattern* of change was observed, per se. The same actions in Chrome did not provoke any damaged fonts to appear, even using the same page as with Firefox.