pdf2djvu crashed with SIGSEGV in OutputDev::cvtDevToUser()

Bug #413599 reported by Jamie Strandboge
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pdf2djvu (Ubuntu)
Fix Released
Medium
Luca Falavigna

Bug Description

Binary package hint: pdf2djvu

pdf2djvu -o cups_testprint.djvu ./cups_testprint.pdf crashes pdf2djvu. Attached is the pdf causing the problem.

ProblemType: Crash
Architecture: amd64
Date: Fri Aug 14 08:24:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/pdf2djvu
Package: pdf2djvu 0.4.13-0ubuntu3
ProcCmdline: pdf2djvu -o cups_testprint.djvu ./cups_testprint.pdf
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x7fdbfff3d572 <_ZN9OutputDev12cvtDevToUserEddPdS0_+50>: movsd %xmm0,(%rdx)
 PC (0x7fdbfff3d572) ok
 source "%xmm0" ok
 destination "(%rdx)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pdf2djvu
StacktraceTop:
 OutputDev::cvtDevToUser(double, double, double*, double*) () from /usr/lib/libpoppler.so.5
 Page::displaySlice(OutputDev*, double, double, int, int, int, int, int, int, int, int, Catalog*, int (*)(void*), void*, int (*)(Annot*, void*), void*) () from /usr/lib/libpoppler.so.5
 Page::display(OutputDev*, double, double, int, int, int, int, Catalog*, int (*)(void*), void*, int (*)(Annot*, void*), void*) ()
 ?? ()
 ?? ()
Title: pdf2djvu crashed with SIGSEGV in OutputDev::cvtDevToUser()
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse kqemu kvm libvirtd lpadmin plugdev pulse pulse-access sbuild scanner video

Related branches

Revision history for this message
Jamie Strandboge (jdstrand) wrote :
Revision history for this message
Jamie Strandboge (jdstrand) wrote :
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Just checked and the above command works fine on Juanty i386.

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:OutputDev::cvtDevToUser (this=0xeffe10,
Page::displaySlice (this=0xefc8a0, out=0xeffe10,
Page::display (this=0xeffe10, out=0xefc8a0,
pdf::Document::display_page (this=0xefbc90,
xmain (argc=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in pdf2djvu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

removed privacy, confirmed on latest karmic...
output on terminal:
cups_testprint.pdf:
- page #1 -> #1
Segmentation fault

visibility: private → public
Changed in pdf2djvu (Ubuntu):
status: New → Confirmed
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

Quite a pickle:
* pdf2djvu in karmic is still at 0.4.13:
http://packages.ubuntu.com/karmic/pdf2djvu
* while upstream (google code) is 0.5.11:
http://code.google.com/p/pdf2djvu/
* but upstream depends on libpoppler4, while the one in ubuntu depends on libpoppler5
* libpoppler4 existed only in jaunty:
http://packages.ubuntu.com/jaunty/libpoppler4

To sum up, I was unable to install the latest upstream version in order to check if the issue remains...

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

Opened upstream issue on the broken dependency:
http://code.google.com/p/pdf2djvu/issues/detail?id=41

Anyways, why do we keep changing the library name?
- libpoppler5 (0.11.2) in Karmic
- libpoppler4 (0.10.5) in Jaunty
- libpoppler3 (0.8.7) in Intrepid
- libpoppler2 (0.6.4) in Hardy
- libpoppler1 (0.5.1) in Dapper

Why not just call it libpoppler?

Revision history for this message
Jakub Wilk (jwilk) wrote :

The only way I can reproduce this bug is to:
- compile pdf2djvu with poppler 0.11.0;
- upgrade to poppler 0.11.1.
That's because poppler 0.11.1 broke both API and ABI without bumping SONAME. pdf2djvu < 0.5.11 even FTBFS with the unstable version of poppler.

To work around this bug you should upgrade to pdf2djvu 0.5.11 (or backport the proper fix from 0.5.11) and ensure both build-time and runtime dependency on poppler >= 0.11.1.

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

fixed upstream, marking as fix committed

jakub, thank you for your time and efforts

Changed in pdf2djvu (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Jakub Wilk (jwilk) wrote :
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

I don't have an amd64 box to test this, but I uploaded a package on my PPA (https://launchpad.net/~dktrkranz/+archive/ppa), could you please test it? Thanks in advance!

Changed in pdf2djvu (Ubuntu):
assignee: nobody → Luca Falavigna (dktrkranz)
Revision history for this message
Luca Falavigna (dktrkranz) wrote :

pdf2djvu (0.4.13-0ubuntu4) karmic; urgency=low

  * debian/patches/413599-segfault.patch:
    - Apply upstream patch to avoid crashes with newer libpoppler (LP: #413599).

 -- Luca Falavigna < <email address hidden>> Sat, 26 Sep 2009 12:46:01 +0200

Changed in pdf2djvu (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.