Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#68529 - [sane] No brightness and contrast adjustments possible with Canon Lide40

Attached to Project: Arch Linux
Opened by Stefan (User__Stefan789) - Wednesday, 04 November 2020, 21:03 GMT
Last edited by David Runge (dvzrv) - Saturday, 19 February 2022, 20:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


After sane version 1.0.28-3 brightness and contrast could not be adjusted anymore, e.g. in simplescan or xsane. Brightness also not changing with scanimage via command line. This means that adjustments in the program (e.g. simple scan) do not take effect on the scanned document. I am using a Canon Lide40 scanner. Scanner driver: genesys.

My current version is sane 1.0.31-3. I used to work with v1.0.28-3, but this is not possible anymore with the latest arch update due to broken (old) dependencies with 1.0.28-3 (libusbx is not used in archlinux anymore).

Thank you very much.
This task depends upon

Closed by  David Runge (dvzrv)
Saturday, 19 February 2022, 20:03 GMT
Reason for closing:  Upstream
Comment by David Runge (dvzrv) - Tuesday, 16 February 2021, 10:52 GMT
@User__Stefan789: Thanks for the report!

Please give 1.0.32-2 in [testing] a try and report back whether it fixes the issue you see.
Comment by Stefan (User__Stefan789) - Thursday, 18 February 2021, 16:26 GMT
I could not find 1.0.32-2 but the next version 1.0.32-3 in [testing].
Unfortunately 1.0.32-3 [testing] did not resolve the issue. Still no changes in brightness or contrast.
Thank you.
Comment by David Runge (dvzrv) - Thursday, 18 February 2021, 16:50 GMT
@User__Stefan789: It seems that someone reported this behavior upstream [1].
A suggested fix does not seem to be considered very well implemented yet though [2].

This is an upstream issue and it is not related to the packaging of sane.