On 10.12.2010 10:28, Ibán Cereijo wrote:
Hi,

Thank you for your report.

If the bug appears when you have selected JACK as your audio system, I think
I've already solved the problem in the incoming release 0.8.2:

https://savannah.nongnu.org/bugs/index.php?31369

If the bug happens when you are running ALSA, I'm aware of it, but I haven't
fixed it yet

https://savannah.nongnu.org/bugs/index.php?31532

If this last case, I'm only able to reproduce the bug in very rare
situations, with a few sound cards, and when I change manually the audio
device to "hw:0". Have you modified the "audio device" field too?

We have a version ready for test (currently version 0.8.2beta4), please read
this if you want to try it (if you do, please tell us whether the bug is
still there):

http://lists.nongnu.org/archive/html/lingot-devel/2010-10/msg00001.html


Answering all questions:
1. Bug is systematic and I can reproduce it every run.
2. Lingot is not eating CPU - when non-responive it takes about 0-2% according to top - same as normal. 3. When stracing 0.8.1-1+b1, it hangs in a way I have to switch to text console and kill lingot. 4. I'm using ALSA, have not much experience with jackd, when I installed it I got 'cannot connect to jack server' (not sure if it was running).
arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: rev50 [VIA 82C686A/B rev50], device 0: VIA 82C686A/B rev50 [VIA 82C686A/B rev50]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
5. I cannot modify "audio device" - it's grayed out (0.8.2beta4).
6. Bug still exists in 0.8.2beta4
7. I belive it's something with preferences handling - it runs OK (and I can tune) after start, it hangs when I click those buttons in preferences.

In a few days I have to leave this computer for some time (weeks at least). Will check on other hardware if the bug still exists, if so, will try to debug it there.

Thanks,
Pawel



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to