From Kristian Høgsberg (upstream):
The only ABI/API guarantees provided by poppler are for the glib and qt
bindings. We can not guarantee any kind of stabilty for the core xpdf API,
since any bugfix or security fix will touch some class and add or remove member
variables. The problem is that
Why is rebuilding the deps a hack?
If there's something fragile about it, couldn't we just back out the
003_refcount patch for Dapper, and issue an update later? I assume
libpoppler will need several security updates throughout Dapper's
support period. Won't some of these break ABI? Is there a
Why is rebuilding the deps a hack?
If there's something fragile about it, couldn't we just back out the
003_refcount patch for Dapper, and issue an update later? I assume
libpoppler will need several security updates throughout Dapper's
support period. Won't some of these break ABI? Is there a
I just want to say that this patch scares me.
You also have to bump the SONAME, because you've changed
the size of GfxFont.
--
evince crashes when highlighting text at line end
https://launchpad.net/bugs/24970
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Still crashes with 0.5.1, see bug #41661 for another document which
causes the issue, as well as a valgrind dump (just showing that it's a
font which was cleared by Gfx::popResources when still present in the
state instance variable, I think).
** Bug 41661 has been marked a duplicate of this bug
** Attachment added: Possible fix for crashing
http://librarian.launchpad.net/2382580/poppler_fixmem.patch
--
evince crashes when highlighting text at line end
https://launchpad.net/bugs/24970
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
