Bug 718006

Summary: unable to save multi-page as TIFF or PDF
Product: [Fedora] Fedora Reporter: Michael S. Tsirkin <mst>
Component: gscan2pdfAssignee: Bernard Johnson <bjohnson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: bjohnson
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 15:09:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael S. Tsirkin 2011-06-30 16:12:47 UTC
Description of problem:
I scan a multi-page document.

When I try to save as PDF, I get this error:
Error creating PDF image object: Can't call method "val" on an undefined value at /usr/share/perl5/vendor_perl/PDF/API2/Resource/XObject/Image.pm line 66.

When I try to save as TIFF, I get this message:
Error writing TIFF


Version-Release number of selected component (if applicable):
gscan2pdf-0.9.32-1.fc15.noarch

How reproducible:
unsure

Steps to Reproduce:
1. scan a 6 page document
2. File/Save
3. select PDF or TIFF format
  
Actual results:
fails to save

Expected results:
should save

Additional info:
Worked fine in FC13.

Comment 1 Michael S. Tsirkin 2011-06-30 16:15:50 UTC
Noticed more issues:
saving as PS fails with 'error writing TIFF'.
so error message is wrong.

Saving as dejavu gives me 'error writing dejavu'

Comment 2 Michael S. Tsirkin 2011-06-30 16:17:00 UTC
note: saving separate pages (save/selection when
only 1 page is selected) works.
try to save many pages - it fails.

Comment 3 Michael S. Tsirkin 2011-06-30 16:31:54 UTC
ok, it turns out the specific session was bad, this
is reproducible if I load a bad session that
I saved by I re-scanned and it went away.


I can try help debugging using that session I saved if
someone is interested.
Unfortunately I can't attach the session
itself as the document scanned was not public.

The error message for PS is wrong (it says 'TIFF')
as per Comment 1, and this might be reproducible
but the rest of the report isn't
reproducible it this point.

Comment 4 Michael S. Tsirkin 2011-06-30 16:33:12 UTC
just noticed there are some errors printed
in the terminal where it's run from:

Use of uninitialized value $filename in pattern match (m//) at /usr/bin/gscan2pdf line 3245.
Use of uninitialized value in division (/) at /usr/bin/gscan2pdf line 2855.
Use of uninitialized value in division (/) at /usr/bin/gscan2pdf line 2856.
Use of uninitialized value $type in concatenation (.) or string at /usr/bin/gscan2pdf line 2874.
Use of uninitialized value $type in pattern match (m//) at /usr/bin/gscan2pdf line 2875.
Use of uninitialized value in numeric eq (==) at /usr/bin/gscan2pdf line 1201.
Use of uninitialized value in numeric eq (==) at /usr/bin/gscan2pdf line 2595.
Use of uninitialized value in division (/) at /usr/bin/gscan2pdf line 2855.
Use of uninitialized value in division (/) at /usr/bin/gscan2pdf line 2856.
Use of uninitialized value $type in concatenation (.) or string at /usr/bin/gscan2pdf line 2874.
Use of uninitialized value $type in pattern match (m//) at /usr/bin/gscan2pdf line 2875.
Use of uninitialized value in division (/) at /usr/bin/gscan2pdf line 2855.
Use of uninitialized value in division (/) at /usr/bin/gscan2pdf line 2856.
Use of uninitialized value $type in concatenation (.) or string at /usr/bin/gscan2pdf line 2874.
Use of uninitialized value $type in pattern match (m//) at /usr/bin/gscan2pdf line 2875.
*** unhandled exception in callback:
***   Image file '/tmp/9V70RryDAh/LzWWoLA5RC.pnm' contains no data at /usr/bin/gscan2pdf line 1873.
***  ignoring at /usr/bin/gscan2pdf line 12318.
Use of uninitialized value in numeric eq (==) at /usr/bin/gscan2pdf line 1201.
*** unhandled exception in callback:
***   Image file '/tmp/9V70RryDAh/LzWWoLA5RC.pnm' contains no data at /usr/bin/gscan2pdf line 1873.
***  ignoring at /usr/bin/gscan2pdf line 12318.
Use of uninitialized value in numeric eq (==) at /usr/bin/gscan2pdf line 1201.
Use of uninitialized value in numeric eq (==) at /usr/bin/gscan2pdf line 2595.

Comment 5 Bernard Johnson 2011-08-19 21:43:13 UTC
(In reply to comment #3)
> ok, it turns out the specific session was bad, this
> is reproducible if I load a bad session that
> I saved by I re-scanned and it went away.
> 
> 
> I can try help debugging using that session I saved if
> someone is interested.
> Unfortunately I can't attach the session
> itself as the document scanned was not public.
> 
> The error message for PS is wrong (it says 'TIFF')
> as per Comment 1, and this might be reproducible
> but the rest of the report isn't
> reproducible it this point.

Session problems like this have been reported by multiple people.  Unfortunately, for everyone it seems to contain private data.  I would suggest one of these courses:

1) Get a crash with session data you can upload
or
2) Work with upstream privately to debug with your session data

Comment 6 Fedora End Of Life 2012-08-07 15:09:44 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping