From: Martin Schlemmer <azarah@gentoo.org>
To: Spider <spider@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] some KDE nastiness...
Date: Fri, 3 Jan 2003 01:57:04 +0200 [thread overview]
Message-ID: <20030103015704.58781851.azarah@gentoo.org> (raw)
In-Reply-To: <20030103002829.7883cbeb.spider@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On Fri, 3 Jan 2003 00:28:29 +0100
Spider <spider@gentoo.org> wrote:
> begin quote
> On Thu, 2 Jan 2003 17:15:29 +0100
> Paul de Vrieze <gentoo-user@devrieze.net> wrote:
>
> >
> > Start with setting up a decent /etc/fonts/fonts.conf if it's not
> > there. Also an upgrade to freetype-2.1.3 might help because that
> > version can eat compressed bitmap fonts. (.pcf.gz which are most of
> > the default fonts in freetype)
>
> Wish it was that simple. the fonts.conf is clean (I removed it, and
> fontconfig, and then reinstated them) as is the freetype (remove and
> reinstate at the same time as fontconfig) so those shouldnt be the
> case here.. I've run fc-cache and all appears good with verbose
> logging.
>
> i've removed all of my ~/.kde and started over, and most of my system
> is as up-to-date as can be.
>
> AA fonts work in Gnome (2) and appears to be doing ok, so I'm a tad
> uncertain here.
>
What version of KDE and QT ? there was an issue with updating Qt to
3.1.1 (or 3.1.0) and not remerging kdelibs and kdebase ...
--
Martin Schlemmer
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-03 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 15:21 [gentoo-dev] some KDE nastiness Spider
2003-01-02 16:15 ` Paul de Vrieze
2003-01-02 23:28 ` Spider
2003-01-02 23:57 ` Martin Schlemmer [this message]
2003-01-03 9:10 ` Spider
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=20030103015704.58781851.azarah@gentoo.org \
--to=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=spider@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