** Changed in: sane-backends (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898905
Title:
Unfunctional plustek scanner in Ubuntu 20.10
To manage
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
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
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You
libsane1 1.0.31-2ubuntu0.20.10 from groovy-proposed fixes the problem for me.
Thx for taking care of this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898905
Title:
Unfunctional plustek scanner
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
** Description changed:
+ * 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
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 Thu,
** Changed in: sane-backends (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898905
Title:
Unfunctional plustek scanner in Ubuntu 20.10
To manage
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).
--
You received this bug notification because you are a
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?
** Changed in: sane-backends (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sane-backends (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898905
** Bug watch added: Debian Bug tracker #971584
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584
** Also affects: sane-backends (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584
Importance: Unknown
Status: Unknown
--
You received this bug notification
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.
--
You received
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).
--
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
--
You received this bug notification
15 matches
Mail list logo
