On 29/10/15 16:55, Mike Blumenkrantz wrote: > I think you misunderstood both the commit message and the note in the > README, so perhaps more notes should be added. To summarize: > * xwayland module sets DISPLAY after pulse init, so at no point is the > variable actively unset > * nowhere does it say that the module needs to be loaded, only built > > The main issue is that pulseaudio forces checks for an X11 environment > before anything else--which is backwards--and this ensures deadlocking in > the case where a process internally uses pulseaudio and is also running the > xserver. Relatedly, there seems to be no way to use API to disable this > behavior, it can only be compiled out by disabling X11 support entirely. > A lesser issue is that ecore-audio creates its global pulseaudio connection > only upon creating the first audio object. In enlightenment, this > (currently) only occurs when typing for the first time in an internal > window's entry widget since this triggers the delightful key press sounds. > Without pre-initialization of ecore-audio's global connection, this > deadlocks the server if no previous X11 client has been launched. > The least significant issue is that ecore-audio provides no method for > determining what features it provides, meaning that I can only guess based > on whatever support is enabled by the user during build time. And even this > is not guaranteed to be correct. > > The best possible solution, for me, would be to completely disable > ecore-audio in internal windows if the xwayland module loads, at least > until pulseaudio fixes its internals to stop deadlocking. This seemed like > it would be unpopular for some, however, so I went with the solution which > was most likely to work for the majority of users.
If you ask me, I would disable typing sounds all around, but that's a whole different topic. Anyhow, I get it now. I thought you meant not loading when you said "disable", not "not building". That makes it less bad. Still weird though, I don't understand how having the module compile (but not loaded) would help. Also, can't we have configure fail if someone is trying to disable the mixer module? You don't need to reply to this email, I got the info I needed. All the questions above are only for you to consider alternative solutions, and not really questions I need to know the answers to. -- Tom. ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
