Bug 369074 - PA error handling is not graceful, infinite crash-restart loop.
Summary: PA error handling is not graceful, infinite crash-restart loop.
Status: RESOLVED DUPLICATE of bug 369073
Alias: None
Product: plasma-pa
Classification: Plasma
Component: general (show other bugs)
Version: 5.7.3
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-19 19:15 UTC by kdebuac.rhn
Modified: 2016-09-21 08:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The console log of what seems to be the first crash in chain. (78.07 KB, text/plain)
2016-09-19 19:16 UTC, kdebuac.rhn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kdebuac.rhn 2016-09-19 19:15:10 UTC
Graceful handling of PulseAudio problems doesn't always kick in, but instead the applet crashes, taking the whole plasma shell into an infinite crash-restart loop.

The bug doesn't occur immediately when PulseAudio encounters, but when the applet is initialized (plasma restart or applet added).

This particular instance comes from a misconfigured Docker container.

Reproducible: Always

Steps to Reproduce:
1. Create Docker container with `--privileged -v /dev/dri:/dev/dri:rw -v /dev/shm:/dev/shm:rw -v /run/user/1000/pulse:/run/user/1000/pulse:rw`
2. Enable network access to PA via paprefs
3. Run inside Docker `PULSE_SERVER=$HOST paplay $SOUND.wav`
4. Restart plasma `kbuildsycoca5 && kquitapp5 plasmashell && kstart5 plasmashell`

Actual Results:  
PA goes into a broken state, Plasma shell crashes while starting, Plasma shell is restarted, Plasma shell crashes while starting, etc.

Expected Results:  
PA goes into a broken state, PA applet doesn't work, Plasma works.

Workaround: when Plasma gets into the crash loop, issue `pulseaudio -k`. If that is not enough, then manually restart it again.

Similar to bug 353177
Comment 1 kdebuac.rhn 2016-09-19 19:16:21 UTC
Created attachment 101187 [details]
The console log of what seems to be the first crash in chain.
Comment 2 David Rosca 2016-09-21 08:22:56 UTC

*** This bug has been marked as a duplicate of bug 369073 ***