Menu

#213 Cant call method freeze on an undefined value

v1.0_(example)
closed-fixed
nobody
None
5
2016-01-11
2016-01-07
Alistair
No

I'm getting basically the same error on two different platforms (line numbers vary slightly, I assume due to different gscan2pdf versions):

*** Arch Linux 4.3.3-2-ARCH

gscan2pdf --version
gscan2pdf 1.3.5

WARN - *** unhandled exception in callback:
*** Can't call method "freeze" on an undefined value at /usr/share/perl5/site_perl/Gscan2pdf/Document.pm line 1076.
*** ignoring at /usr/bin/gscan2pdf line 7269.

*** Ubuntu 12.04

gscan2pdf --version
gscan2pdf 1.3.6

ARN - *** unhandled exception in callback:
*** Can't call method "freeze" on an undefined value at /usr/share/perl5/Gscan2pdf/Document.pm line 1077.
*** ignoring at /usr/bin/gscan2pdf line 7231.

The scanner is the same in both instances: Epson Perfection V370 Photo.

Despite the text about ignoring the error, gscan2pdf appears to get in to an inconsistent state as the progress bar at the bottom of the window never closes and the unpaper and tesseract processes aren't executed.

The trigger appears to be Rotating the pages (Both Sides, 90 degrees).

A workaround is to scan the page then manually rotate, unpaper and OCR the page (although it triples the amount of effort and time required).

I'll attach the two log files to the ticket.

Many Thanks,
Alistair

Discussion

  • Alistair

    Alistair - 2016-01-07

    Attaching logs...

     
  • Jeffrey Ratcliffe

    A very similar bug was in v1.3.4, and I fixed it in v1.3.5 - but evidently broke it again. Anyway, this time I have fixed it properly, and have added a test to make sure it stays fixed. I'll try and get a new release out in the next couple of weeks.

     
  • Jeffrey Ratcliffe

    • status: open --> closed-fixed
     
  • Alistair

    Alistair - 2016-01-09

    Hi Jeffrey,

    Thanks very much for your quick response. If you would like it tested pre-release, I'm happy to patch my system (I had a look at http://git.code.sf.net/p/gscan2pdf/code but it appears to only go up to 20 Dec 2015).

    Looking forward to the next version. :-)

    Thanks again,
    Alistair

     
  • Jeffrey Ratcliffe

    I've pushed all my commits now, so please go ahead and test the fix.

     

Log in to post a comment.

MongoDB Logo MongoDB