Rygle wrote:
> Built with new patches in second last post from Ulf
> (https://bugs.launchpad.net/inkscape/+bug/179988/comments/99). Will try
> new patch now, but I can't test until morning. The following is using
> the patch from
> https://bugs.launchpad.net/inkscape/+bug/179988/comments/99 .
>
> Here's the error info for printing more complex pic (colour with
> gradients and many blurs) with the win-print test code.
>
> - The non-GTK print dialogue (like 0.45.1) comes up and I select a PS printer -> to file and enter a filename
> - Click OK and an info dialogue pops up
>
> =======
> *Microsoft Visual C++ Runtime Library* -> Title of dialogue
>
> Assertion failed!
>
> Program: ...inkscape.exe
> File: cairo-win32-printing-surface.c
> Line:1253
This means cairo has detected an internal error. ie it is a bug in cairo.
What version of cairo are you using? Printing to PDF and checking the
document properties in Acrobat is one way to find the cairo version.
I would suggest finding the simplest drawing that reproduces the
problem. Hopefully this will give me a clue as to what the problem is.
Ideally if I can reproduce the bug with a C test case that calls a few
cairo drawing functions I can debug it.
Rygle wrote: /bugs.launchpad .net/inkscape/ +bug/179988/ comments/ 99). Will try /bugs.launchpad .net/inkscape/ +bug/179988/ comments/ 99 . printing- surface. c
> Built with new patches in second last post from Ulf
> (https:/
> new patch now, but I can't test until morning. The following is using
> the patch from
> https:/
>
> Here's the error info for printing more complex pic (colour with
> gradients and many blurs) with the win-print test code.
>
> - The non-GTK print dialogue (like 0.45.1) comes up and I select a PS printer -> to file and enter a filename
> - Click OK and an info dialogue pops up
>
> =======
> *Microsoft Visual C++ Runtime Library* -> Title of dialogue
>
> Assertion failed!
>
> Program: ...inkscape.exe
> File: cairo-win32-
> Line:1253
This means cairo has detected an internal error. ie it is a bug in cairo.
What version of cairo are you using? Printing to PDF and checking the
document properties in Acrobat is one way to find the cairo version.
I would suggest finding the simplest drawing that reproduces the
problem. Hopefully this will give me a clue as to what the problem is.
Ideally if I can reproduce the bug with a C test case that calls a few
cairo drawing functions I can debug it.