Bob Jamison-2 wrote:
Yes, I believe that all of the patches made it into the trunk. However, I don't think that any of them applied to Poppler. This sounds like simply a typical common regression here. ^^
We haven't done a "debug" upload in a few weeks. Time to do another one, I guess.
I reported this in the bug mentioned above - https://bugs.launchpad.net/inkscape/+bug/229524
There's a full backtrace in it, as well as the stderr output using inkcl.bat, so hopefully that helps someone with more programming nouse than me.
Johan, all the windows patches from 0.46 were applied to trunk before the 0.46 release. They haven't been integrated into the 0.46 branch because of Linux distro issues, but are all sitting obediently in RELEASE_0_46_BRANCH/packaging/win32/patches - there is an 0.46 folder for the ones that went in the release, and an 0.46.1 folder for those I hope will go into the .1 release sometime soon.
I've had a quick look at the SVN records for trunk/src/extension/internal/ - things like pdf-input-cairo.cpp and stuff in the pdfinput folder, but I couldn't find any obvious recent changes that might have caused this problem (but I'm just a c++ noob!).
Some other options that I haven't tried are to go back through the dev libs versions one at a time and rebuild each time, and also to build SVN revisions going back in leaps of about 50 commits per jump and see when it starts mucking up. If you're keen, that's two good starting points.
Cheers,
Rygle.