pulseaudio dies randomly when not in 2.0 output

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



the process is killed.

julie at silverstone:~$ LANG=C pulseaudio -vvvv --log-time=1 >
~/pulseverbose.log>&1
Killed

julie at silverstone:~$ tail -f pulseverbose.log
(   0.004|   0.000) I: [pulseaudio] main.c: System supports high resolution
timers
(   0.004|   0.000) D: [pulseaudio] memblock.c: Using shared memory pool
with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum
usable slot size is 65472
(   0.005|   0.000) D: [pulseaudio] memblock.c: Using shared memory pool
with 1024 slots of size 64.0 KiB each, total size is 64.0 MiB, maximum
usable slot size is 65472
(   0.005|   0.000) I: [pulseaudio] cpu-x86.c: CPU flags: CMOV MMX SSE SSE2
SSE3 SSSE3 SSE4_1 SSE4_2 MMXEXT
(   0.005|   0.000) I: [pulseaudio] svolume_mmx.c: Initialising MMX
optimized volume functions.
(   0.005|   0.000) I: [pulseaudio] remap_mmx.c: Initialising MMX optimized
remappers.
(   0.005|   0.000) I: [pulseaudio] svolume_sse.c: Initialising SSE2
optimized volume functions.
(   0.005|   0.000) I: [pulseaudio] remap_sse.c: Initialising SSE2
optimized remappers.
(   0.005|   0.000) I: [pulseaudio] sconv_sse.c: Initialising SSE2
optimized conversions.
(   0.005|   0.000) I: [pulseaudio] svolume_orc.c: Initialising ORC
optimized volume functions.




On Fri, Mar 31, 2017 at 6:00 AM, Tanu Kaskinen <tanuk at iki.fi> wrote:

> On Wed, 2017-03-29 at 10:32 +1300, John Nunnington wrote:
> > I'm running Ubuntu 16.10 and 16.04, and I get repeatable failures in
> > Spotify that are caused by the pulseaudio daemon dying.
> >
> > I don't get this issue when my sound is configured in analog-stereo
> through
> > the sound card, or when outputing to the speaker system through the
> > motherboard (which is 2.0 anyway). Any other configuration
> > (4.0,4.1,5.05.1), fails within 5-25 minutes.
> >
> > I've reported this through ubuntu-bugs but nothing seems to happen.
> >
> > Can anybody either confirm they've seen this before, or tell me how I can
> > gather some additional information to assist resolving this ??
>
> How does it die? Does it abort due to an assertion failure, or does a
> segmentation fault happen, or does it get killed? If you don't know,
> and you don't find the information from the syslog, run pulseaudio in a
> terminal. Instructions for running pulseaudio in a terminal can be
> found here: https://wiki.ubuntu.com/PulseAudio/Log
>
> --
> Tanu
>
> https://www.patreon.com/tanuk
> _______________________________________________
> pulseaudio-discuss mailing list
> pulseaudio-discuss at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20170331/c138c27b/attachment.html>


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux