ddjvu -format=pdf makes blank documents

Bug #499324 reported by Юрий Аполлов
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
djvulibre (Debian)
Fix Released
Unknown
djvulibre (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When making
ddjvu -format=tiff in.djvu out.tiff
and then
tiff2pdf out.tiff -o out.pdf
everything goes right and outgoing pdf is readable. But when it's made in a way
ddjvu -format=pdf in.djvu out.pdf
then a blank document is the result. Actually, not fully blank: there are pages, their count is right, but no content on them can be seen, as to file properties. It can be seen in evince that the creator of the document is:
libtiff / tiff2pdf - 20060323 / d
BTW I've downloaded Windows binary - and it's OK in it!
Also I've tried djview to convert djvu to pdf - same results on both platforms: negative @ Ubuntu, positive @ Vista.
There, I got
diff -a bad.pdf good.pdf > outfile
and saw that the result of diff'ing is about 70 Kb. So, it's not the whole file - it's only a header or something I guess, I attach a difffile.
System: Ubuntu 9.04 with all updates

Revision history for this message
Юрий Аполлов (apollovy) wrote :
Revision history for this message
Dave Walker (dogatemycomputer) wrote :

Юрий Аполлов:

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Could you please attach the in.djvu you are using? If that is a problem then could you walk me through creating an acceptable 'djvu' file that I can use for testing? I just want to reproduce this bug so I can confirm it for you.

Please note that I have never used ddjvu.

Changed in djvulibre (Ubuntu):
status: New → Incomplete
Revision history for this message
Юрий Аполлов (apollovy) wrote :

Ok, I'll attach it now. And I got a difference in a more user-friendly way.
It's in:

stream
q 923.7600 0.0000 0.0000 696.2400 0.0000 0.0000 cm /Im1 Do Q
Actually in signs of point (.). In bad file there are comma (,) signs. That's the reason, I guess. And I found the difference there (in the end of file:

/ID[<FF180000FF670000FF4A00006C3D0000><FF180000FF670000FF4A00006C3D0000>]

But I guess it's relative to different files - they are different, of course =)

Revision history for this message
Dave Walker (dogatemycomputer) wrote :

Юрий Аполлов:

I am using Ubuntu 9.10.

This string of commands produces a valid out.tiff which can be viewed using Gwenview. It contains 38 pages.

sudo apt-get install djvulibre-bin
ddjvu -format=tiff in.djvu out.tiff

This command produces a pdf of the in.djvu file:

ddjvu -format=pdf -o out.pdf

I have attached the resulting pdf. I can see the contents of the pdf which are pretty much the same as the contents of the resulting tiff file from the earlier statement. I can view this pdf using Okular and Evince.

I cannot find any bug in this process. What am I missing or what steps are needed to reproduce the problem you are describing?

Revision history for this message
Dave Walker (dogatemycomputer) wrote :

Юрий Аполлов:

Please ignore my previous statement indicating I attached the PDF. It was too large to attach so I omitted it from the post.

Revision history for this message
Юрий Аполлов (apollovy) wrote :

Strange, but true: I've installed djvulibre-bin on liveusb - and it successfully converted my djvu to pdf and I was able to read it! So, it's somewhere in my system - but how can I guess where???
It's bug anyway, and it's gotta be gone =)
So, I'm ready to listen to guesses. I can give you information of any kind - this bug sincirelly interested me =))

Changed in djvulibre (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Dave Walker (dogatemycomputer) wrote :

Юрий Аполлов:

I am sorry but I do not believe your problem qualifies as a bug. This appears to be a configuration issue and should be handled via one of the many support methods available to Ubuntu users. I am also happy to convert this to a question and post your request for support in the forums.

If it helps then you may want to force removal and re-installation of the package and its dependencies.

Revision history for this message
Юрий Аполлов (apollovy) wrote : Re: [Bug 499324] Re: ddjvu -format=pdf makes blank documents

Guess you're right, but I had no customizations with djvulibre at all -
download, install and use! =)
But it'll be helpful if it'll be converted to a question. Btw, shall I
receive messages with answers to this question via my email, if I'm
subscribed to this bug's maillist?

2009/12/25 Dave Walker <email address hidden>

