Summary: | Disappearing characters with big fonts and disabled antialiasing | ||
---|---|---|---|
Product: | cairo | Reporter: | Jan Janecek <janjanjanx> |
Component: | general | Assignee: | Chris Wilson <chris> |
Status: | RESOLVED MOVED | QA Contact: | cairo-bugs mailing list <cairo-bugs> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jan Janecek
2014-04-13 18:54:41 UTC
So the debian bug report says that "gxmessage -fn 'DejaVu Sans Mono 100' 1.2.3.4.5" is supposed to be broken. However, that works for me. It also says a bit about some stuff in ~/.fonts.conf. Since I don't know much about .fonts.conf, I asked google for some input and came up with the following: <?xml version="1.0"?> <!DOCTYPE fontconfig SYSTEM "fonts.dtd"> <fontconfig> <match target="font" > <edit mode="assign" name="antialias" > <bool>false</bool> </edit> </match> </fontconfig> Still no problem with gxmessage. What am I doing wrong? (P.S.: This works for me both with latest git and with debian's 1.12.16-2) This is weird. Now I am on my laptop and I can't reproduce the bug either. I am sure the bug happens on my home PC as I described, however I won't have acces to the PC for next few days. Looks like the bug is affected by something else (I guess it can be anything from gpu drivers to libpango and gtk2 version). On home PC I use nouveau, on laptop I have radeon. But if I remember correctly, the bug was happening on my laptop too some time ago. I don't remember exact versions of most of the libraries, so you'll have to wait for that information until I'll be back home. Do you have any ideas what specific libraries could affect this bug? Ok, it is indeed releated to graphic drivers. This bug stopped occouring on my home PC (with nouveau) when I disabled 2D acceleration globally in xorg.conf. On radeon drivers it doesn't seem to happen at all. Now is this a nouveau bug or a cairo bug? Correction: I was using proprietary fglrx drivers on the laptop (where the bug was NOT happening). Now I use opensource radeon drivers (on the same laptop) and the bug IS occuring. So, the summary is: This bug occurs with nouveau and radeon oupensource drivers (with 2D acceleration enabled). It does not occur with fglrx drivers. I have not tested nvidia proprietary drivers. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/175. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.