Crashes when trying to record (Segmentation Fault)

[robotangel]

I just installed rezound to digitalize some tapes. When I try to record it crashes every time.

Console Output:
$ rezound
using path '/usr/share/rezound' for share data directory
If rezound dies unexpectedly while seeking with the keyboard, auto-repeat may be disabled.. if this happens run 'rezound --fix-auto-repeat'
cannot write to working directory candidate: / -- Permission denied
Segmentation fault (core dumped)

I've got a Creative Audigy LS (recording supported, Skype and TS work). Doesn't work with --fix-auto-repeat either.

[robotangel (robotangel)]

... didn't know where to include it when I reported the bug ...

[Sebastian (mdkuser)]

I can confirm this bug as filed here:

https://launchpad.net/distros/ubuntu/+source/rezound/+bug/70577

It crashes everytime I tried to use the record function. I tested it under an Machine with Intel onboard soundcard as well as on a machine with creative sound blaster live. It always crashes rezound. This problem does not occour in Breezy nor in Dapper.

[Sebastien Bacher (seb128)]

Thank you for your bug

[Sebastian (mdkuser)]

So what? Is someone going to fix it?
I filed this bug ages ago and no one respond!
If this is what the Ubuntu developer calls support then I will no longer take my time to file bug reports because it will be ignored at the end anyway!
Some bugs in Ubuntu are still present since DAPPER and still not fixed yet!

[Sebastian (mdkuser)]

Just one comment rezound does not comile on edgy? Configure runs smooth but make stops after a while with an unexpected error.
I had no problems compiling rezound under Zenwalk current and I runs ok.
On Ubuntu the rezound package and the rezound source package are simply crap!

[Michael (michael-oshinsky)]

ReZound also crashes when you try to record in ZuBuntu Feisty. I compiled from the source and reinstalled and it still crashes on record.

During the ./configure process, I noticed the following note:
configure: Tests for methods to use for audio I/O will follow below. The method actually used will be determined at run-time depending on the order of the values in the ~/.rezound/registry.dat file in AudioOutput(or Input)Methods and will depend on which method first initializes successfully. Alternatively, there is an --audio-method=... flag to the rezound binary to choose which method to try first. See 'rezound --help' for more information.

There are three choices for the --audio-method argument (oss, alsa or NULL)
rezound --audio-method=oss : doesn't work
rezound --audio-method=alsa : works like a charm!!!!

[Apreche (apreche)]

We are also having this problem in rezound on Feisty on every machine we have tried. It crashes as soon as you try to record with a segfault. Trying to compile rezound from source results in the same exact issue. My guess is that one of the dependencies of rezound is a newer version in Feisty and that dependency, whatever it is, has changed in a way that breaks rezound. Heck, it might even be a kernel change. The reason the segfault happens appears to be because rezound screws up while reading from /dev/dsp. Perhaps the buffer it is reading into gets broken, or perhaps it is reading improperly. I can't tell.

Also, I can say that rezound --audio-method=alsa has not worked to solve this problem. I have tried it on many different Feisty machines, and it crashes just the same as when using the default of OSS. However, there is a way to get rezound to work. The way is to use jack. Do the following if you don't have jack working already.

sudo apt-get install qjackctl
qjackctl
# push the start button
rezound --audio-method=jack

Now rezound will be able to work properly without crashing. Using jack should also give you some measure of enhanced performance. This will be especially true if you have the low-latency audio stuff in the kernel, or if you use UbuntuStudio, which has the low-latency stuff by default.

Regardless, I think this bug needs increased priority. Rezound is the only halfway decent single-track audio editor for Linux, and it's the only free open source one in existence. Multi-track editors like Jokosher or Audacity just do not cut it compared to Rezound, especially when it comes to thinks like podcasting. Not having this application work in Ubuntu Feisty is a pretty big deal.

[Sebastian (mdkuser)]

