* chuck <charlesr.har...@gmail.com> [2009-11-03 16:47:09 CET]: > Shouldn't Wesnoth work out of the box on freshly installed Karmic Koala?
Of course it should. > It's not *my* sound setup, it's Karmic's. Right, and that one is broken, please check the referenced bug report. And actually, it is the way the sound setup on *your* system is handled, even if it's done by regular karmic install. I don't decline that there is a bug, far from it - it just isn't in wesnoth but in libsdl. > If libsdl1.2debian-pulseaudio is needed for Wesnoth on a standard > install, then it is a dependency of Wesnoth. If it isn't a dependency, > then that sure looks like a bug to me. Erm, no, it's not that easy. wesnoth works with *any* SDL capable sound system. Though, that sound system needs to be proper setup. wesnoth (and other SDL applications) don't enforce any specific sound setup and leaves you the choice. It's just an error in the default dependency chain that is done within the *libsdl* packages that is causing the troubles. There is nothing that wesnoth can do for you that isn't just a dirty hack. Fixing it on the proper place is the right thing to do and the way to go. Limiting users of wesnoth to pulseaudio isn't a proper way and I definitely don't want to go down that road. Hope this was a bit more clear and understandable. :) Rhonda -- wesnoth no sound, high cpu usage, can't quit without freezing the application https://bugs.launchpad.net/bugs/442535 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
