Options - change a value - Apply and Lingot Crashes

[paul123]

Binary package hint: lingot

Freshly installed Ubuntu Hardy 8.04 - I then updated fully - installed Lingot and a few other packages.

Lingot opens and runs ok until I open Options and Apply a change then it Vanishes from screen. Next I opened from Terminal to see the fault, when the problem occurs it gives this message 'Unable to open audio device /dev/dsp: Device or resource busy'. Started lingot again and went through system monitor to see what I could find running. Nothing obvious.

So next I tried this, I opened Lingot again and opened terminal and did this while lingot was running 'cat /dev/urandom > /dev/dsp'. The noise was present, so at this point /dev/dsp is not busy! Kill the PID of cat /dev/urandom > /dev/dsp.

Opened Options applied a change and this time it saves the change and continues to run. Closed Lingot and reopened, back to options/change a value/apply and it crashes again.

Lingot runs on Fiesty with this hardware.

Ubuntu 8.04, 2.6.24-19-generic #1 SMP Wed Jun 4 15:10:52 UTC 2008 x86_64 GNU/Linux, Lingot 0.7.4

[Jón Fairbairn (jon-fairbairn)]

I have a similar problem; it seems to be some sort of incompatibility with pulseaudio
If I fire up lingot from the command line, (using a config file that says
AUDIO_DEV = /dev/dsp
which is the default), it runs and responds to signals, but Tuner=>Options [change something]=>Apply
causes it to die with "Unable to open audio device /dev/dsp: Device or resource busy"
On the other hand, "padsp lingot" behaves very oddly as far as sound input is concerned, but this time
Tuner=>Options [change something]=>Apply works (and changes the config file).

[Visko (visko)]

Actually there is a 0.7.6 from lingot (current one is 0.7.4) for almost more than a year, and its news says that some segmentation faults have been corrected. I think this one should be in the repository.

[Tomas Cassidy (tomas-cassidy)]

This is still occuring with lingot in Intrepid. I am getting it to crash with a segfault after viewing the options screen.

[kede (kede)]

Happens in Ubuntu 10.10.

[Ibán Cereijo (ibancg)]

Hi all,

Thank you for your reports and comments.
If any of you could try the new version 0.9.0 and give me a feedback about the bugs it would be really helpful.

http://download.savannah.gnu.org/releases/lingot/

TIA,
Ibán.

[Tomas Cassidy (tomas-cassidy)]

I just compiled lingot 0.9.0 on Ubuntu 10.10 with --enable-jack=no.

When I started for the first time, I received the following warnings in alert/messageboxes:
"The requested sample rate is not available, the real sample rate has been set to 1520 Hz".
"The temporal buffer is smaller than FFT size. It has been increased to 8.421 seconds".

When I opened the preferences dialog and clicked "Cancel", I got a segfault in the terminal output.

After restarting lingot, I got the warning "The requested sample rate is not available, the real sample rate has been set to 11347264 Hz".

I opened the preferences dialog and clicked "Ok" and got the following terminal output:

Exiting core thread
duplicated message: The temporal buffer is smaller than FFT size. It has been increased to inf seconds
Segmentation fault

Each time I start lingot, I get the same warnings appearing in alert/messageboxes but with different values for the "Hz" and "seconds" numbers.

[Ibán Cereijo (ibancg)]

Hi Tomas,

Wow!, thank you for your time!.

Could you please tell me:

About the first segfault:

  - Is it reproducible using OSS, ALSA, or both?
  - Any other information you have about it will be really helpful. If you have a GDB backtrace it would be perfect.

About the messages telling you that the real sample rate has been set to ridiculous values:

  - Is it reproducible using OSS, ALSA, or both?
  - As you are obtaining a warning on the start-up, can you tell me the SAMPLE_RATE value on your ~/.lingot/lingot.conf file?.

About the second segfault (it may come from the attemp to allocate a huge buffer)

  - Is it reproducible using OSS, ALSA, or both?

Thank you again for your help in improving Lingot,
Ibán.

[Tomas Cassidy (tomas-cassidy)]

I recompiled lingot 0.9.0 on Ubuntu Natty and I couldn't get those segfaults to appear.
I did manage to get a buffer overflow when setting the sample rate to 1150438151 in the preferences screen. The generated coredump of this was 1.9GB, so I won't be uploading that here. gdb log is attached, using the steps from https://wiki.ubuntu.com/Backtrace.

Changing the value of SAMPLE_RATE in lingot.conf back to 44100 allowed lingot to start successfully. Maybe there should be some input validation on the sample rate field in the preferences screen?

I couldn't test OSS because lingot said it couldn't find /dev/dsp. I'm guessing that OSS is not installed.

[Ibán Cereijo (ibancg)]

Hi Tomas,

Thank you again for your time.

You are right!, Lingot needs a validation of the requested configuration to avoid ridiculous or impossible values in any of its parameters. I'll do it in order to get rid of the second segfault/buffer overflow and other potential bugs.

I'm still worried about the first segfault, the one appeared after pressing the Cancel button, and also about the unability of putting the requested sample rate, but I'll work on it (now I know that it only happens with ALSA).

Best,
Ibán.

[Thomas Hotz (thotz-deactivatedaccount)]

Any updates on this bug? Thank you for the information?

[Launchpad Janitor (janitor)]

[Expired for lingot (Ubuntu) because there has been no activity for 60 days.]