I think you guys better change the distribution!
It seems that Ubuntu doesn't really care about fixing bugs, so why should we report those bugs?
I got rezound working on every other distrie out there and it also compiles without problems (well you have to patch it if you want to compile it agains the newest flac-version) but not under Ubuntu.
If Ubuntu doesn't care about quality why support this distrie?!

[Apreche (apreche)]

This bug is still the same in the gutsy beta. If the bug isn't going to be fixed, just remove rezound from the repositories. Do we want *buntu users to have easy access to the best open source single-track audio recorder/editor or not?

[Andrew Somerville (andy16666)]

I can confirm this bug. Among many other issues, this bug will probably force me to install gentoo again. I agree 100% with the other poster. As a musician, rezound is essential equipment, and not only for single track. It's also one of only a couple free multitrack programs out there for linux and the only really superb one.

Hopefully you guys will get your acts together and fix some of these small show stoppers like this one. I can't stress enough that this bug is likely to force me to stop using ubuntu if it isn't addressed.

Here's my output:

$ rezound
Fontconfig warning: "~/.fonts.conf", line 10: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 18: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 26: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 34: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 42: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 50: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 58: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 66: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 74: invalid constant used : full
Fontconfig warning: "~/.fonts.conf", line 82: invalid constant used : full
using path '/usr/share/rezound' for share data directory
Error occurred while initializing audio output method 'oss' -- virtual void COSSSoundPlayer::initialize() -- error opening OSS device '/dev/dsp -- Device or resource busy
JACK tmpdir identified as [/dev/shm]
'lame' executable not found in $PATH -- mp3 support will be disabled
error - bool ASoundFileManager::prvOpen(std::string, bool, bool, bool, const ASoundTranslator*) -- file does not exist: /untitled0.rez
If rezound dies unexpectedly while seeking with the keyboard, auto-repeat may be disabled.. if this happens run 'rezound --fix-auto-repeat'
cannot write to working directory candidate: / -- Permission denied
Segmentation fault (core dumped)

[Andrew Somerville (andy16666)]

Other confirmations of this bug from a quick search:
http://www.linuxquestions.org/questions/linux-software-2/is-anyone-familiar-with-rezound-71622/
http://lists.linuxaudio.org/pipermail/linux-audio-user/2006-March/032890.html

I suspect that this bug is for some reason due to the fact that rezound is trying to use / as its temporary storage. I have no idea why it would be doing this, but Ubuntu is the only distro upon which I have seen this bug, so it must be something that you guys are doing when you compile/package it.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 alpha?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[maccus (maccus)]

Why close this report if the bug is still there in Hardy?

ubuntu@cumbus:~$ rezound
using path '/usr/share/rezound' for share data directory
no more csLADSPA plugins
If rezound dies unexpectedly while seeking with the keyboard, auto-repeat may be disabled.. if this happens run 'rezound --fix-auto-repeat'
Segmentatiefout

Please fix this. I agree with the above posters that Rezound is an important application. Even more so if you run ubuntu-studio. And Audacity doesn't work with jack on Hardy, so the options for sound recording get pretty limited. For a distro like Studio you should be able to record sound.

[maccus (maccus)]

I just noticed that the XDG menu has an Exec line rezound --audio-method=jack. However, if jack is not started, you get the same behaviour, rezound crashes on trying to record. How on earth are users supposed to know that jackd is needed for Rezound? Better really fix this issue.

As for me, i'm using a script /usr/local/bin/fix-rezound, may be of interest to others, as long as this bug is not fixed by Ubuntu:

Open a terminal:

ALT+F2 gnome-terminal

Start a text editor:

sudo gedit /usr/local/bin/fix-rezound

Write the script:

#!/bin/bash
jackd -d alsa &
sleep 1
rezound --audio-method=jack
killall jackd
exit 0

Make it executable:

sudo chmod 755 /usr/local/bin/fix-rezound

Then copy /usr/share/applications/audacity.desktop to ~/.local/applications/audacity.desktop, open it with a text editor and change "Exec=rezound --audio-method=jack" to "Exec=fix-rezound"