Description of problem: in manaplus, i noticed that hit sounds was significantly slower to start than it should be, so i did some testing: i did "aplay /usr/share/sounds/purple/alert.wav" (from pidgin), but it seemed to start immediately i then wrote a small SDL_mixer app that plays a wav file, see http://paste.pocoo.org/show/453886/ (i compiled with "-lSDL_mixer -I/usr/include/SDL" ) and tested with the same wav file. then sent this to a friend and he had it running at +0.1 ; while i had it at +0.6. after i disabled pulseaudio, it seemed to play at +0.1 as well... after this i compiled the program on my mandriva 2010.1 (with pulseaudio) and it ran at +0.1 as well. thus i kind of conclude that pa on mageia seems to have an extra 0.5 sec delay. is there anything else i can do to help? (this is on a vbox VM)
CC: (none) => mageia
Did all your other tests happen on non-VMs? i.e. did all the ones that are 0.1s happen on bare metal and all the 0.5s ones happen via a hypervisor?
no, everything is on the same VM, except for the mandriva, that was not a VM
in fact, i just mv libpulse to somewhere else for that second test, and moving that lib away made the whole thing 0.5s faster can you reproduce?
The test case works fine for me. I strongly suspect that it's a driver timing issue. Does adding tsched=0 to the "load-module module-udev-detect" line in default.pa help kill off the delay?
It seems to help a tiny bit, (like +0.1s), but not completely
bump?
Without being able to reproduce this, there is very little I can do. One question, do you ssh in to your VM box or login directly? If you SSH in then you may be trying to connect to the remote PA on the machine that you connect from. If there is a firewall that could result in a connection timeout which could account for the delay.
no, not using ssh. is anyone else able to reproduce?
Assigning to maintainer now that our maintainers database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me.
CC: (none) => stormiAssignee: bugsquad => mageia
I'm still not able to reproduce. If it would be possible I can perhaps SSH into your machine with an account with appropriate permissions? If this is potentially possible, please drop me a line on IRC.
ok, that should be possible
(In reply to comment #10) > I'm still not able to reproduce. If it would be possible I can perhaps SSH into > your machine with an account with appropriate permissions? If this is > potentially possible, please drop me a line on IRC. (In reply to comment #11) > ok, that should be possible Does that still need to be done? @ Colin Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
CC: (none) => marja11
3-monthly ping
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
colin, can you relook at this? if i remember correctly, you were able to reproduce at a later time...
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX