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. ** Changed in: sane-backends (Ubuntu Groovy) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1898905 Title: Unfunctional plustek scanner in Ubuntu 20.10 Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Groovy: Fix Committed Status in sane-backends package in Debian: Unknown 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://gitlab.com/sane-project/backends/-/issues/363 Another report: https://gitlab.com/sane-project/backends/-/issues/360 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971584 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1898905/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
