update-manager crashed with Depends in _show_transaction(): libsystemd0 (= 234-2ubuntu12) but 234-2ubuntu12.1 is installed

[Jillie Beam]

it says updates were broken..

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: update-manager 1:17.10.11
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 13 14:39:40 2017
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
 b'com.ubuntu.update-manager' b'first-run' b'false'
 b'com.ubuntu.update-manager' b'launch-time' b'int64 1510582719'
InstallationDate: Installed on 2017-11-13 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonArgs: ['/usr/bin/update-manager']
PythonDetails: /home/zeus/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/home/zeus/Error: command ['which', 'python'] failed with exit code 1:": "/home/zeus/Error: command ['which', 'python'] failed with exit code 1:", unpackaged
SourcePackage: update-manager
Title: update-manager crashed with Depends in _show_transaction(): libsystemd0 (= 234-2ubuntu12) but 234-2ubuntu12.1 is installed
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[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.