Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Crash when restarting Pulseaudio #45

Closed
pabloab opened this issue Feb 21, 2017 · 3 comments
Closed

Crash when restarting Pulseaudio #45

pabloab opened this issue Feb 21, 2017 · 3 comments
Labels
enhancement resolved in dev The issue is resolved in dev branch but not released yet

Comments

@pabloab
Copy link

pabloab commented Feb 21, 2017

I was trying paprefs to output simultaneously when notice indicator-sound-switcher crash always I (kill and)restart Pulseaudio (pulseaudio -k).
Using v2.1.1, Ubuntu 16.04 and pulseaudio 8.0.

@yktoo
Copy link
Owner

yktoo commented Feb 21, 2017

Well yes, SSI doesn't account for PulseAudio dying while it's running. For me, it actually shows a critical error CRI Context failed. I'm not sure it's a problem really, obviously a sound switcher cannot function without the sound server. Perhaps exiting after PA has gone offline would be more consistent.

@pabloab
Copy link
Author

pabloab commented Feb 21, 2017

Maybe instead of crashing could handle/catch the situation, for example keep waiting to PA to come back (as usually happens after a pulseaudio -k). Also maybe could send a warning to notify-osd.

@yktoo
Copy link
Owner

yktoo commented Feb 23, 2017

I wholeheartedly agree that nothing should ever crash, but in my case there was no crash, just a log message with CRITICAL status. I'll think what can be done here.

yktoo added a commit that referenced this issue Jun 16, 2019
@yktoo yktoo added enhancement resolved in dev The issue is resolved in dev branch but not released yet labels Jun 16, 2019
@yktoo yktoo closed this as completed Jul 21, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement resolved in dev The issue is resolved in dev branch but not released yet
Projects
None yet
Development

No branches or pull requests

2 participants