I have not tracked down the steps leading to the problem. Did some research, and tracked the problem to deluge. Seems that the sound notification routines that it pulls from pygame, or how it uses it locks the sound device. Can be resolved by stopping/killing deluge. I do not even have the notification active. Made patch that removes the routine, and also removes the option in the preferences tab. Just commented out the code, not deleted. Compiles fine, runs fine, now. Reproducible: Sometimes Steps to Reproduce: 1. Run deluge gtk gui 2. Let run for (at present) unknown amount of time (Seems to be over 1 hour) 3. Run other application that need sound 4. No sound Actual Results: No applications can use the device. Mplayer, Firefox, mpg123, games. Deluge needs to be quitted/stopped/killed to release the device. Attaching patch I made that removes(comments out) 99% of references to the sound notification, including the UI reference for the preferences. Left the actual initial definition as a stub.
Created attachment 217348 [details, diff] Patch that removes references to sound in the gtk user interface
Still exists. Patch did not work. Must be a different section. Will continue to dig. Only thing I have to provoke this bug so far is time. Will go through the logs a bit more, and see what else I can pull.
Is this still a problem with never versions of deluge? 1.1.9 is not in the tree anymore, so I guess you are using at least 1.2.0. Can you still reproduce?
