Faheem Mitha

Hi Jeffrey, On Wed, 10 Apr 2019, Jeffrey Ratcliffe wrote: Here, it looks as though imagemagick is running out of tmp: https://www.imagemagick.org/discourse-server/viewtopic.php?t=25064 Having scanned the image without the to-png option, please copy it out of the /tmp/gscan2pdf-xxxx directory to somewhere it won't get deleted, and see if you can reproduce the problem from the command file: convert test.pnm test.png If that produces the same error, df Might tell where you are short of space and convert...

Hi Jeffrey, Here's hoping that replying via email works. On Mon, 8 Apr 2019, Jeffrey Ratcliffe wrote: gscan2pdf uses imagemagick for all the image operations - conversions and the like. I eee. I didn't know that. You are right, this looks like an imagemagick memory problem. Ok. Therefore, I assume you can workaround the problem by scanning a smaller area, or using a lower resolution. As well as helping you get imagemagick working, I'd like to have gscan2pdf not crash, and produce a reasonable error...

Also note that searching for fatal/cache.c/CacheSignalHandler/3626 gives hits for Imagemagick, which does not seem like a coincidence., though I was not aware that gscan2pdf depended on Imagemagick.

gscan2pdf crashes with error message: perl: unable to extent pixel cache `No such file or directory' @ fatal/cache.c/CacheSignalHandler/3626

I set the "Specify time as well as date", which I don't recall hearing about before. But it makes no difference. The time still shows up in pdfinfo as (in my current example) CreationDate: Tue Dec 25 00:00:00 2018 IST ModDate: Tue Dec 25 00:00:00 2018 IST Currently running 2.2.1. Should I post a log?

I concur. This option (which I also have set), does not solve the issue, at least for pdfinto / PDF metadata. I currently get output like CreationDate: Sat Oct 27 00:00:00 2018 IST ModDate: Sat Oct 27 00:00:00 2018 IST The timestamps listed by ls, however, it now correct, at least approximately. I haven't done careful checks. Were these also incorrect before?

So you did. Sorry, I must be losing my mind.

Hi Jeffrey, I see that #247 is listed as fixed by 2.1.5, but this is still open.