Ubuntu
bluez package

package bluez 5.48-0ubuntu3.1 failed to install/upgrade: instalado bluez paquete post-installation guión el subproceso devolvió un error con estado de salida 1

Bug #1781747 reported by Martin on 2018-07-14

This bug report is a duplicate of: Bug #1769800: package bluez failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ["Unable to get on D-Bus"]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	bluez (Ubuntu)	New	Undecided	Unassigned

Bug Description

I had the problem described here:
https://askubuntu.com/questions/641642/gui-does-not-start
So I run this commands in a terminal following a suggestion of an user:
sudo apt purge gdm gdm3
sudo apt install gdm3 ubuntu-desktop
systemctl restart gdm
After that brings up the report that I'm sending to you, related with bluez package.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Jul 14 19:02:53 2018
ErrorMessage: instalado bluez paquete post-installation guión el subproceso devolvió un error con estado de salida 1
InstallationDate: Installed on 2017-12-18 (208 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron 5423
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=cd8feae8-3880-4b62-b7a2-0046e75dc205 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2
apt 1.6.2
SourcePackage: bluez
Title: package bluez 5.48-0ubuntu3.1 failed to install/upgrade: instalado bluez paquete post-installation guión el subproceso devolvió un error con estado de salida 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/17/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0F45CW
dmi.board.vendor: Dell Inc.
dmi.board.version: A06
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: dmi:bvnDellInc.:bvrA06:bd09/17/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0F45CW:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 5423
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
  BD Address: E0:06:E6:D5:76:B2 ACL MTU: 1021:8 SCO MTU: 64:1
  DOWN
  RX bytes:886 acl:0 sco:0 events:36 errors:0
  TX bytes:386 acl:0 sco:0 commands:36 errors:0

Tags:

Revision history for this message

Martin (mgleria) wrote on 2018-07-14:

AptOrdering.txt Edit (2.0 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (59.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (441 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (55.5 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (4.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (14.7 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (22.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (671 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (4.1 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (3.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (162.5 KiB, text/plain; charset="utf-8")
getfacl.txt Edit (161 bytes, text/plain; charset="utf-8")
rfkill.txt Edit (175 bytes, text/plain; charset="utf-8")
syslog.txt Edit (2.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2018-07-16:

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 1769800, 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.