Hi
The reason that I reassigned it to that package is that I can not see
how lightspeed can distroy the internal data structure in fontconfig
so that it on finalize of the structure makes an assert. The lightspeed
application do not even call this function.
I think it is valid to forward this
On Sun, Dec 10, 2006 at 07:26:55PM -0800, Steve Langasek wrote:
It does not follow that just because an assertion failure happens in
fontconfig that the bug is in fontconfig. This problem hasn't been reported
against any other programs besides lightspeed,
It has been reported for several
reassign 402402 libfontconfig1
thanks
Hi
On Mon, Dec 11, 2006 at 02:04:55PM +0100, Steinar H. Gunderson wrote:
On Sun, Dec 10, 2006 at 07:26:55PM -0800, Steve Langasek wrote:
It does not follow that just because an assertion failure happens in
fontconfig that the bug is in fontconfig. This
reassign 402402 lightspeed
thanks
On Mon, Dec 11, 2006 at 02:47:35PM +0100, Ola Lundqvist wrote:
Removed from where? In lightspeed case the FcFinit is not called
directly but rather via gtk libraries.
Wrong. Check src/ogl-ftgl.cc, line 70.
I'm reassigning back to fontconfig. If the function
unmerge 387606 402402
reassign 387606 lightspeed
severity 402402 important
thanks
Hi
Doh!!! I have been looking in the wrong source tree for lightspeed.
Sorry about that. I must have downloaded the sarge version some time
ago and did not check which version I was looking into. Thanks a lot
for
5 matches
Mail list logo