Bug 3619

Summary: Jack server is not running
Product: Mageia Reporter: Jacques Pronchery <jacques.pronchery>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal CC: mageia, marja11
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: Record
Playback

Description Jacques Pronchery 2011-12-05 14:04:49 CET
When lauching audacity it say :

[jacques@localhost ~]$ audacity
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2212:(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
Cannot connect to server socket err = Aucun fichier ou dossier de ce type
Cannot connect to server socket
jack server is not running or cannot be started
Expression 'stream->capture.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3857
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1035
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir, &self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1192
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi, inParams, StreamDirection_In, NULL != callback )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1433
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi, inputParameters, outputParameters, sampleRate, framesPerBuffer, callback, streamFlags, userData )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2105
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
[jacques@localhost ~]$ 

If I launch lmms I have :

[jacques@localhost ~]$ lmms
Notice: could not set realtime priority.
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: Permission non accordée
cannot open sequencer: Permission non accordée
ALSA lib rawmidi_hw.c:233:(snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed: Aucun fichier ou dossier de ce type
cannot open MIDI-device: Aucun fichier ou dossier de ce type
Couldn't create MIDI-client, neither with ALSA nor with OSS. Will use dummy-MIDI-client.
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
Cannot connect to server socket err = Aucun fichier ou dossier de ce type
Cannot connect to server socket
jack server is not running or cannot be started
Cannot connect to server socket err = Aucun fichier ou dossier de ce type
Cannot connect to server socket
jack server is not running or cannot be started
Erreur de segmentation
[jacques@localhost ~]$ 

My config :

[jacques@localhost ~]$ cat /proc/asound/cards
 0 [NVidia         ]: HDA-Intel - HDA NVidia
                      HDA NVidia at 0xfe024000 irq 20
 1 [U0x46d0x802    ]: USB-Audio - USB Device 0x46d:0x802
                      USB Device 0x46d:0x802 at usb-0000:00:02.1-3, high speed
[jacques@localhost ~]$ ls -l /dev/snd/*
crw-rw----+ 1 root audio 116,  9 déc.   5 15:16 /dev/snd/controlC0
crw-rw----+ 1 root audio 116,  3 déc.   5 15:16 /dev/snd/controlC1
crw-rw----+ 1 root audio 116,  8 déc.   5 15:16 /dev/snd/hwC0D0
crw-rw----+ 1 root audio 116,  7 déc.   5 15:53 /dev/snd/pcmC0D0c
crw-rw----+ 1 root audio 116,  6 déc.   5 16:01 /dev/snd/pcmC0D0p
crw-rw----+ 1 root audio 116,  5 déc.   5 15:19 /dev/snd/pcmC0D1p
crw-rw----+ 1 root audio 116,  4 déc.   5 15:53 /dev/snd/pcmC0D2c
crw-rw----+ 1 root audio 116,  2 déc.   5 15:53 /dev/snd/pcmC1D0c
crw-rw----  1 root audio 116,  1 déc.   5 15:16 /dev/snd/seq
crw-rw----+ 1 root audio 116, 33 déc.   5 15:16 /dev/snd/timer

/dev/snd/by-id:
total 0
lrwxrwxrwx 1 root root 12 déc.   5 15:16 usb-046d_0802_8AA7BE50-02 -> ../controlC1

/dev/snd/by-path:
total 0
lrwxrwxrwx 1 root root 12 déc.   5 15:16 pci-0000:00:02.1-usb-0:3:1.2 -> ../controlC1
lrwxrwxrwx 1 root root 12 déc.   5 15:16 pci-0000:00:05.0 -> ../controlC0
[jacques@localhost ~]$
Comment 1 Marja Van Waes 2012-01-26 19:03:59 CET
@ Jacques

Do you still have this problem in updated cauldron / Mga 2 alpha ?

cc'ing our sound magician

Keywords: (none) => NEEDINFO
CC: (none) => mageia, marja11

Comment 2 Jacques Pronchery 2012-01-26 22:34:10 CET
Yes there is still the same problem.
Comment 3 Manuel Hiebel 2012-01-27 00:52:06 CET
And if you start jackd with qjackctl or change the prefs in the software ?
Comment 4 Colin Guthrie 2012-01-27 10:02:16 CET
Hmm, it seesm that /dev/snd/seq is not getting the ACLs which could be a problem (tho' not likely the reason jackd isn't running).

How do you start jackd? You do realise that you have to start jackd manually if you want to use such a setup? Is this intentional (i.e. do you really want to use jack) or is it just the subject of this bug because of the output from the two programs?

I'll ask upstream about that.


Otherwise I suggest you start jack first. But please do just let us know if this is not the configuration you want to use and you've just accidentally enabled it.
Comment 5 Jacques Pronchery 2012-01-27 11:43:26 CET
I do not really want to use it, I only use audacity for normelize level, erase same noises and make transition between audio files.
But as I have some problems with mixers, I have searched what happen with somes audio apps, And I found this report.
If I try to start jackd, it do not start, but it seems that I have a poor sound card and a powerless driver.
I have report this bug only to inform you of a possible problem.
Comment 6 Colin Guthrie 2012-01-27 11:57:31 CET
If you do not want to use jack, then you should probably be using the default setup which uses PulseAudio.

Please report output from: update-alternatives --display soundprofile
Comment 7 Jacques Pronchery 2012-01-27 13:29:34 CET
(In reply to comment #6)
> If you do not want to use jack, then you should probably be using the default
> setup which uses PulseAudio.
> 
> Please report output from: update-alternatives --display soundprofile

Here is the report :

[root@localhost jacques]# update-alternatives --display soundprofile
soundprofile - status is auto.
 link currently points to /etc/sound/profiles/pulse
/etc/sound/profiles/alsa - priority 10
/etc/sound/profiles/pulse - priority 20
Current `best' version is /etc/sound/profiles/pulse.
[root@localhost jacques]#
Comment 8 Marja Van Waes 2012-02-11 15:40:06 CET
removing NEEDINFO keyword, because the requested information was given

@ Colin

Can you look at Jacques feedback, please?
Can this issue be assigned to you? 

(I understand the problem isn't in audacity or lmms, therefore removing those package names)

Keywords: NEEDINFO => (none)
Source RPM: audacity - lmms => (none)

Comment 9 Colin Guthrie 2012-02-13 10:09:59 CET
It just looks like audacity is misconfigured.

On my system I get similar output from running audacity on the command line, but this is all expected - it's just audacity probing to see what does and does not work.

Using the default configuration of audacity (alsa using "default" devices), everything works fine.

I tried running lmms and it didn't segv on me.

I really cannot see any actual bug here...

@Jacques, can you provide any more details on your audacity setup? You should just have a basic alsa output configured (with PortAudio v19) and have "default" selected for both playback and capture.

Keywords: (none) => NEEDINFO

Comment 10 Jacques Pronchery 2012-02-13 11:25:12 CET
Here is my config :
Interface
   host   : ALSA
   using  : PortAudio V19-devel
Playback
   Device : HDA NVidia: ALC888 Analog(hw:0,0)
Recording
   Device : default
   Channels : 2 (Stereo)

With recording device : USB Device (mike)
With Playback Device : pulse 
It is the same.
Comment 11 Colin Guthrie 2012-02-13 11:58:44 CET
Both playback and capture should both be "default".

If you want to actually change the devices, do so using e.g. pavucontrol, not the internal audacity config.

By accessing the hw:0,0 device directly in audacity it will prevent any other application using it at the same time, and may prevent playback.

So leave audacity config as "default" for both playback and capture.

If you still do not get sound recording or playing back, then please record something and while it's recording, execute "pacmd ls >pacmd.record.txt 2>&1" and likewise, open up a known-good wav file (or similar) and play it back and execture "pacmd ls >pacmd.playback.txt 2>&1" while it's playing.

Then attach both files here.

I've tested here and the setup works fine with both recording and playback so I suspect something trivial (like the device or stream being muted on either recording or playback in PA) is to blame.
Comment 12 Jacques Pronchery 2012-02-13 14:02:16 CET
Created attachment 1541 [details]
Record
Comment 13 Jacques Pronchery 2012-02-13 14:03:16 CET
Created attachment 1542 [details]
Playback
Comment 14 Colin Guthrie 2012-02-13 15:04:38 CET
Hmm, I've only just noticed a bug in the output of the pacmd ls for source outputs... it doesn't show the volume or mute status... I must have missed it when I added that feature :s

Anyway, all looks well there.

Things look to be both playing and recording fine (the recording is happening on your front microphone - not your USB, but I presume that's what you want? If not, just use the Recording tab in pavucontrol to move the Audacity stream to the appropriate device there).

I wonder if your front mic works generally? Have you tried using other apps to record the mic - e.g. gnome-sound-recorder? Does playback work generally (i.e. in VLC)?
Comment 15 Jacques Pronchery 2012-02-13 15:47:28 CET
Recording and playback work fine.
I can commute the analogic mike and the USB mike with pavucontrol
or with audacity.
It seems that all work for my job.
Comment 16 Colin Guthrie 2012-02-13 15:52:29 CET
Ahh OK, so then it all works as expected and this bug can be closed. If you disagree, please do feel free to reopen :)

You may want to try investigating the lmms segv issue further and open a bug against it. Like I say, I could not reproduce the issue here.

FWIW, the /dev/snd/seq issue is because this node was not handled by any module. Simply loading the snd_seq_dummy module allowed udev to know about the device and add the appropriate tags for ACL application, so no real problem there either.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME