package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1631172 reported by Anthony Di Franco
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
click (Ubuntu)
Confirmed
Undecided
Unassigned
unity-scopes-api (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

appears upon logging in

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8
Uname: Linux 4.8.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Wed Oct 5 19:25:54 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-07-01 (96 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.1
SourcePackage: unity-scopes-api
Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-10-04 (2 days ago)

Revision history for this message
Anthony Di Franco (di-franco) wrote :
Revision history for this message
Paweł Stołowski (stolowski) wrote :

Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
Traceback (most recent call last):
  File "/usr/bin/click", line 55, in <module>
    from click import commands
ImportError: cannot import name 'commands'
dpkg: error processing package libunity-scopes1.0:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1

It looks like click failed, perhaps click and/or its dependencies needs upgrading. In any case, libunity-scopes package is innocent here.

Changed in unity-scopes-api (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in click (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.