As someone who's been watching this bug for a while, I feel the need to
interject to defend the Debian maintainers before they're alienated.
Given how trivial a poppler-less xpdf package would be to create, the
Debian maintainers probably have good reason not to package one. I'm
guessing this i
Michael Gilbert writes:
>> #662882
>> https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/669211 (see comment 47)
>
> Those are this bug, and Ubuntu developers are responsible for their
> system preferring poppler's globalparams and pretty much breaking
> everything. They need to find their own
On Sun, Oct 07, 2012 at 03:30:08PM -0400, Michael Gilbert wrote:
> > #622877
> > #640515
> > #606885
>
> Not major i.e. release-critiical issues.
I didn't claim /those/ where release-critical issues. Apart from that, broken
printing (landscape), quiet aborts for password-protected PDF and
apparen
control: severity -1 important
On Thu, Oct 4, 2012 at 8:37 PM, Jens Stimpfle wrote:
> To reiterate again, the current wheezy xpdf package is in a terribly
> defunct state, possibly imposing severe security problems and should
> under no circumstances be included into the stable release.
No it isn
severity 658264 grave
thanks
Fri, 10 Aug 2012 18:38:38 +0200, David Madore :
> Is there any hope of this fix entering Debian Wheezy before it
> completely freezes? To reiterate what has been said earlier in the
> thread, accessing uninitialized memory has potential security issues,
> so this shou
Just to confirm that Wolfram's patch works beautifully for me, and
fixes the utter brokenness of xpdf on Ubuntu Precise as well as its
not-so-obvious brokenness on Debian Wheezy. So, many thanks to him
for figuring this one out and fixing it!
Is there any hope of this fix entering Debian Wheezy b
Just out of interest:
Is this really a namespace conflict? As I understand the code, xpdf and
libpoppler should want to use an object of same class from the same
namespace, but due to some reason, the class code was duplicated to
xpdf. I'm not c++ expert, but perhaps this was to make linking of xp
And here is the corresponding patch for stable/squeeze.
Luckily it is a bit simpler.
Regards,
Wolfram.
description: fix type clash GlobalParam xpdf vs. poppler
author: Wolfram Gloger
debian-bug: http://bugs.debian.org/658264
Index: xpdf-3.02/xpdf/GlobalParams.cc
=
tag 658264 patch
thanks
Michael Gilbert writes:
> Since you're interested in
> this, it would be great if you could spend some time trying to find a
> solution.
Ok, here is a patch, to be applied after all other debian patches. It
is not nice, but IMHO should work. valgrind doesn't complain a
reopen 658264
severity 658264 important
tag 658264 help
retitle 658264 possible memory corruption in GlobalParams
thanks
> and xpdf.xx:159 is exactly the forementioned problematic:
>
> globalParams = new GlobalParams(cfgFileName);
>
> I have now invested \approx 6h in this report and am 100% sure
ow...@bugs.debian.org (Debian Bug Tracking System) writes:
> Make sure you've also updated to the expa from squeeze. This bug has
> been reported many times now: #628591, #603153, etc.
Upgrading libexpat1 indeed changes behaviour and avoids the obvious bug
symptoms, presumably due to a different
Package: xpdf
Version: 3.02-12+squeeze1
Severity: grave
After upgrading to squeeze, xpdf crashes on startup, even without any
input file:
% /usr/bin/xpdf any.pdf
xpdf: pthread_mutex_lock.c:62: __pthread_mutex_lock: Assertion
`mutex->__data.__owner == 0' failed.
Abgebrochen (core dumped)
I also
12 matches
Mail list logo
