If the scanimage and scanadf frontends in gscan2pdf produce this result, too, then the bug is either in sane, or more likely in the backend. Are you using HPLIP?
If the scanimage and scanadf frontends in gscan2pdf produce this result, too, then the bug is either in sane, or more likely in the backend. Are you using HPLIP?