Summary: | esound 0.2.37-r1, and signal blockage after long periods. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Brian Beardall <brian> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | totem debug after lockup regarding this issue. |
Description
Brian Beardall
2007-04-05 02:32:52 UTC
I don't think any of us really uses esound ... please check in gnome's bugzilla for similar bugs, that's the only thing I can recommend right now. Thanks for reporting this bug Created attachment 115530 [details]
totem debug after lockup regarding this issue.
I looked at gnome bugzilla and didn't find anything like this. This bug just showed with the latest esound.
Do you have esound in the default runlevel? The new version disables autospawning of esound in its global configuration file (assuming you updated the conf file with etc-update or similar), and that MIGHT cause problems like this. Note that autospawning was disabled by default (and therefore requiring /etc/init.d/esound to be in running status when system sounds are used) due to many issues with the autospawning. It might also be possible that you still have autospawning on, and you now hit one of those issues it was having. While none of this might help out, if you do use esound please make sure that you have esound through the init script running and not relying on autospawning. If that doesn't help for this, it at least takes other possible problems affecting this out of the equation. Other than that I can only point at upstream too :( Hopefully esound will go away eventually and not too far in the future (PulseAudio and/or gstreamer are the way upstream wants to move eventually). I had it loaded in the default run level. However that caused audio programs to lockup of the long term. I've since removed it from the default run level, and set it to autospawn and I haven't had a problem since. closing as fixed per comment #4 |