utushi backend: operation was cancelled after scanning document
Brought to you by:
ra28145
Menu
▾
▴
1 Attachments
#326 utushi backend: operation was cancelled after scanning document
Hi,
After upgrading Ubuntu from 1810 to 1904 gscan2pdf will no more scan documents.
The scanner Epson DS1660W is recognized. All necessary options are accepted.
After starting the program I get:
scan-pages error: “Option was canceled” just after the scan movement without the preview of the document neither the possibility to save it.
Sometimes I get the error:
update_options error: “The Reload-Recursion-Limit (435) was exceeded”
I reinstalled the scanner driver and gscan2pdf without any effect.
The scan is stil possible with e.g. Image Scan, the application from Epson, but without preview less useful.
I’m using gscan2pdf for many years, because I think it is the best scanner software for Linux and I would like to continue so. On an other PC it is still working fine under Ubuntu 1810.
You will find a log-file in attachment.
Sincerely
sourcy
Related
This bug was fixed in v2.5.2. Please upgrade via the PPA and confirm that the fix has worked for you, too.
Hi Jeffrey,
thank you for your advice.
I updated gscan2pdf from V2.3.0 to V2.5.4 as suggested.
Unfortunately I'm still receiving scan_pages error: Operation was canceled
Thanks for the log file. Now you have a different bug. I'd say that this is at least partly a bug in the backend. It gets into a loop trying to set the top-left y value to 1:
DEBUG - Setting option 'tl-y' from '0.999984741210938' to '1'.
DEBUG - Setting widget 'tl-y' to '1'.
INFO - sane_set_option 12 (tl-y) to 1 returned status 0 (Success) with info 21870 (? + ? + ? + ? + ? + ? + ? + SANE_INFO_RELOAD_PARAMS + SANE_INFO_RELOAD_OPTIONS)
DEBUG - Options support paper size 'US-Letter'.
DEBUG - Options support paper size 'A4'.
DEBUG - signal 'finished-process' emitted with data: set_option tl-y to 1
As the backend does not set it to 1, but back to 0.999984741210938, it should return SANE_INFO_INEXACT, but doesn't, which I think is a bug (perhaps you can report this to the SANE project). However, gscan2pdf should do better.
As a workaround, what happens if you don't set it to 1 (which is coming from your previous session)? i.e. if you are up to editing ~/.config/gscan2pdfrc and removing the 'tl-y': 1 entry from 'default-scan-options', then do so, or otherwise, delete or rename ~/.config/gscan2pdfrc, thereby leaving the option at 0.
In the mean time, I'll try to mock up a backend to reproduce your problem.
Hi Jeffrey,
I thank you very much for your explication.
I tried the following steps:
The program works now perfectly and I'm very glad to can proceed as normal!!
Thanks for your prompt and efficient collaboration!
Unfortunately I discovered now the next anomaly.
Changing brigliance or contrat <> 0, gscan2pdf fails also with the same error
Can you work with patches? If so, please try the attached patch. If not, I can build a .deb.
Hi,
I never worked with patches, but I could try to explore this domain. In
this case I would start to analyse the patch at the end of the month
because of holidays.
On the other hand, if the built of a .deb wouldn't take too much time for
you, I would appreciate your help.
In any case I thank you very much for your concern of the problem hoping
that even other users could benefit from your solution.
Very best regards
Wini 100
Am Di., 9. Juli 2019 um 12:36 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326Hi Jeffrey,
I found a recent message from you without content.
Therefore I checked my sourceforge account and found on the top right edge an update of gscan2pdf. After downloading and extraction I tried this version, which always don't permit to change the value of brightness and contrast.
Now I’m wondering if this update is really the last one considering my final problems or if I should try your patch later on.
Please try this.
Hi Jeffrey,
I'm back again and I apologize for the interruption.
Today I uninstalled completely and reinstalled gscan2pdf with your
gscan2pdf_2.5.5-0rc1_all.deb (attachment from Jul 07 2019).
Unfortunately the procedure of scanning is stopped and I get the
error: 'Operation
was cancelled.'
Would there be any advice?
Am Do., 11. Juli 2019 um 16:22 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326Please upgrade to 2.5.5 from the ppa and give me another log file, having reproduced the problem.
the logfile of version 2.5.5
Am So., 28. Juli 2019 um 12:41 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326Hi Jeffrey,
I installed the version 2.5.5 and deleted /home/.config/gscan2pdfrc.
The result is still 'Operation cancelled.'
You will find the logfile in attachment by separated email, because the link 'Add attachments' underneath goes only on the top of the page.
Thanks for the log file.
I see that you successfully scanned a colour page with a resolution of 50, then changed the resolution to 200, lowered the brightness and started a second scan, which was cancelled.
Did you cancel the scan? i.e. did you press the cancel button to the right of the progress bar, or the cancel button on the scanner?
What happens if you change the "image type" option to monochrome or grayscale?
Hi Jeffrey,
in the last log file I didn't touch any button. I only adjusted resolution
and brightness before scaning.
After several tryings with various 'image type' and without previous
./config/gscan2pdfrc I found the real reason of the error.
The error appears only, if I modify the value of brightness or contrast
different to '0'!
In the attached new log file I scanned with brightness 0 and brightness ><0
too. Each scan with brightness different to 0 was cancelled. When I started
the successif scan with 0 again even in the same session, the scan was
realized without problem.
Unfortunately I need a different value of brightness to adjust my
monochrome result.
Am Mo., 29. Juli 2019 um 09:33 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326Well spotted. In that case, I am fairly sure that you have a problem with the backend. To confirm this, please try:
which I assume will suffer the same problem with being cancelled.
If so, please report this to the SANE project (https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel)
Hi Jeffrey,
the command 'scanimage --brightness=5 > image.pnm' gives me a perfect
output.
Even if I modify the value of brightness, the scan procedure complete well!
Am Di., 30. Juli 2019 um 08:17 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326Thanks for the feedback. I see from the previous log:
i.e. the first scan was carried out with brightness=5.
Please try selecting "Cycle SANE handle after scan" in Edit/Preferences, then scan a couple of pages with and without brightness and contrast, and give me another log file.
Hi Jeffrey,
I dont know why the first scan with brightness=5 is marked as passed.
Before updating from ubuntu 1810 to 1903 the options brightness and
contrast were always working. Actually each time I modify brightness=<>0 or
contrast the error occurs and the scan is cancelled.
After selecting "Cycle SANE handle after scan" the result is still the same.
Am Mi., 31. Juli 2019 um 10:30 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326Thanks for the log and for your persistance.
I see you made several attempts at scans, all with the following options:
mode=Monochrome
The first scan, just with the above, succeeded.
Note that of the four scans that succeeded, one included brightness=-10 and one threshold=128, because setting an option does not clear the previous ones.
Assuming you haven't changed any options since the previous attempt, if you restart gscan2pdf, you will still have threshold=128. So please don't change that and try to scan.
Then please add, say brightness=5 and scan, which I assume will fail.
What happens if you then try to scan again without changing anything else?
In Edit/Preferences there is a option 'Force new scan job between pages'. What happens if you scan after enabling this?
Hi Jeffrey,
I thank you also very much for your endurance, but I'm very interested to
continue using gscan2pdf.
I'm wondering that the log file indicates under number 5 a successful scan,
because I don't remember this event. Each time I change the value of
brightness or/and contrast the scan is systematically cancelled.
Nevertheless repeating a scan with a changed value of brightness or/and
contrast will fail again.
I encountered the following problem for the last test. The option "Force
new scan job between pages" is gray and therefore inaccessible for me.
Am Do., 1. Aug. 2019 um 10:41 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326If you enable 'Allow batch scanning from flatbed' in Edit/Preferences, does it then allow you to enable "Force new scan job between pages"?
Enabling 'Allow batch scanning from flatbed' in Edit/Preferences, the
option 'Force new scan job between pages' becomes accessible.
Unfortunately also forcing a new scan has no influence to the acceptance of
modification of brightness/contrast.
Am Do., 1. Aug. 2019 um 14:55 Uhr schrieb Jeffrey Ratcliffe ra28145@users.sourceforge.net:
Related
Bugs:
#326I'm going to take this problem to the SANE dev mailing list, but I have a couple of suggestions for workaround in the mean time:
What happens if you set brightness=-5, threshold=80, and then threshold=0? Brightness should still be set to -5. Can you then scan?
In Edit/Preferences, you can set the frontend to scanimage. This is certainly much slower, but should allow you to scan.
Before I write to the SANE dev mailing list, please try the following: