update-manager crashed with Depends in _show_transaction(): libpython3-stdlib (= 3.6.1-0ubuntu3) but 3.6.1-0ubuntu3 is installed

[spike speigel]

After a failed python update crash:

https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1718042

Tried autoclean and clean, then this crash...

was going to try apt-get -f install to attempt to fix the issue...

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: update-manager 1:17.10.9
ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep 18 17:24:33 2017
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 b'com.ubuntu.update-manager' b'show-details' b'true'
 b'com.ubuntu.update-manager' b'window-height' b'481'
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'window-width' b'528'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1505773437'
InstallationDate: Installed on 2017-04-29 (141 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170408)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.2-1ubuntu1
PythonArgs: ['/usr/bin/update-manager']
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2
SourcePackage: update-manager
Title: update-manager crashed with Depends in _show_transaction(): libpython3-stdlib (= 3.6.1-0ubuntu3) but 3.6.1-0ubuntu3 is installed
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1203562, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.