Owen, any clue?

[I can't actually confirm here ATM, my system is all screwed up. :/ Will try
tomorrow.]

Should be fixed in CVS as of today

*** This bug has been marked as a duplicate of 305391 ***

yes, it's partially fixed. i'm only able to change hinting settings,
antialiasing can't be switched off.
btw. setting pixel order to VRGB or VBGR kills all apps
(cairo 0.5.2, pango 1.9.0 HEAD, glib/gtk 2.7.4, gnome 2.11.x devel up to date)

I don't see how you could have gotten the VRGB crash with Cairo-0.5.2,
there was no handling of subpixel ordering in 0.5.2. Maybe you were testing
with CVS? I've fixed the crash there:

2005-07-24  Owen Taylor  <otaylor@redhat.com>

        * src/cairo-ft-font.c (_render_glyph_outline): Fix size of allocated buffer
        for vertical subpixel rendering. (Reported by Fryderyk Dziarmagowski,
        http://bugzilla.gnome.org/show_bug.cgi?id=310935)
        (_get_pattern_load_flags): Fix a problem where we were OR'ing multiple
        FT_LOAD_* flags together.

        * src/cairo-xlib-screen.c (_cairo_xlib_init_screen_font_options): Fix
        reversed check for subpixel or not.

I can't reproduce problems turning off antialiasing. Can you try updating
to the latest Cairo from CVS. If you still have problems with antialiasing,
can you tell me *exactly* what options you have set in gnome-font-properties.

Thanks.

That was 0.5.2 cvs HEAD, sorry about that.

V* pixel order crash seems to be solved. Problem with antialiasing was
fontconfig related. Atfer commenting out following code (was always my default
font setup):

<!-- /etc/fonts/local.conf -->

<match target="pattern"> 
 <edit name="autohint" mode="assign"> 
  <bool>true</bool> 
 </edit> 
</match> 
 
<match target="font"> 
 <edit name="antialias" mode="assign"> 
  <bool>true</bool> 
 </edit> 
</match> 

setting "font rendering" to "monochrome" works perfectly. But shouldn't be local
font configuration respected as well?

The configuration in fonts.conf is going to win over the options from the
display - the reason for this is that people like to do things like disabling
hinting for just one font in fonts.conf, and that shouldn't be overriden
by global settings.

However, fonts.conf isn't really a good place to do global configuration;
it's hard to machine edit, and you won't get changes to running applications.
That's why the primary set of options is stored on the display instead.

Thanks for the testing.

oops, now I see "antialias assign true" in my config :\. that was my local
problem, sorry about that.

Big thanks to Owen for his awesome work.

closing, as resolved/fixed.