Pulseaudio crashes on startup of rhythmbox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Starting up rhythmbox lets pulseaudio crash. The applet in the ubuntu status bar shows no audio possible, and hotkeys for audio level do also refuse to work.
$ lsb_release -rd
Description: Ubuntu 16.04.2 LTS
Release: 16.04
$ apt-cache policy rhythmbox
rhythmbox:
Installiert: 3.3-1ubuntu7
Installations
Versionstabelle:
*** 3.3-1ubuntu7 500
500 http://
100 /var/lib/
$ apt-cache policy pulseaudio
pulseaudio:
Installiert: 1:8.0-0ubuntu3.2
Installations
Versionstabelle:
*** 1:8.0-0ubuntu3.2 500
500 http://
100 /var/lib/
1:8.0-0ubuntu3 500
500 http://
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.2
ProcVersionSign
Uname: Linux 4.4.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/
CurrentDesktop: Unity
Date: Fri Feb 17 07:48:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-04-22 (300 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04
dmi.board.
dmi.board.name: W65_W67RZ
dmi.board.vendor: TUXEDO
dmi.board.version: Not Applicable
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TUXEDO
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: W65_W67RZ
dmi.product.
dmi.sys.vendor: TUXEDO
modified.
mtime.conffile.
Thank you for reporting this bug to Ubuntu.
If it is pulseaudio crashing then it's likely that's already been reported via https:/ /errors. ubuntu. com/
If you would like to actively debug the problem however then we will need a stack trace from your particular crash. In that case, please try to obtain a backtrace following the instructions at http:// wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.