pulseaudio crashed with SIGABRT in main()

[elhoir]

just did a dist-upgrade and rebooted

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:6.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-7.7-lowlatency 3.19.0
Uname: Linux 3.19.0-7-lowlatency x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: elhoir 14677 F...m pulseaudio
 /dev/snd/pcmC0D0p: elhoir 14677 F...m pulseaudio
 /dev/snd/controlC0: elhoir 14677 F.... pulseaudio
 /dev/snd/controlC1: elhoir 14677 F.... pulseaudio
Date: Wed Mar 11 00:43:14 2015
ExecutablePath: /usr/bin/pulseaudio
ExecutableTimestamp: 1424647281
InstallationDate: Installed on 2012-02-27 (1107 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcCwd: /
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.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/libpulsecore-6.0.so
 main ()
Title: pulseaudio crashed with SIGABRT in main()
UpgradeStatus: Upgraded to vivid on 2015-02-20 (19 days ago)
UserGroups:

dmi.bios.date: 01/15/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A7616MLN.10F
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MS-7616
dmi.board.vendor: MEDIONPC
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: MEDIONPC
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
dmi.product.name: MS-7616
dmi.product.version: 1.0
dmi.sys.vendor: MEDIONPC

[Apport retracing service (apport)]

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.