package kio-extras 4:15.12.3-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd_fileitem_linking_plugin.so', which is also in package kactivities 5.18.0-0ubuntu1

[specialk74]

During upgrade from Ubuntu 16.04 to 16.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: kio-extras 4:15.12.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Wed Nov 16 07:15:31 2016
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd_fileitem_linking_plugin.so', which is also in package kactivities 5.18.0-0ubuntu1
InstallationDate: Installed on 2014-10-26 (751 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.1
SourcePackage: kio-extras
Title: package kio-extras 4:15.12.3-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/qt5/plugins/kactivitymanagerd_fileitem_linking_plugin.so', which is also in package kactivities 5.18.0-0ubuntu1
UpgradeStatus: Upgraded to yakkety on 2016-11-13 (2 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[misko (michael-wagner-gmx)]

I have the same issue, occured just now when trying to update from kubuntu 16.4 to 16.10.
What can I do to finish the upgrade? (I don't dare to restart my computer right now ...)

[misko (michael-wagner-gmx)]

Further information:
In my case, the situation happened when updating Kubuntu (16.4 to 16.10) from command line using, and after do-release-upgrade crashed during update.
Google adviced me to try apt-get -f install - then the error described above happened.
After retrying "apt-get -f install", "apt-get update", "apt-get upgrade", "apt-get dist-upgrade" a few times, the installation finally completed without errors.

So this bug seems to be a side-effect of another bug in do-release-upgrade .