package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to install/upgrade: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured because libsane:i386 is at a different version (1.0.25+git20150528-1ubuntu2)

[tom]

I don't know about this I am getting notified only about the bug rather than getting to know about the big

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Mon Jun 5 09:37:28 2017
DuplicateSignature:
 package:libsane:amd64:1.0.25+git20150528-1ubuntu2.16.10.1
 Unpacking libsane-common (1.0.25+git20150528-1ubuntu2.16.10.1) over (1.0.25+git20150528-1ubuntu2) ...
 dpkg: error processing package libsane:amd64 (--configure):
  package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured because libsane:i386 is at a different version (1.0.25+git20150528-1ubuntu2)
ErrorMessage: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured because libsane:i386 is at a different version (1.0.25+git20150528-1ubuntu2)
InstallationDate: Installed on 2017-03-29 (70 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.3
SourcePackage: sane-backends
Title: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 failed to install/upgrade: package libsane:amd64 1.0.25+git20150528-1ubuntu2.16.10.1 cannot be configured because libsane:i386 is at a different version (1.0.25+git20150528-1ubuntu2)
UpgradeStatus: No upgrade log present (probably fresh install)

[Marc Deslauriers (mdeslaur)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.