[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Just for the record: the (now public) bug report for this issue in Ubuntu 12.04 is bug #943195 -- discussion should continue there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf s

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

i took a minute to look at this, and yes, once again, there is a segfault on all pdf's :( the backtrace is different, so this really is a different issue...but anyway the discussion is here now, so on to the solution... to fix this, you can simply install the known working oneiric xpdf and poppler

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

So there is really nothing more I can do for now? ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 To manage notifications about this bug g

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I reproduce it when I add a PDF file argument, but when Precise wants to file a bug report it tells me it has already been reported (private bug). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Updated again, still not running. xpdf 3.02-21build1, libpoppler19 0.18.4-1ubuntu2 (crash message = * MediaBox = ll:0,0 ur:841.89,595.28 * CropBox = ll:0,0 ur:841.89,595.28 * Rotate = 0 Segmentation fault ) su I remember it worked with oneiric's libpoppler. I will fill another bu

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Xpdf works for me in Precise. Please install all updates and if it still does not run, open a new bug report using "ubuntu-bug" command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: X

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

This bug is probably back in ubuntu Precise.. only with libpoppler19 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 To manage notifications

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

One of the sources mentioned in comment #63 now has to be changed to: http://archive.ubuntu.com/ubuntu/pool/main/p/poppler/poppler_0.16.7-2ubuntu2.debian.tar.gz Then, the installation procedure is: sudo dpkg -i libpoppler13_0.16.7-2ubuntu2_amd64.deb libpoppler- cpp0_0.16.7-2ubuntu2_amd64.deb libp

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

So far I was using evince and Acrobat Reader, but both don't allow me to open a PDF file more than once at the same time. But thanks for mentioning okular, I've tried that one and it does this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I guess you should use the LTS if you don't want random problems with non core applications. Or install Oneiric beta. Or do as the rest of us, use another (core) application like evince/okular. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to U

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

When will there be a fix for Ubuntu 11.04? This bug has been terribly annoying over the past half a year. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpo

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@Marcel Stimberg, thanks. This does indeed solve it for me as well. A back port to Natty would indeed be a good thing (TM). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaul

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Can confirm the fix with installing libpoppler13 v0.16.7-2ubuntu1 as well. However, I still propose to backport that fix to 11.04 (natty) as there the xpdf installation is still broken and no update has been released for it so far and oneiric isn't out yet and perhaps not all people are going to sw

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Confirmed here too. The libpoppler13 version 0.16.7-2ubuntu1 package (current version in Oneiric) installs cleanly on Natty, and allows Xpdf to run without segfaults. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchp

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@UWP Thank you for sharing your precise instructions. I used to use Jim Reeses's solution (compiling xpdf from source) and the segmentation fault went away. However, on a few of the pdf files that I view, I get the error "Bogus memory allocation size". I had to resort to evince or adobe reader t

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

And to be precise: it can be used with the original xpdf-packages from ubuntu. The SEGV-bug was only in the poppler-libs. I also tried compiling from source and it also worked. This means: for those of you who need xpdf we now have 2 workarounds: install libpoppler by hand, either from the oneiric-

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

% sudo dpkg -i libpoppler13_0.16.7-2ubuntu1_amd64.deb makes xpdf work for me. Yay! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 To manage

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Here is a quick update on what I found out: The xpdf changes in debian (that are also in oneiric) are not responsible for fixing the issue. Instead, some change in the poppler library (which was also updated in oneiric) fixes the crash. I'll try to find out what change exactly is necessary. In the

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I tried the version in oneiric, and indeed, I can display PDFs again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 To manage notifications

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@Marcel: Ok, I understand that the SRU process is needed. My problem is that I (and I guess lots of other people here) don't have the background to do it (patches? I'd like to have the binary package...). I'd appreciate it if you do this for us. And there wouldn't be any other way? Maybe some kind

