← Back to team overview

documentation-packages team mailing list archive

[Bug 1688022] Re: text randomly scatters in documents


** Tags added: ui

** Also affects: ubuntu-font-family
   Importance: Undecided
       Status: New

You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-font-family-
sources in Ubuntu.

  text randomly scatters in documents

Status in Ubuntu Font Family:
Status in ubuntu-font-family-sources package in Ubuntu:

Bug description:
  You newer know when your document or template created using ubuntu family fonts will crash.
  You can save a flawless document and after reopening it within minutes it's crashed. The text is scattered around and you can make it useful again only by changing the size of the font and/or changing font into anything outside the ubuntu family. Sometimes after you change fonts like that and then change the font back to ubuntu everything is ok.
  Sometimes the problem can be temporarily solved by logging out from Windows user account/ ubuntu session. But that's not always true. Sometimes when a document is scattered in Open Office - opening it in Libre office shows perfect, flawless document.
  It's affecting both: Libre and Open Office programs on both: Windows (XP, Vista,7, 10) and Linux (Ubuntu 12.04 LTS, 14.04 LTS as well as Mint and Xubuntu). It's a problem when creating, editing and reading a file but also when printing it.
  The problem occurs when text is scattered - then the printout will be affected as well. When file looks ok - print will be fine. Used printers: HP laser and ink printers and OKI laser printers.

  It would be nice to be sure how your document will look like in a moment. There are days and weeks without a single error. But then again there are days you can't work because documents simply won't come up without errors.
  This is the one and only font that makes things like that. I would really like to avoid changing it to another one as I use it in many work related tasks.

To manage notifications about this bug go to: