package blueman 2.0.4-1ubuntu2 failed to install/upgrade: package blueman is not ready for configuration cannot configure (current status 'half-installed')

Bug #1683082 reported by Allan L McCoy
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

  python3-ptyprocess python3-renderpm python3-reportlab
  python3-reportlab-accel snap-confine ubuntu-core-launcher xsane-common
0 upgraded, 0 newly installed, 173 to remove and 1 not upgraded.
3 not fully installed or removed.
Need to get 0 B/2,782 kB of archives.
After this operation, 5,982 MB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 1915149 files and directories currently installed.)
Removing gcc-4.8-base:i386 (4.8.5-4ubuntu2) ...
Removing gcc-4.9-base:i386 (4.9.3-13ubuntu2) ...
Removing libgtk-3-0:i386 (3.18.9-1ubuntu3.2) ...
dpkg: unrecoverable fatal error, aborting:
 fork failed: Cannot allocate memory
E: Sub-process /usr/bin/dpkg returned an error code (2)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: blueman 2.0.4-1ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat Apr 15 18:42:51 2017
DuplicateSignature:
 package:blueman:2.0.4-1ubuntu2
 Setting up ntpdate (1:4.2.8p4+dfsg-3ubuntu5.4) ...
 dpkg: error processing package blueman (--configure):
  package blueman is not ready for configuration
ErrorMessage: package blueman is not ready for configuration cannot configure (current status 'half-installed')
InstallationDate: Installed on 2014-10-03 (925 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.19
SourcePackage: blueman
Title: package blueman 2.0.4-1ubuntu2 failed to install/upgrade: package blueman is not ready for configuration cannot configure (current status 'half-installed')
UpgradeStatus: Upgraded to xenial on 2016-07-29 (260 days ago)

Revision history for this message
Allan L McCoy (8-curly) wrote :
tags: removed: need-duplicate-check
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
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.