public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nuitari <nuitari@melchior.nuitari.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] vmware-player fonts unreadable
Date: Sat, 10 Mar 2007 10:51:07 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0703101050180.19731@melchior.nuitari.net> (raw)
In-Reply-To: <200703100924.35974.menola@sbcglobal.net>

> > > > I noticed that my realplayer also has the same problems, so I don't
> > > > think it's a vmware-specific issue...
> > > >
> > > > Hmm...
> > >
> > > Check your GTK font settings.
> >
> > Umm... how? =A0I've never messed with them, they've always "just
> > worked"...
> 
> I adjust them via kde control center (there was a dedicated package I=20
> installed to provide access to GTK settings which I don't recall at this=20
> time, sorry)
> Goggle may be of some help

When my mozilla-firefox-bin fonts were messed up it turned out to be the 
RenderAccel setting in my xorg.conf, though this only applies if you use 
the binary nvidia drivers.
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2007-03-10 15:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 23:57 [gentoo-amd64] vmware-player fonts unreadable Michael George
2007-03-09  1:36 ` Chris Traylor
2007-03-09 14:50 ` The Doctor
2007-03-10 14:04   ` Michael George
2007-03-10 14:36     ` Michael George
2007-03-10 14:47       ` Joe Menola
2007-03-10 15:00         ` Michael George
2007-03-10 15:24           ` Joe Menola
2007-03-10 15:51             ` Nuitari [this message]
2007-03-10 18:38             ` Michael George
2007-03-10 18:39             ` Michael George
2007-03-10 18:46               ` Joe Menola
2007-03-10 19:05               ` Richard Freeman
2007-03-10 19:29                 ` Michael George
2007-03-10 18:56 ` Simon Stelling
2007-03-12 13:18 ` The Doctor
2007-03-12 16:31   ` Cermelo Woodgett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0703101050180.19731@melchior.nuitari.net \
    --to=nuitari@melchior.nuitari.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox