Unfunctional plustek scanner in Ubuntu 20.10

It would be great if you would able to compile previous working Sane version, and bisect when the issue starts appearing.
More information about git bisect is available at:
https://www.metaltoad.com/blog/beginners-guide-git-bisect-process-elimination

Both current master and 1.0.31 work like a charm when I compile them myself, dynamic and static loaded backend. So there's not much to bisect for me?
If I relink the packaged libsane-plustek.so.1 to my compiled version in /usr/local/lib everything also works (with the packaged scanimage).

On 2020-10-07 22:23, mrvanes wrote:
> Both current master and 1.0.31 work like a charm when I compile them
> myself, dynamic and static loaded backend.

That indicates some packaging issue, doesn't it? If you agree, it would be good if you could inform about it on the Debian bug.

Status changed to 'Confirmed' because the bug affects multiple users.

The Debian bug has some comments stating that creating /var/lock/sane is enough to make things work, could you confirm if that's the case for you?

Yes, creating /var/lock/sane resolves the problem (for me) in 1.0.31. The problem is that /var/lock is a temp fs under Debian/Ubuntu and thus should be recreated on every boot, instead of once during installation (or by sane on startup).

This bug was fixed in the package sane-backends - 1.0.31-2ubuntu1

---------------
sane-backends (1.0.31-2ubuntu1) hirsute; urgency=medium

  * debian/rules:
    - build again with --disable-locking since the feature currently
      not working correctly (lp: #1898905)

 -- Sebastien Bacher <email address hidden> Thu, 29 Oct 2020 13:08:07 +0100

Hello mrvanes, or anyone else affected,

Accepted sane-backends into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sane-backends/1.0.31-2ubuntu0.20.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted sane-backends (1.0.31-2ubuntu0.20.10) for groovy have finished running.
The following regressions have been reported in tests triggered by the package:

gscan2pdf/2.8.2-1ubuntu2 (arm64, armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/groovy/update_excuses.html#sane-backends

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

libsane1 1.0.31-2ubuntu0.20.10 from groovy-proposed fixes the problem for me.
Thx for taking care of this

Thanks for testing, marking as verified.

The autopkgtest regression on arm sounds like flaky tests rather than an issue with the update, they have been retried now

This bug was fixed in the package sane-backends - 1.0.31-2ubuntu0.20.10

---------------
sane-backends (1.0.31-2ubuntu0.20.10) groovy; urgency=medium

  * debian/rules:
    - build again with --disable-locking since the feature is currently
      not working correctly (lp: #1898905)

 -- Sebastien Bacher <email address hidden> Tue, 03 Nov 2020 17:30:51 +0100

The verification of the Stable Release Update for sane-backends has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.