Unfunctional plustek scanner in Ubuntu 20.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sane-backends (Debian) |
Fix Released
|
Unknown
|
|||
sane-backends (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
* Impact
The plustek driver isn't working in 20.10
* Test case
Try doing a copy of a document on a plustek based device
* Regression potential
The locking option was disabled until 20.10, the locking code relies on a lock directory to exist in /var/lock but that location is not persitant which means the locking can't work. Debian has turned the option off again, we are going the same in the SRU because it's safer than trying to fix an option that never got properly tested. There is special verification to do, just check that plustek and other devices are working correctly.
-------
There are multiple reports now of failing plustek backend in libsane 1.0.31-2 as shipped in Ubuntu 20.10 and Debian dev
My report:
https:/
Another report:
https:/
Debian bug report:
https:/
Changed in sane-backends (Ubuntu): | |
status: | Confirmed → Fix Committed |
description: | updated |
Changed in sane-backends (Debian): | |
status: | Unknown → Fix Released |
It would be great if you would able to compile previous working Sane version, and bisect when the issue starts appearing. /www.metaltoad. com/blog/ beginners- guide-git- bisect- process- elimination
More information about git bisect is available at:
https:/