GNOME Bugzilla – Bug 334478
when asked to standby, esd doesn't release the device fast enough
Last modified: 2012-02-28 20:32:53 UTC
Please describe the problem: Using the alsa backend, it seems that under some circumstances, esd doesn't release the audio device fast enough, causing the problems described in bug 330586. Just making the client application sleep for 100ms before claiming the device was enough to make it work. Steps to reproduce: 1. Start esd in daemon mode. 2. Start ekiga 1.99 3. run the configuration wizard 4. test the sound Actual results: A dialog saying that the audio device couldn't be opened is displayed. Expected results: ekiga should be able to open the audio device, since it asked esd to standby before. Does this happen every time? Yes Other information:
*** Bug 335089 has been marked as a duplicate of this bug. ***
There are a lot of usleep(100) in esound's code related to server resume. Maybe some usleep(100) should be added for server standby too ? Also, in clients.c, there's a usleep(100) after the call to esd_server_resume. In proto.c, there's none after the call to esd_server_resume. Maybe one should be added, or maybe it should be moved to esd.c:esd_server_resume ?
I only see usleep()s in the osf backend.
And one nanosleep() in esd.c
"esound" has not seen code changes for more than three years according to http://git.gnome.org/browse/esound/log/ , and it will not see further active development anymore according to its developers. Closing this report as WONTFIX - Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again.