Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unusual sensor #18

Open
btro1404 opened this issue Feb 14, 2021 · 2 comments
Open

Unusual sensor #18

btro1404 opened this issue Feb 14, 2021 · 2 comments

Comments

@btro1404
Copy link

Hey Alex,

I checked out a Canon "CanoScan LIDE 20" with insaned and it doesn't work together. I think it's because of the unusual name of the buttons that contains a space in their name:

$ insaned -L
List of sensors for device 'plustek:libusb:001:008':
    button 0    [no]
    button 1    [no]
    button 2    [no]

If I press a button, I expected a syslog entry of a missing script handler but there is no one.
Do you see a possibility to support these unusual names to use the scanner together with insaned?

Thank you, and
Gruß Bernd

@hannesrauhe
Copy link

Looking at this line:
if (system((handler + " " + mCurrentDevice).c_str()) < 0) {

I guess, insaned will execute a script named "button" and put 0,1,2 as first parameter.
Running ./insaned --dont-fork -vv (stop the service before), should give you some more information....

@btro1404
Copy link
Author

btro1404 commented Mar 6, 2021

No, you are wrong: A script named button isn't executed. And insaned --dont-fork -vv do not give a hint because it do not notice about a pressed button

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants