Re: [Denemo-devel] Denemo fails to start

[Andreas Schneider]

After git pull and recompile, Denemo still crashed:

(null) - WARNING : Couldn't register with accessibility bus: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.
Denemo - MESSAGE : Loading preference file:
/home/andreas/.denemo-1.1.9/denemorc
Denemo - MESSAGE : Audio driver is 'portaudio' 0
Denemo - MESSAGE : Initializing Fluidsynth
Denemo - MESSAGE : The default fluidsynth soundfont has been loaded
Denemo - MESSAGE : Initializing Rubberband
Denemo - MESSAGE : Initializing PortAudio backend
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams,
&alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c',
line: 924
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams,
&alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c',
line: 924
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams,
&alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c',
line: 924
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition
'cards.HDA-Intel.pcm.rear.0:CARD=0'
ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer
returned error: Datei oder Verzeichnis nicht gefunden
ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder
Verzeichnis nicht gefunden
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM rear
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition
'cards.HDA-Intel.pcm.center_lfe.0:CARD=0'
ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer
returned error: Datei oder Verzeichnis nicht gefunden
ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder
Verzeichnis nicht gefunden
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
Denemo - WARNING : Invalid device 'ALSA: USB Audio DAC: - (hw:2,0)'
Denemo - WARNING : Initializing audio backend 'portaudio' failed,
falling back to dummy
Denemo - MESSAGE : Initializing dummy audio backend
Denemo - MESSAGE : MIDI driver is 'portmidi'
Denemo - MESSAGE : Initializing PortMidi backend
Attempt to unlock mutex that was not locked
Abgebrochen

As you suggested my sources might be muddled, I removed my whole Denemo
source tree, cloned it again and recompiled. The result is the same.

After removing the line <portaudio_device> in denemorc, the program
started up. I noticed that USB Audio DAC had changed to hw:1,0. I
changed the entry in the preferences dialog and quit. Trying to start
Denemo again, I got some crashes I could not reproduce, i.e. it did not
crash afterwards while I do not know what was different. But in the end,
it is again that Denemo crashes when the audio out device is busy and
starts up when it is not.

(null) - WARNING : Couldn't register with accessibility bus: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the
reply timeout expired, or the network connection was broken.
Denemo - MESSAGE : Loading preference file:
/home/andreas/.denemo-1.1.9/denemorc
Denemo - MESSAGE : Audio driver is 'portaudio' 0
Denemo - MESSAGE : Initializing Fluidsynth
Denemo - MESSAGE : The default fluidsynth soundfont has been loaded
Denemo - MESSAGE : Initializing Rubberband
Denemo - MESSAGE : Initializing PortAudio backend
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams,
&alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c',
line: 924
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams,
&alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c',
line: 924
Expression 'alsa_snd_pcm_hw_params_set_period_size_near( pcm, hwParams,
&alsaPeriodFrames, &dir )' failed in 'src/hostapi/alsa/pa_linux_alsa.c',
line: 924
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition
'cards.HDA-Intel.pcm.rear.0:CARD=0'
ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer
returned error: Datei oder Verzeichnis nicht gefunden
ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder
Verzeichnis nicht gefunden
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM rear
ALSA lib confmisc.c:1286:(snd_func_refer) Unable to find definition
'cards.HDA-Intel.pcm.center_lfe.0:CARD=0'
ALSA lib conf.c:4259:(_snd_config_evaluate) function snd_func_refer
returned error: Datei oder Verzeichnis nicht gefunden
ALSA lib conf.c:4738:(snd_config_expand) Evaluate error: Datei oder
Verzeichnis nicht gefunden
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM center_lfe
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:947:(find_matching_chmap) Found no matching channel map
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server request channel
jack server is not running or cannot be started
Denemo - WARNING : Invalid device 'ALSA: USB Audio DAC: - (hw:1,0)'
Denemo - WARNING : Initializing audio backend 'portaudio' failed,
falling back to dummy
Denemo - MESSAGE : Initializing dummy audio backend
Denemo - MESSAGE : MIDI driver is 'portmidi'
Denemo - MESSAGE : Initializing PortMidi backend
Attempt to unlock mutex that was not locked
Abgebrochen

Andreas


Am 06.10.2014 um 10:56 schrieb Richard Shann:
> Ooops! I thought it was strange that I could have missed the
> g_mutex_unlock() the first time, what happened was that I mistakenly
> deleted the g_mutex_free() and left the unlock, and then when I looked
> again saw the unlock still there and thought I'd missed it.
> But this meant the g_mutex_free() was missing - this didn't crash my
> machine when I tested it, but it could run you out of memory ...
> Your error messages don't seem to match this mistake of mine though - 
> there are now just three g_mutex_unlock()s in the C code all in
> audiointerface.c and all matched with lock/trylock.
> So this
> Attempt to unlock mutex that was not locked
>> Abgebrochen
>>
> is puzzling. On the face of it, it looks like a muddle with versions of
> the program - a failed git pull, corruption of files ... I can't think
> what.
> 
> Well, I have fixed the failure to free the mutex and so it is worth
> testing again. 
> 
> Richard