Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29069 - [libxft] With update to libxft 2.3.0-2, rxvt-unicode xft font rendering breaks

Attached to Project: Arch Linux
Opened by Matthew Via (via) - Friday, 23 March 2012, 05:20 GMT
Last edited by Andreas Radke (AndyRTR) - Wednesday, 23 October 2013, 18:13 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After upgrading libxft from 2.2.0-2 to 2.3.0-2, rxvt-unicode renders my dejavu-ttf font incorrectly. Attached image shows two instances of rxvt-unicode, with the one on the right showing the incorrect rendering of my font, specified as:

xft:Deja Vu Sans Mono:pixelsize=11:style=Condensed

And the left shows an instance after downgrading back to 2.2.0-2. I imagine the problem is that urxvt needs to be relinked against the new libxft.

Additional info:
* rxvt-unicode version 9.15-1
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Wednesday, 23 October 2013, 18:13 GMT
Reason for closing:  Upstream
Additional comments about closing:  I'm CC'ed to the upstream report. We can't do anything downstream here for now.
Comment by Sébastien Luttringer (seblu) - Saturday, 24 March 2012, 14:44 GMT
Can you be more clear about "renders my dejavu-ttf font incorrectly"? It's not obvious in your matrix terms.

Not a linking issue:
$ ldd =urxvt|grep Xft
libXft.so.2 => /usr/lib/libXft.so.2 (0x00007f773f9dd000)
$ ll /usr/lib/libXft.so.2
lrwxrwxrwx 1 root root 15 2012-03-12 21:23 /usr/lib/libXft.so.2 -> libXft.so.2.3.0

I've the same display with xterm and urxvt. Can you please confirm you hjave the same rendering with xterm and urxvt?

Maybe new version of libXft introduce drawback.
   term.png (157.1 KiB)
Comment by Matthew Via (via) - Sunday, 25 March 2012, 02:01 GMT
The problem does not appear to affect xterm.

I don't know how I can be more clear about "renders my dejavu-ttf font incorrectly" -- it has nothing to do with my color scheme, can you not see that the right terminal is completely different? The spacing is all wrong and the characters have less width.

Your ldd test doesn't show it is not a linking issue. All it shows is that its linked against libXft.so.2, not a specific version.
Comment by Sébastien Luttringer (seblu) - Sunday, 25 March 2012, 12:47 GMT
in the previous sceenshot i started xterm with:
xterm -fa 'xft:Deja Vu Sans Mono:pixelsize=11:style=Condensed'

and rxvt-unicode with:
urxvt -fn 'xft:Deja Vu Sans Mono:pixelsize=11:style=Condensed'

__Do you see your issue in my screenshot__ (one window/both windows)?

> Your ldd test doesn't show it is not a linking issue. All it shows is that its linked against libXft.so.2, not a specific version.
If you do not see it, build urxvt and see if it change something.
Comment by Antony Martin (Yno) - Sunday, 01 April 2012, 19:24 GMT
I have the exact same issue Matthew has. Downgrading to rxvt-unicode-9.14-1 solved the problem for me.

EDIT: Oh, after rebooting, it turns out that the problem came back. Weird :) (so WHY did the problem disappeared when I downgraded?)
EDIT2: Downgrading libxft to 2.2 seems to work.
Comment by Sébastien Luttringer (seblu) - Monday, 02 April 2012, 11:07 GMT
I think it's a issue with libxft. xterm have same displaying and downgrading libxft fix issue.
Comment by Sébastien Luttringer (seblu) - Friday, 06 April 2012, 15:59 GMT
Without connection, rxvt-unicode was rebuilt today.
Comment by Jan de Groot (JGC) - Wednesday, 08 August 2012, 11:53 GMT
Is this still an issue with 2.3.1?
Comment by Yardena Cohen (yardenac) - Monday, 29 April 2013, 15:04 GMT
  • Field changed: Percent Complete (100% → 0%)
Sorry to bring up old news, but I can confirm this is still a bug in 2.3.1-1.
Comment by Yardena Cohen (yardenac) - Monday, 29 April 2013, 16:34 GMT

Loading...