SD> some fonts can't be displayed any more which worked with freetype1
SD> based freetype module
Yes. The FreeType 1 library had been fine-tuned to include
workarounds for a number of common font bugs (much against David
Turner's preferences). These hacks are only now getting into
FreeType 2.
On Fri, Feb 28, 2003 at 11:06:49 -0500, Mike A. Harris wrote:
> On Fri, 28 Feb 2003, Alan Hourihane wrote:
>
> >From: Alan Hourihane <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Reply-To: [EMAIL PROTECTED]
> >Content-Type: text/plain; charset=us-ascii
&g
On Thu, Feb 27, 2003 at 09:40:00PM +0100, Stefan Dirsch wrote:
>On Thu, Feb 27, 2003 at 09:51:15AM -0800, Keith Packard wrote:
>> Around 16 o'clock on Feb 27, Stefan Dirsch wrote:
>>
>> > No. Will be some work to extract the CVS diff for me. So you can't
>> > reproduce this problem with 4.3.0? I'l
On Fri, 28 Feb 2003, Alan Hourihane wrote:
>From: Alan Hourihane <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Reply-To: [EMAIL PROTECTED]
>Content-Type: text/plain; charset=us-ascii
>Subject: Re: xf86cfg: ERROR SIGSEGV caught!
>
>> >Loading /usr/X11R6/lib/module
On Fri, Feb 28, 2003 at 05:46:24AM -0500, Mike A. Harris wrote:
> On Thu, 27 Feb 2003, Stefan Dirsch wrote:
>
> >> > No. Will be some work to extract the CVS diff for me. So you can't
> >> > reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now
> >> > before looking deeper into this is
On Fri, Feb 28, 2003 at 05:46:24AM -0500, Mike A. Harris wrote:
> On Thu, 27 Feb 2003, Stefan Dirsch wrote:
>
> >> > No. Will be some work to extract the CVS diff for me. So you can't
> >> > reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now
> >> > before looking deeper into this is
On Thu, 27 Feb 2003, Stefan Dirsch wrote:
>> > No. Will be some work to extract the CVS diff for me. So you can't
>> > reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now
>> > before looking deeper into this issue.
>>
>> I've just tried xf86cfg under 4.3 and didn't have any difficul
On Thu, Feb 27, 2003 at 09:51:15AM -0800, Keith Packard wrote:
> Around 16 o'clock on Feb 27, Stefan Dirsch wrote:
>
> > No. Will be some work to extract the CVS diff for me. So you can't
> > reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now
> > before looking deeper into this issu
Around 16 o'clock on Feb 27, Stefan Dirsch wrote:
> No. Will be some work to extract the CVS diff for me. So you can't
> reproduce this problem with 4.3.0? I'll have a try with 4.3.0 now
> before looking deeper into this issue.
I've just tried xf86cfg under 4.3 and didn't have any difficulties.
On Thu, Feb 27, 2003 at 10:11:00AM -0500, David Dawes wrote:
> On Thu, Feb 27, 2003 at 12:35:57PM +0100, Stefan Dirsch wrote:
> >Hi
> >
> >Looks like xf86cfg in 4.2.99.902 (most likely also 4.3.0) is
> >broken. At least I see now messages like this.
> >
> >[...]
> >Loading /usr/X11R6/lib/modules/ex
On Thu, Feb 27, 2003 at 12:35:57PM +0100, Stefan Dirsch wrote:
>Hi
>
>Looks like xf86cfg in 4.2.99.902 (most likely also 4.3.0) is
>broken. At least I see now messages like this.
>
>[...]
>Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
>Module GLcore: vendor="The XFree86 Project"
>co
Hi
Looks like xf86cfg in 4.2.99.902 (most likely also 4.3.0) is
broken. At least I see now messages like this.
[...]
Loading /usr/X11R6/lib/modules/extensions/libGLcore.a
Module GLcore: vendor="The XFree86 Project"
compiled for 4.2.99.902, module version = 1.0.0
ERROR SIGSEGV caught!
[.
12 matches
Mail list logo
