repar
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpulse0:amd64 1:8.0-0ubuntu3.2
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: jeudy 1673 F.... pulseaudio
/dev/snd/controlC0: jeudy 1673 F.... pulseaudio
Date: Thu Jan 19 20:06:17 2017
DuplicateSignature:
package:libpulse0:amd64:1:8.0-0ubuntu3.2
Processing triggers for mime-support (3.59ubuntu1) ...
dpkg: error processing package oracle-java8-installer (--configure):
package oracle-java8-installer is already installed and configured
ErrorMessage: package libpulse0:amd64 is already installed and configured
InstallationDate: Installed on 2017-01-15 (4 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.18
SourcePackage: dpkg
Title: package libpulse0:amd64 1:8.0-0ubuntu3.2 failed to install/upgrade: package libpulse0:amd64 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/20/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80BB
dmi.board.vendor: HP
dmi.board.version: KBC Version 94.12
dmi.chassis.asset.tag: 5CG5412P9M
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.21:bd07/20/2016:svnHP:pnHPNotebook:pvrCNB1:rvnHP:rn80BB:rvrKBCVersion94.12:cvnHP:ct10:cvrChassisVersion:
dmi.product.name: HP Notebook
dmi.product.version: CNB1
dmi.sys.vendor: HP
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.