I don't understand why this still happens. This bug is basically a duplicate of #833521, which I fixed and closed in v1.5.2.
Please start gscan2pdf from the command line: gscan2pdf --log=log Reproduce the problem, quit gscan2pdf and post the log file.
