Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 302623 - iscan-2.21.0 crashes with memory violation when trying to use jpeg pdf as output format
Summary: iscan-2.21.0 crashes with memory violation when trying to use jpeg pdf as out...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Stefan Briesenick (RETIRED)
Depends on: 302624
  Show dependency tree
Reported: 2010-01-28 12:58 UTC by Andrzej Kardas
Modified: 2010-07-21 22:56 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Andrzej Kardas 2010-01-28 12:58:42 UTC
I'm using Epson Perfection 4490 Scanner with iscan 2.21.0 and firmware installed with the ebuild media-gfx/iscan-plugin-gt-x750 taken from this bug report:
When ever I'm trying to use pdf or jpeg as output format the program crashes with memory violation error. Other formats are working fine.

Reproducible: Always

Steps to Reproduce:
1. emerge =media-gfx/iscan-2.21.0
2. emerge media-gfx/iscan-plugin-gt-x750
3. iscan
4. push the scan button and choose the pdf or jpeg as output format

Actual Results:  
The program is crashing just after scanning the marked part of the document or photo with memory violation msg. The scanner stops after this leaving the device in unstable state: the scanning device stops in the place when photo or documents ends.

Expected Results:  
Scanning should work fine (It does with newer version of iscan)

I manage to solve this issue by using newer version of iscan 2.23.0 with the same firmware (installed by the same ebuild). I will write separate bug report with bump version request, and link it here.
Comment 1 Andrzej Kardas 2010-01-28 13:11:43 UTC
Version bump request:
Comment 2 Stefan Briesenick (RETIRED) gentoo-dev 2010-07-21 22:56:02 UTC
new version in portage. I close that bug now. if your problem still exists, feel free to reopen.