package blueman 2.0.4-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1602709 reported by Danushka
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
High
Unassigned

Bug Description

AFTER REINSTALL FOLLOWING SHOWED UP, SO looks like the issue can be resolved with reinstall.

BUT this BUG arose when doing debootstrap.

dan@ACER:~$ sudo dpkg-reconfigure blueman
[sudo] password for dan:
/usr/sbin/dpkg-reconfigure: blueman is broken or not fully installed
dan@ACER:~$ sudo apt-get install blueman
Reading package lists... Done
Building dependency tree
Reading state information... Done
blueman is already the newest version (2.0.4-1ubuntu2).
blueman set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up blueman (2.0.4-1ubuntu2) ...
Setting up lubuntu-desktop (0.65) ...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: blueman 2.0.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
AptOrdering:
 blueman: Configure
 lubuntu-desktop: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Jul 13 19:36:11 2016
Df:
 Filesystem 1K-blocks Used Available Use% Mounted on
 /dev/sda11 41152220 3882040 35156728 10% /
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.12~ubuntu16.04.1
SourcePackage: blueman
Title: package blueman 2.0.4-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Danushka (danushka) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in blueman (Ubuntu):
status: New → Confirmed
Changed in blueman (Ubuntu):
importance: Undecided → High
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.