This repository has been archived by the owner on Dec 18, 2019. It is now read-only.
Fujitsu SnapScan resolution not detected correctly #230
Labels
Milestone
Comments
|
Hm, the driver of your scanner probably returns the resolutions in a weird way. It's not the first time I've seen this kind of problem. I need you to do the following: It will list all the options provided by your scanner (including the resolution) and all their constraints. Can you give me the output of this script please ? |
|
Hi @jflesch, Sure: |
|
Woops, it was actually a regression. Darn. |
|
No worries, Merci! :-) |
Closed
|
Can you confirm that the fix is working please ? I'm thinking of releasing a version 0.1.1 with this fix, but I have no scanner returning the accepted resolutions like yours. |
|
I'm trying where that file is located in the current installation to apply the fix on it: |
|
For now, I would advise that you try the branch 'unstable'. Unfortunately the installation process has already evolved quite a bit between the 0.1 (stable) and the 0.2 (unstable). You will have to re-read the README. If TL;DR: |
|
By the way, if you decide to backport the patch, I must tell you that the target file has been moved between 0.1 (stable) and 0.2 (unstable):
|
|
Tried applying to the version i have the changes, but now have 2 behaviors: When only snapscan is connected, hitting Scan button i have: "Error while scanning: " (nothing more) in a pop-up. And in console: (doing second comment for other case) |
|
And with both scanners connected, i have infinite loop (had that also before the fix) until i press the exit button: |
|
Trying installing 0.2 unstable as 0.1 stable seems to still have those other bugs. Followed your instructions: Got: ImportError: You need So did after that (as suggested here: http://docs.cython.org/src/quickstart/install.html ): That finished a long compilation with lots of minor compilation notices, and at end I had: Reporting in next comment on running 0.2: |
|
Running 0.2 with both scanners attached and pressing scan button: |
|
Removing the Epson stylus photo RX425 scaner/printer, output looks much better now, and resolutions are displayed correctly in the scaner settings. A scan worked! in terminal logs i got following warnings (if that may help): EDIT: UPDATED: And when quitting I get: |
|
It looks like the double-sided scan of the ScanSnap scanner isn't supported by PaperScan 0.2 unstable. BTW 0.2 unstable seems to work more stable than 0.1 stable ;) |
^ This one is actually a regression in Pyinsane. I just fixed it (pyinsane 1.2.1). To fix it: |
Known issue: #220
Known issue: pyinsane/#1 I think most of your other problems may be related to the regression in Pyinsane. |
|
Great! I could now reproduce one of the bugs as follows:
EDIT: fixed markup to make errors visible: If when pressing Scan, the configured scaner is not found, then the configuration dialog should appear instead of hanging and looping errors ? |
|
OK, yet another related issue (btw do you prefer me to open them as separate issues on github ?):
Output in terminal: |
ERROR paperwork.frontend.util.jobs 4: /usr/local/lib/python2.7/dist-packages/pyinsane/abstract_th.py: L 53: wait ^ This exception is normal. It is actually handled (a Gobject signal is sent) and then reraised. I do it because the exception caught is a bit too generic, so I prefer have the whole info anyway. ^ Fixed: ^ Fixed : 3792dae I think the remaining exceptions / errors are probably the result of these ones. |
Yes, I would prefer, because we are very far from the original issue now. |
I need a scanner to try this one. I don't have one right now (I'm not at home). I'll try it tomorrow evening. |
|
Thanks! No worries, no rush, this is free and libre open-source :-) Strangely the same works with the ScanSnap but not with the Epson. So not 100% sure you will be able to reproduce. To upgrade the 0.2 installed from git to confirm you the fixes above, what do I do after the git pull ? To install I did as you recommended: |
|
To upgrade: |
|
Ok, this time I have the nice new pop-up window: "No scanner found (is your scanner turned on ?)" : So at first it sounds good. But clicking "Ok", I have spinning mousepointer, and "Scanning ..." at bottom status. Here the errors reported in the terminal window between clicking Scan (with scanner off) and spinning wheel: |
|
The problem you need to reproduce is still there, this time I get PaperWork to quit on second Settings press with the Epson scanner, and this in terminal: |
|
Fixed by f63bc3a |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
getting following errors and no resolution displayed for the SnapScan scaner:
The text was updated successfully, but these errors were encountered: