On 10/10/07, Lubomir Kundrak <lkundrak@xxxxxxxxxx> 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 ... > > 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 > > > but the daemon is not running so I had to delete the folder manually .. > > This is the following bug: > https://bugzilla.redhat.com/show_bug.cgi?id=299131 > I somehow had to delete that directory manually also, though I don't > remember the actual setting anymore. Probably it is derived from $USER > rather than from the effective id and gets created when you start the > daemon as another user or whatever. It is also a (though pretty low > severity) denial of service condition. -- Mohd Izhar Firdaus Bin Ismail Amano Hikaru 天野晃 「あまの ひかる」 http://fedoraproject.org/wiki/MohdIzharFirdaus http://blog.kagesenshi.org 92C2 B295 B40B B3DC 6866 5011 5BD2 584A 8A5D 7331 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
