package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package account-plugin-google 0.13+16.10.20160929.1-0ubuntu1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kaccounts-providers (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Attempted to install KDE Plasma 5.8.5 on fresh install of Ubuntu 16.10. Installation failed:
Errors were encountered while processing:
/temp/apt-
E: Sub-process /usr/bin/dpkg returned an error code(1)
Used possible solution:
sudo dpkg --configure -a
Attempted reinstall sudo apt-get install kubuntu-desktop
Response: already installed
Restarted. KDE failed to load. Now getting above error.
Additional info:
=======
Description: Ubuntu 16.10
Release: 16.10
=======
Package: kaccounts-Providers 4:16.04.3-Oubuntu1
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: kaccounts-providers (not installed)
ProcVersionSign
Uname: Linux 4.8.0-37-generic i686
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
Date: Tue Feb 7 11:25:53 2017
DuplicateSignature:
package:
Unpacking kaccounts-providers (4:16.04.
dpkg: error processing archive /tmp/apt-
trying to overwrite '/etc/signon-
ErrorMessage: trying to overwrite '/etc/signon-
InstallationDate: Installed on 2017-02-07 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
RelatedPackageV
dpkg 1.18.10ubuntu1
apt 1.3.4
SourcePackage: kaccounts-providers
Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-
UpgradeStatus: Upgraded to yakkety on 2017-02-07 (0 days ago)
tags: | removed: need-duplicate-check |
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 1622499, 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. Feel free to continue to report any other bugs you may find.