> Юрий Аполлов:
>
> I am sorry but I do not believe your problem qualifies as a bug. This
> appears to be a configuration issue and should be handled via one of the
> many support methods available to Ubuntu users. I am also happy to
> convert this to a question and post your request for support in the
> forums.
>
> If it helps then you may want to force removal and re-installation of
> the package and its dependencies.
>
> --
> ddjvu -format=pdf makes blank documents
> https://bugs.launchpad.net/bugs/499324
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “djvulibre” package in Ubuntu: Invalid
>
> Bug description:
> When making
> ddjvu -format=tiff in.djvu out.tiff
> and then
> tiff2pdf out.tiff -o out.pdf
> everything goes right and outgoing pdf is readable. But when it's made in a
> way
> ddjvu -format=pdf in.djvu out.pdf
> then a blank document is the result. Actually, not fully blank: there are
> pages, their count is right, but no content on them can be seen, as to file
> properties. It can be seen in evince that the creator of the document is:
> libtiff / tiff2pdf - 20060323 / d
> BTW I've downloaded Windows binary - and it's OK in it!
> Also I've tried djview to convert djvu to pdf - same results on both
> platforms: negative @ Ubuntu, positive @ Vista.
> There, I got
> diff -a bad.pdf good.pdf > outfile
> and saw that the result of diff'ing is about 70 Kb. So, it's not the whole
> file - it's only a header or something I guess, I attach a difffile.
> System: Ubuntu 9.04 with all updates
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/499324/+subscribe
>

Revision history for this message
Dave Walker (dogatemycomputer) wrote :

Юрий Аполлов:

Have you tried uninstalling and reinstalling the package?

sudo apt-get purge -f djvulibre-bin && sudo apt-get install djvulibre-bin

Revision history for this message
Юрий Аполлов (apollovy) wrote :

BTW I've tried reinstalling - but not purging! Trying...
Unsuccessfull =(

2009/12/27 Dave Walker <email address hidden>

> Юрий Аполлов:
>
> Have you tried uninstalling and reinstalling the package?
>
> sudo apt-get purge -f djvulibre-bin && sudo apt-get install djvulibre-
> bin
>
> --
> ddjvu -format=pdf makes blank documents
> https://bugs.launchpad.net/bugs/499324
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “djvulibre” package in Ubuntu: Invalid
>
> Bug description:
> When making
> ddjvu -format=tiff in.djvu out.tiff
> and then
> tiff2pdf out.tiff -o out.pdf
> everything goes right and outgoing pdf is readable. But when it's made in a
> way
> ddjvu -format=pdf in.djvu out.pdf
> then a blank document is the result. Actually, not fully blank: there are
> pages, their count is right, but no content on them can be seen, as to file
> properties. It can be seen in evince that the creator of the document is:
> libtiff / tiff2pdf - 20060323 / d
> BTW I've downloaded Windows binary - and it's OK in it!
> Also I've tried djview to convert djvu to pdf - same results on both
> platforms: negative @ Ubuntu, positive @ Vista.
> There, I got
> diff -a bad.pdf good.pdf > outfile
> and saw that the result of diff'ing is about 70 Kb. So, it's not the whole
> file - it's only a header or something I guess, I attach a difffile.
> System: Ubuntu 9.04 with all updates
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/499324/+subscribe
>

Revision history for this message
Jakub Wilk (jwilk) wrote :
Changed in djvulibre (Ubuntu):
status: Invalid → In Progress
Changed in djvulibre (Debian):
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package djvulibre - 3.5.23-3ubuntu1

---------------
djvulibre (3.5.23-3ubuntu1) natty; urgency=low

  * Merge from Debian unstable. Remaining changes:
    + Fix thumb2 porting issues; we suspect that the mov found during code
      review is not an active code path; adding compile time error
      #ifdef __thumb__ to ensure that its really not used in Ubuntu;
      Thanks for Dave Martin for this patch (LP: #513725)

djvulibre (3.5.23-3) unstable; urgency=low

  * revert switch to dpkg-source 3.0 (quilt) format

djvulibre (3.5.23-2) unstable; urgency=low

  * make any2djvu script not fail to notice assent (closes: #515310)
  * upstream changes fix many bugs
    - djvumake no longer fails with these tiny images (closes: #539272)
    - locale set internally as appropriate, e.g., PDF output (closes: #562156)
      also fixes https://bugs.launchpad.net/ubuntu/+source/djvulibre/+bug/499324
    - thread-related crash addressed, slightly post 3.5.23 (closes: #582961)

djvulibre (3.5.23-1) unstable; urgency=low

  * new upstream release
  * bump policy (debian/control)
  * Ubuntu patch from Benjamin Drung (closes: #592964)
    - use autotools-dev to update config.* files to unclutter debdiffs
    - change recommendation from mozilla-firefox to firefox
  * modernise debian/rules with dh7 overrides, also thanks to Benjamin Drung
  * switch to dpkg-source 3.0 (quilt) format
 -- Benjamin Drung <email address hidden> Wed, 17 Nov 2010 16:03:21 +0100

Changed in djvulibre (Ubuntu):
status: In Progress → Fix Released
Changed in djvulibre (Debian):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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