Menu

new error after upgrade to Ubuntu 18, please advise

Help
JJ Méric
2018-10-02
2018-10-04
  • JJ Méric

    JJ Méric - 2018-10-02

    Hello

    I upgraded from Ubuntu 16 to Ubuntu 18, and now something no longer works :

    • loading a document - jpg or pdf, works well
    • selecting an area for ocr also works
    • ocr in vietnamese or in french work ok
    • ocr in bambara, a west african language with a few special latin characters, which I setup already 4 years ago and use regularly, ... stopped working:
      On screen, it takes time (more than usual) displaying "OCR running" (bottom left)
      Then the whole display disappears ans I get this error message in Terminal (see below).
    • what do I need to do ? re-install ? upgrade my bambara files (how to?) ...
      Thanks for help!

    JJ
    ERROR MESSAGE

    ~/VietOCR3$ java -jar VietOCR.jar
    
    Error: Illegal Parameter specification!
    "Fatal error encountered!" == NULL:Error:Assert failed:in file globaloc.cpp, line 75
    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    #  SIGSEGV (0xb) at pc=0x00007f87dc3a169b, pid=2237, tid=2310
    #
    # JRE version: OpenJDK Runtime Environment (10.0.2+13) (build 10.0.2+13-Ubuntu-1ubuntu0.18.04.2)
    # Java VM: OpenJDK 64-Bit Server VM (10.0.2+13-Ubuntu-1ubuntu0.18.04.2, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
    # Problematic frame:
    # C  [libtesseract.so.4+0x25969b]  ERRCODE::error(char const*, TessErrorLogCode, char const*, ...) const+0x16b
    #
    # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P" (or dumping to /home/corpus-team/VietOCR3/core.2237)
    #
    # An error report file with more information is saved as:
    # /home/corpus-team/VietOCR3/hs_err_pid2237.log
    #
    # If you would like to submit a bug report, please visit:
    #   http://bugreport.java.com/bugreport/crash.jsp
    # The crash happened outside the Java Virtual Machine in native code.
    # See problematic frame for where to report the bug.
    #
    Aborted (core dumped)
    
     
  • Quan Nguyen

    Quan Nguyen - 2018-10-02

    Your old traineddata is not compatible with Tesseract 4.0's new LSTM engine. You can either retrain it using the new technique or use the OCR Engine Mode 0 (Legacy engine only).

     

    Last edit: Quan Nguyen 2018-10-02
  • JJ Méric

    JJ Méric - 2018-10-04

    thanks for help, but setting to Legacy did not work.
    seeting to LTSM crashes much faster, that's clear, and the error message is just the same.
    Unfortunately, I have no time to retrain just now... Legacy mode was a ray of hope, but alas...

     

Log in to post a comment.