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

Re: Pulseaudio not restarting after crash



On Wed, 2007-10-10 at 06:18 +0800, Hikaru Amano wrote:
> On 10/10/07, Lubomir Kundrak <lkundrak redhat com> wrote:
> > It's not a bug that it doesn't restart. Many services don't do so.
> > Respawning a dying daemon is not a good idea, because in case of
> > exploitation of a security issues, it would effectively defeat
> > randomization giving the attacker more tries, etc. etc.
> 
> it would be nice if theres something that would notify the user that
> pulseaudio terminated (and maybe ask permission to restart it) ...
> rather than silently quit and left the users wondering what happened
> to their pc sound and started blaming Fedora doesnt work ...

It would be a just blame. Pulseaudio should _not_ crash. Imagine if we
did thing such as this (the respawn) for about every thing that is
expected to run and can crash -- not a real solution.

> > The real problem is the crash. Do you have a core dump? Or at least
> > relevant lines from the log file? Are you able to reproduce the problem?
> > Please do file a bug in case you do/are.
> 
> ( I think i should use the term stopped rather than crashed )
> 
> I couldnt find the cause of pulseaudio stopping yet .. pulseaudio
> suddenly quits on random ..
> 
> the last time it terminated, pulseaudio gived out this error
> 
> [kagesenshi Hikari ~]$ while true;do pulseaudio ;echo "DIED";done
> Soft CPU time limit exhausted, terminating.
> E: module-volume-restore.c: failed to open file '(null)': No such file
> or directory
> DIED

I had exactly the same problem.
https://bugzilla.redhat.com/show_bug.cgi?id=322481
After I decided to hunt down the problem and compiled pulseaudio with
profiling data, I noticed, that I forgot respawining esd that was now
causing two instances of pulseaudio to run. No idea how does it relate,
but removing one kind of solved this problem for me. I'll return to it
once I have more time.

Please use that bug report to trace every piece of information you get about that.

-- 
Lubomir Kundrak (Red Hat Security Response Team)


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