Comment 2 for bug 1869107

Without looking at the deb file, this is likely a regression of 2.0 which was fixed in the recently released 2.0.1 in Debian. Pretty sure that will eventually flow into Ubuntu as well. See the commit in question for details if you are interested: https://salsa.debian.org/apt-team/apt/-/commit/bf46e09f0e4b52b3c71ac20bb11e7511fc16179f

That the scanner doesn't seem to work for you is orthogonal to this issue. You might want to contact a support channel of Ubuntu about this with more details – bugreports tend not be a good place for getting hardware to behave with drivers in third-party packages. Thanks for reporting your issue none the less!