after upgrade the gtk library, when using someof fonts, display is missing.

Bug #52445 reported by Strange
4
Affects Status Importance Assigned to Milestone
libcairo (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: libgtk2.0-0

when upgrade from edgy to dapper, or only upgrade the gtk library to
 libgtk2.0-0 2.8.18-0ubuntu2. And using someof fonts such as wenquanyi or simsun, a pragraph of text splitted by space will only display the first word leaving the words after first space blank.
This bug could simply reproduced by using wenquanyi fonts and using nautilus to explore some directoies contains of word and spaces, such as "My Document". In this case, only the word "My" will be displayed.
I think it's a bug as everything is ok in edgy, and lots of people said, after upgrade, this bug is found.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you downgrade to dapper or upgrade to edgy?

Changed in gtk+2.0:
status: Unconfirmed → Needs Info
Revision history for this message
Michael S. (jellicle) wrote :

I can confirm there's a bug here somewhere. Using all the latest Edgy packages (libgtk2.0 2.10.1), certain GTK2 applications have terrible font rendering. Gaim and Gnucash show this, but Firefox does not. The bug submitter is saying it's also visible in Nautilus.

Fonts are thin and jagged. Many words are not visible unless moused-over or highlighted, which is basically what the bug submitter is trying to describe.

Revision history for this message
Sebastien Bacher (seb128) wrote :

what font do you use? could you provide a screenshot of the issue?

Revision history for this message
Sebastien Bacher (seb128) wrote :

That was a libcairo bug and it's fixed with this upload:

 libcairo (1.2.0-5ubuntu1) edgy; urgency=low
 .
   * debian/control:
     - don't require a directfb newer than the ubuntu package
 .
 libcairo (1.2.0-5) unstable; urgency=medium
 .
   * Rebuild against directfb 0.9.25 which has changed library and udeb
     package names from 0.9.24 that all earlier cairos were built against,
     and which are now removed. This should prevent Cairo from becoming
     uninstallable due to this change. Urgency medium due to this.
 .
 libcairo (1.2.0-4) unstable; urgency=medium
 .
   * Added patch cairo-bug-7494.patch (Closes: #378005)
   * Added patch cairo-bug-7514.patch (Closes: #380064)

Changed in gtk+2.0:
assignee: nobody → desktop-bugs
importance: Untriaged → Medium
status: Needs Info → Fix Released
Revision history for this message
Paul Sladen (sladen) wrote :

Turns out that this isn't actually a bug in Cairo, but in the X server; and the cairo patch is merely a workaround that doesn't actually fix the core issue:

  https://bugs.freedesktop.org/show_bug.cgi?id=7681

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.