| Summary: | x11-libs/cairo[xlib-xcb] causes ugly font rendering in gtk (compared to cairo-1.12.14-r2) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alexandre Rostovtsev (RETIRED) <tetromino> |
| Component: | [OLD] Library | Assignee: | Ben de Groot (RETIRED) <yngwin> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | brebs, robink, x11 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info output
screenshot with cairo-1.12.14-r2 screenshot with cairo-1.12.14-r3 |
||
Created attachment 353686 [details]
screenshot with cairo-1.12.14-r2
Comment on attachment 353686 [details]
screenshot with cairo-1.12.14-r2
gedit-3.6 screenshot with cairo-1.12.14-r2 - this looks good on my monitor
Created attachment 353688 [details]
screenshot with cairo-1.12.14-r3
gedit-3.6 screenshot with cairo-1.12.14-r3 - this looks terrible on my monitor
cairo-1.12.14-r2 says: > # --disable-xcb-lib: > # do not override good xlib backed by hardforcing rendering over xcb and cairo-1.12.14-r3 silently adds > + $(use_enable xcb xlib-xcb) \ Regardless if this is your issue, we should revert this. That new use_enable is wrong, take a look at the cairo compilation output - choice tidbits: The following surface backends: XCB: yes The following functions: X11-xcb functions: no (disabled, use --enable-xlib-xcb to enable) So for Gentoo there should/would be 2 use flags: xcb and xlib-xcb. However, who actually *benefits* from --enable-xlib-xcb? On Nvidia, for me it's always been noticeably slower in firefox, in the simple operation of opening a new tab and having 9 preview panes drawn in the empty tab. There's also that little catch, that xlib-xcb (at least last time I've checked - granted it was awhile here) causes artifacts in some of the corner cases in firefox. Though even if that's still valid, you never know with firefox whose fault is it. Emerging cairo-1.12.14-r3 with EXTRA_ECONF=--disable-xlib-xcb fixes the font rendering problem. The reason why I enabled it is bug 441878 comment 9. But it appears that not all users benefit from this so I will make it optional in the next revbump, and NX packages need put blockers or documentation in place. 1.12.14-r4 now has xlib-xcb USE flag |
Created attachment 353684 [details] emerge --info output Updating from cairo-1.12.14-r2 to cairo-1.12.14-r3 causes the fonts in all gtk2 and gtk3 applications to be rendered quite ugly (too much hinting, too thin, and looks like the wrong subpixel order for my screen). Both revisions were emerged with the same USE flags: X glib opengl svg xcb (-aqua) -debug -directfb -doc (-drm) (-gallium) (-gles2) -legacy-drivers -openvg (-qt4) -static-libs -valgrind