Description of problem: Trying a new scanner out. Attempted to use YAGF to perform OCR. Input file was an A3 scan of over 205MB. YAGF appears to crash after reading the file in. Running it from the command line reports a segmentation error. Version-Release number of selected component: yagf-0.9.3-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: yagf crash_function: __memcpy_sse2_unaligned executable: /usr/bin/yagf kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:40 #1 memcpy at /usr/include/bits/string3.h:51 #2 QIPGrayscaleImage::copy at /usr/src/debug/yagf-0.9.3/src/core/qipgrayscaleimage.cpp:259 #3 ImageProcessor::crop at /usr/src/debug/yagf-0.9.3/src/core/imageprocessor.cpp:48 #4 Page::loadFile at /usr/src/debug/yagf-0.9.3/src/tpage.cpp:109 #5 PageCollection::appendPage at /usr/src/debug/yagf-0.9.3/src/tpagecollection.cpp:81 #6 MainForm::loadFile at /usr/src/debug/yagf-0.9.3/src/mainform.cpp:498 #7 MainForm::loadFiles at /usr/src/debug/yagf-0.9.3/src/mainform.cpp:242 #8 MainForm::loadImage at /usr/src/debug/yagf-0.9.3/src/mainform.cpp:368 #9 MainForm::qt_static_metacall at /usr/src/debug/yagf-0.9.3/src/moc_mainform.cxx:145
Created attachment 880218 [details] File: backtrace
Created attachment 880219 [details] File: cgroup
Created attachment 880220 [details] File: core_backtrace
Created attachment 880221 [details] File: dso_list
Created attachment 880222 [details] File: environ
Created attachment 880223 [details] File: exploitable
Created attachment 880224 [details] File: limits
Created attachment 880225 [details] File: maps
Created attachment 880226 [details] File: open_fds
Created attachment 880227 [details] File: proc_pid_status
Created attachment 880228 [details] File: var_log_messages
Please try # yum --enablerepo=updates-testing update yagf for new 0.9.3.1 version (see also https://admin.fedoraproject.org/updates/yagf-0.9.3.1-1.fc20 ). If problem will remain please make a record of this here.
Should be fixed in 0.9.3.2.
*** Bug 1087640 has been marked as a duplicate of this bug. ***