Package: audacity
Version: 1.3.12-3

Hmm, works fine over here.

No doubt.  :)

     $ audacity
     Cannot connect to server socket err = No such file or directory
     Cannot connect to server socket
     jack server is not running or cannot be started
     Segmentation fault

Do you have a ~/.jackdmp? If so, try to move it away (delete or rename


If it still asks for a jackd for you (don't know why, perhaps via some
kind of .asoundrc, /etc/asound.conf or whatever magic), you could start

    jackd -d dummy

Though this won't give you any output, it should at least enable you to
start audacity. You could then still use the plain ALSA backend.

Well, I have never had JACK installed, and never had 'audacity' insist on its presence before.

I failed to mention before that I do use a heavily customized /etc/asound.conf file: I have a 5.1 surround speaker system, and output to it without any sound server (pulse, esound, etc.). However, this has been in place (with no changes) for several years, and 'audacity' worked fine with it. I can provide the contents of that config file upon request, but I assure you that there is nothing in it that has anything to do with JACK.

For a real analysis, we'd need a backtrace:

I agree. I've been a bit on the busy side, so I decided to report the bug first without running 'gdb'. I may find some time this weekend. (I also have had a problem -- for over a year -- with 'gmplayer' where it crashes when running its configuration dialog, and need to nose around with 'gdb' to troubleshoot that. I just don't use 'mplayer', and have had no motivation, and no one else seems to be having the same problem, just like this 'audacity' glitch.)

As an added data point, take a quick look at this 'totem' error reported on debian-user:

This user is being hit with the same complaint about JACK that I am being hit with. This makes it look like 'audacity' is not the problem at all, but some library or other dependency.

Dave W.

pkg-multimedia-maintainers mailing list

Reply via email to