Re: [Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

* Marcel Stimberg <669...@bugs.launchpad.net>: > I did not check whether the upstream (which is in this case Debian) > changes are easy to backport yet, but I might do later and initiate the > SRU process. I guess we all would appreciate this. > Note that xpdf is in the universe repository [1] a

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@UWP: That might be strange but it is the standard procedure in every Linux distribution. Only the most recent development version (in this case, Oneiric) has the most recent upstream version and can benefit from bug fixes in that distribution. The version in natty cannot be simply updated to th

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

This is a bit strange to me. The stable version doesn't run, it segfaults. Lots of people saying "bugbugbug". A fix comes. And now we have the strange situation that the bug will not be fixed for the environment it has been found? I don't want to update to oneiric now and I thought: when it's fixed

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@Kierun: The status "Fix Released" means it is fixed in the *current development release*[1], i.e. in Ubuntu Oneiric. If you find it still crashes in Oneiric, feel free to reset the status to "New". For a fix in Natty, you (or someone else) has to follow the SRU process[2]. [1] https://wiki.ubuntu

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@Michael Gilbert: I just did a apt-get update && apt-get install xpdf and the resulting xpdf still core dumps. Am I missing something? $ xpdf fu.pdf Segmentation fault (core dumped) $ gdb xpdf [...] (gdb) run Starting program: /usr/bin/xpdf Program received signal SIGSEGV, Segmentation fault.

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

** Changed in: xpdf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 To manage notifications

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Same problem. ProblemType: Bug Architecture: amd64 Date: Mon Jul 25 20:23:42 2011 Dependencies: coreutils 8.5-1ubuntu6 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

"Ursula's .deb file fixes it for me. Thanks." Yes, Ursula's .deb file fixes the crashing problem for me too. However and unfortunately, it occurs frenquently that what gets out of the printer when I try to print a pdf file with Xpdf is a sheet with an error message printed in red. This does neve

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Same problem in natty with xpdf 3.02-12ubuntu2 and any PDF file. "evince" works fine. $ gdb xpdf GNU gdb (Ubuntu/Linaro 7.2-1ubuntu11) 7.2 Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> Maybe it would be possible to ship libpoppler5 specifically for > xpdf as a legacy version? yes, that would certainly work, but someone would actually need to volunteer to do that. > Reverting to an old version of poppler in general is certainly > not an option, e.g. epdfview and most important

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> This would not be a problem if they were using the Debian poppler version. Maybe it would be possible to ship libpoppler5 specifically for xpdf as a legacy version? Reverting to an old version of poppler in general is certainly not an option, e.g. epdfview and most importantly evince as the def

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> The Poppler library itself is based on Xpdf, and while it is sensible to > factor out the > resulting redundant code from the latter, I think it is clear that more > development > work is needed to achieve that goal successfully. This conclusion is incorrect. The conversion works fine in Debi

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

As far as I can tell, the problem is due to the presence of two, seemingly-incompatible definitions of the GlobalParams class. One is in libpoppler (poppler/GlobalParams.cc), one is in the Xpdf source (xpdf/GlobalParams.cc). The diff between them is pretty extensive. If I attempt to link Xpdf witho

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Initially posted a bug downstream on Linux Mint (#798671) until I saw this bug report. Kind of surprising that this is still broken. Jim Rees' build commands from source (comment 19) worked great for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Ursula's PPA works fine, thanks! I cannot believe Ubuntu's xpdf is still *completely unusable* seven months after this bug report, even though there's a known fix, be it an unfavorable one or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Thanks Ursula, that stopped the segmentation fault. The /etc/xpdf/xpdfrc file does not seem to be read, maybe xpdf has been compiled to look elsewhere? Changes to the psFile line have no effect. So I copied that file to ~/.xpdfrc and now the psFile is setting is being read. -- You received thi

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Same problem xpdf crashed everytime and Ursula's solution fixed it. Thank you Ursula! Natty has been a rough ride for some of us out here. xpdf is the 7th issue and there are still more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Thanks Ursula for your workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com h

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Any update on this? I too am having a problem with xpdf not being able to read any pdfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 -- u

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@Chris, I was about to propose the increase of the importance of this bug, but it seems like the scale is not for the application (which would be "Critical"), but for all Ubuntu users. And since this packages is in "Universe", I guess it is not a core application, and thus applies for this descript

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@Akkana: Many thanks for the hint -- I accidentally left the bug at the private status :-/ It is public now, sorry for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfault

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Marcel: unfortunately bug 783109 isn't public (and my attempt to file a public one was duped to the private bug), so those of us experiencing problems with epdfview can't see that bug or add comments there. (Sorry for the spam, I'll shut up about epdfview now.) Thanks, Alexander, for the mupdf reco

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Problems does seem to be with poppler. I installed the latest version from source (http://poppler.freedesktop.org/) and xpdf works again. I do not know if it helps anyone but valgrind points at GlobalParams::findFontFile(GooString*, char**) (in /usr/lib/libpoppler.so.13.0.0) as the guilty party.

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

@rew: It has been stated in the previous comments that the epdfview issue is a different one. Please follow this bug report for the epdfview crashes: bug 783109 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I wrote the above comment trying to argue that the epdfview bug was probably the same but forgot to make the point after the intro. However. epdfview however crashes in strdup (libc) and not in libpoppler. [Switching to Thread 0x7fffec326700 (LWP 23313)] 0x75a3a5d1 in ?? () from /lib/

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I THINK that xpdf worked for me for a while before it suddenly stopped working. But I can't be sure. I then switched to epdfview as my PDF viewer. I was happy for a day or two Then epdfview started crashing just like xpdf The thing is... epdfview still displays SOME pdfs. For epdfview i

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

$ sudo apt-get install mupdf now works for me as workaround. Or maybe even as replacement for xpdf/epdfview. Time will tell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaul

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Split off the epdfview issue to bug 780911. I don't see debug symbols even with poppler-dbg, though. Compiling from source is working with xpdf, so maybe I'll try that with epdfview too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I just upgraded to Natty, and I got this error. The method of @Jim Rees worked for me. Uninstalled xpdf and compiled from source. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title:

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> It does work on some PDFs that xpdf crashes on, but it still crashes on > others. > http://www.ebparks.org/files/EBRPD_files/photoguides/1-EBRPD_Wildflowers.pdf > crashes it repeatably. that's definately a different issue. you should submit a new bug against epdfview. you can get symbols for

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I don't know if a stack trace from libs without symbols is useful, but here's epdfview: #0 0xb775b706 in ?? () from /lib/i386-linux-gnu/libc.so.6 #1 0xb7f5777b in g_strdup () from /lib/i386-linux-gnu/libglib-2.0.so.0 #2 0x0011a56e in ?? () #3 0x0011fe93 in ?? () #4 0x00120684 in ?? () #5 0x0

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

actually, epdfview on natty seems to work just fine for me (tested a couple pdf files). your bug is probably a different issue altogether. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title:

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> epdfview also crashes on startup on every PDF file, on natty. Or > should that be filed as a separate bug? I'm guessing it's the > same problem, and there doesn't seem to be an epdfview-specific > bug filed. epdfview also uses poppler, and all evidence points poppler as the root cause at this p

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

epdfview also crashes on startup on every PDF file, on natty. Or should that be filed as a separate bug? I'm guessing it's the same problem, and there doesn't seem to be an epdfview-specific bug filed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscri

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Unfortunately there seems to be another bug in Ursula's package. I don't know if this bug also occurs in the official xpdf package because the official xpdf package crashes so I can't test any more. Ursula's package does not crash, but: I was viewing a multi-page PDF file which I had generated u

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Ursula's .deb file fixes it for me. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ub

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I created a xpdf package removing poppler support, following what @Jim Rees did and also applying other bugfixes the Ubuntu package has. It's waiting to be built in my PPA. Hope this helps while the bug isn't fixed properly in Ubuntu. https://launchpad.net/~ursinha/+archive/ppa -- You received t

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I agree with comment #21. This bug is preventing xpdf from running. I have just run into the problem having been tricked into "upgrading" to 11.04 and cannot understand why it would have a priority of anything other than "critical". -- You received this bug notification because you are a member o

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

It seems inappropriate to me that the importance of this bug is set to "medium," since xpdf is broken and doesn't work at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfau

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> apt-get install libfreetype6-dev lesstif2-dev > ./configure --with-t1-library=no > --with-freetype2-includes=/usr/include/freetype2 > make xpdf this is a reasonable "workaround" (if you want to call it that). ideally someone will step up to actually fix the problem this time for the "o" release

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Here's how I did it: Get the source tarball and apply all patches from: http://www.foolabs.com/xpdf/download.html apt-get install libfreetype6-dev lesstif2-dev ./configure --with-t1-library=no --with-freetype2-includes=/usr/include/freetype2 make xpdf If you do have libpoppler-dev installed you

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

> And then just getting the original source (apt-get source xpdf), and > tar-gunzipping > the original source, configuring, making and installing works fine. that's not surprising. the upstream version (i.e. non-popplerized version) will work just fine, and that's the solution i've been pushing

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

The binary packaged xpdf still segfaults/crashes on every pdf file. I successfully compiled a working xpdf on natty. Here are the required dependencies aside from the regular automake etc packages (these were the maverick build-deps): libfreetype6-dev libpaper-dev libt1-dev libx11-dev libxext-de

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

please revert to the pre-poppler version, which was also done for maverick. that is the only known solution at present. thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf seg

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

** Changed in: xpdf (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.7 -- ubuntu-bugs mailing

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Andreas Moog // this bug is not fixed in xpdf 3.02-12ubuntu12.(with new libpoppler13 0.16.4-0ubuntu1). same segfault occures still. ^_^[/media/sdc1]$ gdb xpdf GNU gdb (GDB) 7.2- Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

fixed with 3.02-12ubuntu2 ** Changed in: xpdf (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in libpoppler.so.

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

poppler 0.16's api differs from 0.12, which xpdf is currently built for. i will fix this in debian when i find the time. sorry for the rant, but this is exactly why ubuntu every ubuntu release turns out so buggy. blingy packages are pushed without consideration of their effects on the rest of the

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

xpdf also crashes for me on every single pdf file, so I tried re-building xpdf from source, but it won't compile. Here is what I get (on natty as of today): $ dpkg-buildpackage -rfakeroot -j8 -b dpkg-buildpackage: export CFLAGS from dpkg-buildflags (origin: vendor): -g -O2 dpkg-buildpackage: expo

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

in the meantime, someone with appropriate permissions should increase the "importance" to release critical. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf segfaults on start in lib

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

also, this may be caused by one of the compiler hardening features, which are on by default on ubuntu, but not debian. one could try compiling with -fno-stack-protector and other flags to see if there is any effect. -- You received this bug notification because you are a member of Ubuntu Bugs, w

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

i'm the debian maintainer. i've spent a day trying to track this issue down already without any luck. its probably originating in a dependency (like freetype). i'm not really sure why, and i don't have any more time to dig into this. if someone wants to try mixing/matching dependencies using de

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

This is actually not exactly the same crash I am seeing (but it is very likely closely related). It is the same crash that was present when xpdf was updated to poppler the last time (during Maverick development), back then it led to a complete revert of the changes. Maybe the old bug (Bug #611446)

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

Crashes here as well. Backtrace: #0 0x0048ea9d in GlobalParams::findFontFile(GooString*, char**) () from /usr/lib/libpoppler.so.7 #1 0x00477516 in GfxFont::findExtFontFile() () from /usr/lib/libpoppler.so.7 #2 0x00477a5c in Gfx8BitFont::Gfx8BitFont(XRef*, char*, Ref, GooString*, GfxFontType

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I'm attaching a more complete backtrace of the crash (triggered with Evolution’s quickref.pdf). I tried the xpdf version in Debian Squeeze which is also 3.02-11, it does not crash. The main difference between Squeeze and Natty is the poppler version, Debian Squeeze still uses 0.12.4-1.2 (libpoppler

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

I am also seeing this crash for every PDF I try, marking as confirmed. ** Changed in: xpdf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/669211 Title: Xpdf

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

This poppler library works with this PDF with the Evince viewer. This poppler library works with this PDF with the Epdfview viewer. It only doesn't work with Xpdf. Also - Xpdf in Meerkat is not dependent on the poppler library by default. As Xpdf changed its behavior and broke, I am putting thi

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

** Changed in: poppler (Ubuntu) Status: Incomplete => New -- Xpdf segfaults on start in libpoppler.so.7 https://bugs.launchpad.net/bugs/669211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bug

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

It crashes with every PDF I have tried. This makes xpdf unusable. ** Attachment added: "Example of PDF causing the crash." https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/669211/+attachment/1723347/+files/PART_1.pdf -- Xpdf segfaults on start in libpoppler.so.7 https://bugs.launchpad.

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

thanks for the report, could you attach the pdf causing the crash? thanks. ** Changed in: poppler (Ubuntu) Importance: Undecided => Medium ** Changed in: poppler (Ubuntu) Status: New => Incomplete -- Xpdf segfaults on start in libpoppler.so.7 https://bugs.launchpad.net/bugs/669211 You

[Bug 669211] Re: Xpdf segfaults on start in libpoppler.so.7

-- Xpdf segfaults on start in libpoppler.so.7 https://bugs.launchpad.net/bugs/669211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubu