View previous topic :: View next topic |
Author |
Message |
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
Posted: Fri Mar 15, 2013 9:38 am Post subject: [SOLVED] Audacity don't start if jackd is running |
|
|
Hi,
few month ago i've used them without problems, but now audacity don't start at all if jackd is running and i get this error:
Code: | libgcc_s.so.1 must be installed for pthread_cancel to work |
I found this error in others threads, but it seems that nobody has a clear idea of where it come from.
Others applications like mplayer still works normally with jack.
Suggestions are welcome!
Last edited by clostry on Wed Apr 17, 2013 2:55 pm; edited 1 time in total |
|
Back to top |
|
|
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
Posted: Fri Mar 15, 2013 11:31 am Post subject: |
|
|
I tried compiling audacity by hand, and i discovered there was something wrong with wxwidgets profile.
The weird thing is that the configure script stopped there, but the ebuild went on and compiled...mmm...
I did "eselect wxwidgets set 1" and "emerge audacity" again.
The problem isn't solved, now i get random errors like segmentation error and this one
Code: | (process:6032): GLib-ERROR (recursed) **: gmem.c:230: failed to allocate 64 bytes |
Or even different Glib errors.... |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Fri Mar 15, 2013 11:39 am Post subject: |
|
|
Which versions of each are you dealing with ?
I get absolutely no trouble building & using audacity-2.0.0 + jack-audio-connection-kit-0.121.3 _________________
|
|
Back to top |
|
|
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
Posted: Fri Mar 15, 2013 12:02 pm Post subject: |
|
|
Same of yours. |
|
Back to top |
|
|
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Fri Mar 15, 2013 5:42 pm Post subject: |
|
|
Please post the output of
EDIT : If you do not achieve this on a regular basis, you might need tofirst. _________________
|
|
Back to top |
|
|
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
Posted: Fri Mar 15, 2013 5:57 pm Post subject: |
|
|
Code: | /usr/lib64/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.6.3/libgcc_s.so.1
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so
/usr/lib64/gcc/x86_64-pc-linux-gnu/4.6.3/32/libgcc_s.so.1
/usr/lib64/openoffice/ure/lib/libgcc_s.so.1 |
|
|
Back to top |
|
|
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
Posted: Fri Mar 15, 2013 6:10 pm Post subject: |
|
|
I forgot to post the full output of audacity...
This is what i get with jackd running
Code: | ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc |
Or others random errors like
Code: | ***MEMORY-ERROR***: audacity[10779]: GSlice: failed to allocate 496 bytes (alignment: 512): Impossibile allocare memoria |
And this is what i get without jackd running
Code: | ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3875
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3875
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3875
|
By the way audacity runs normally in the latter case. |
|
Back to top |
|
|
clostry n00b
Joined: 26 Nov 2008 Posts: 26
|
Posted: Wed Apr 17, 2013 2:59 pm Post subject: |
|
|
Editing the file /etc/security/limits.d/audio.conf and changing the line
Code: | @audio - memlock 500000 |
to
Code: | @audio - memlock unlimited |
and commenting out all @audio entries i had in /etc/security/limits.conf did the trick. |
|
Back to top |
|
|
|