You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. install 0.9.4.3 from
http://ppa.launchpad.net/alex-p/notesalexp-trusty/ubuntu trusty main
2. open yagf.
3. Try to open a simple jpg file
What is the expected output? What do you see instead?
yagf EITHER crashes:
grigory@new-xubuntu:~$ yagf
Object::connect: No such slot MainForm::recognizeAll() in
/build/buildd/yagf-0.9.4.3+git20140818/src/mainform.cpp:164
Object::connect: (sender name: 'actionRecognize_All_Pages')
Object::connect: (receiver name: 'MainWindow')
QImage::scaled: Image is a null image
QImage::scaled: Image is a null image
Ошибка сегментирования (сделан дамп памяти)
OR opens the file as if was corrupted, see attached Screenshot.png
What version of the product are you using? On what operating system?
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
Please provide any additional information below.
Original issue reported on code.google.com by gtubol...@gmail.com on 31 Aug 2014 at 12:30
I used YAGF 0.9.4.4, which is available in source code form from here. It
opened the file quite fine and recognized it. I will try more under different
settings but generally it works.
Original comment by andrei.b...@gmail.com on 7 Sep 2014 at 7:06
День добрый! Может быть, дело в остальных
компонентах, к-рые установлены у меня в Ubuntu
14.04 ? Или пакет в репозитории notealexp как-то
криво собрался ? Какую ещё информацию
прислать ?
Original comment by gtubol...@gmail.com on 7 Sep 2014 at 1:31
Автор сборки пакета посоветовал отключить
в настройках "обрезать изображение при
загрузке". Помогло - ошибка исчезла.
Оказывается, в Дебиан такая же ошибка
проявляется.
Original comment by gtubol...@gmail.com on 7 Sep 2014 at 3:02
Original issue reported on code.google.com by
gtubol...@gmail.com
on 31 Aug 2014 at 12:30Attachments:
The text was updated successfully, but these errors were encountered: