I received the following from one of our users, I think it might help. I've done the Ubuntu 10.04 install from 31st March and updated relevant packages including the latest kernel 2.6.32-19, then installed g++ and allegro4.2.4. When I selected allegro for installation, it selected the liballegro4.2-4-plugin-jack and omitted the liballegro4.2-4-plugin-esd. I left the esd plugin uninstalled.
Atanks 4.4 built as usual and the sound failed first off. However, this time, selecting the OSS sound driver fixed the sound. Reverting it back to autodetect brings back the bug. Strangely, I've got a /tmp/pulse* file with gdm.gdm group/user ownership in addition to mine. Blowing away my /tmp/pulse* file and leaving the one with gdm ownership and leaving atanks with autodetect sound resulted in sound working. Looks like your suggested fix of setting OSS on Ubuntu should pretty well do the trick, although there may be a much smaller population that have the problem I had early on, where changing to OSS didn't fix the problem. Then again, if atanks works first time in Ubuntu with the default selection of OSS, there won't be any need to blow away the /tmp/pulse* directory. I plan to mention removing the /tmp/pulse files in our upstream documentation. For now, I'm going to create a patch that'll check to see if the UBUNTU symbol has been defined. If it has, the system will default to the OSS driver, rather than letting the sound system pick its own. Hopefully that'll clear up the issue. If the maintainer for the package could add a "-DUBUNTU" flag to the down-stream makefile, that would be helpful. -- No sound in battle tanks (atanks) https://bugs.launchpad.net/bugs/385406 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
