updated 16.04 to 18.04 in my Virtualbox. After 2nd reboot this exc appeared

[Björn Kruse]

Can't say much more, the information:
This Ubuntu runs in a VirtualBox 5.2.0 r118431 (Qt5.6.2)
A default Ubuntu with nearly no additional stuff installed, which I use for quite some time now. Updated it today from 16.04 LTS to 18.04.1 LTS, because the OS suggested it.
A few (2 or 3) errors appeared during the updated, but I had no other choice than "continue".
After update to 18.04 finished I did a reboot. Logged in as "ubu", which was created during update.
Installing a German keyboard also resulted in an error.
I did another reboot and logged in as "Ubuntu user", which is the user account I used in 16.04
After logging in, the "system error" message popped up and requested me to report it.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Sun Sep 2 16:12:47 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2
InstallationDate: Installed on 2013-08-24 (1835 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-09-02 (0 days ago)

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1773859, so it 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.