pulseaudio crashed with SIGABRT in main()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This occurred during initial boot. The message appeared on-screen shortly after the desktop appeared.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:6.0-0ubuntu6
ProcVersionSign
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CrashCounter: 1
Date: Tue Apr 28 15:10:30 2015
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2014-10-03 (206 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=en_GB:en
XDG_RUNTIME_
LANG=en_GB.UTF-8
SHELL=/bin/false
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
?? () from /usr/lib/
main ()
Title: pulseaudio crashed with SIGABRT in main()
UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago)
UserGroups:
dmi.bios.date: 06/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1601
dmi.board.
dmi.board.name: A88XM-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1425447, so 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. Please continue to report any other bugs you may find.