FS#4674 - freetype2 don't work with sdl_ttf anymore

Attached to Project: Arch Linux
Opened by Cédric Bermann (skulk) - Sunday, 21 May 2006, 15:28 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To arjan timmerman (blaasvis)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.1 Noodle
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

the TTF_RenderText_Solid, and others text rendering functions of SDL_TTF do not work anymore with the new (freetype2-2.2.1-1) version of freetype2, whereas it works with 2.1.10-3 package version.

With the new version, quite never rendered by sdl_ttf, resulting a NULL pointer with no apparent errors from TTF_GetError().
I'm using sdl-1.2.10-1 and sdl_ttf-2.0.7-2.
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 20 June 2006, 21:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  Revert to 2.1.10
Comment by arjan timmerman (blaasvis) - Sunday, 21 May 2006, 16:11 GMT
please try this package and report back.
(application/x-gzip)    sdl_ttf-2.0.8-1.pkg.tar.gz (18.8 KiB)
Comment by Cédric Bermann (skulk) - Sunday, 21 May 2006, 17:06 GMT
I have the same problem with this package and freetype-2.2.1-1 :/
Comment by arjan timmerman (blaasvis) - Sunday, 21 May 2006, 17:25 GMT
well the problem seems at least to be related to they wricked out the internals.... could you provide some test cases ?
Comment by Cédric Bermann (skulk) - Sunday, 21 May 2006, 18:31 GMT
I've made a very little program which shows (with a beautiful segfault) the problem: with the old freetype2 it works perfectly, but it segfaults with the new one
   ttftest.tar.gz (40.9 KiB)
Comment by nackd (Prieto) - Sunday, 28 May 2006, 20:21 GMT
Foobillard also doesn't work with freetype2-2.2.1. It spits out "FT_Load_Glyph:error#6" and dies.
It works fine with freetype2-2.1.10-3.
Comment by nackd (Prieto) - Tuesday, 30 May 2006, 16:33 GMT
There is another bug open regarding this:
http://bugs.archlinux.org/task/4711

And it links a descriptive document about the problem.
Comment by Jan de Groot (JGC) - Monday, 19 June 2006, 20:44 GMT
The same bug has been reported at debian, seems 2.2.1 isn't such a good release after all.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=371183

Loading...