On Thu, 2008-03-13 at 09:36 -0700, Tom London wrote: > I've found pulse/sound to be pretty good, except for an issue with how > the pulseaudio daemon starts: > https://bugzilla.redhat.com/show_bug.cgi?id=425763 > > It seems that sometimes on reboot, pulse gets confused and thinks > there already is a copy of the daemon running, and so doesn't start > one. > > If you have the "sometimes pulse works and sometimes it doesn't on > reboot" situation, you may want to jump on the above BZ. [There is a > hack described there that seems to paper over the issue for me.] I've run in to this myself. Pulse dies or hangs for some reason, leaving the lockfile. Then it refuses to start again. Drove me nuts, it took an strace run to figure out the lockfile was in /tmp, and not ~/. This is not documented in any obvious place. And there's no command line option to force start or force cleanup. Epic fail. Don't we have *libraries* that get this lockfile stuff right? Seems like something rather fundamental to unix programming. And yet people still manage to do it wrong.
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
