jack don't start after new ubuntu updates

[JAGUT Fr]

jack message =
apparent rate = 44100
creating alsa driver ... hw:2|hw:2|128|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:2
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
cannot load driver module alsa
no message buffer overruns
21:49:03.148 JACK was stopped successfully.
21:49:03.148 Post-shutdown script...
21:49:03.148 killall jackd
21:49:03.253 MIDI active patchbay scan...
21:49:03.304 Audio_00: 20:0 Keystation Pro 88 -> 28:0 M Audio Delta 1010LT connected.
21:49:03.306 ALSA connection change.
21:49:03.307 ALSA connection graph change.
jackd: aucun processus tué
21:49:03.507 MIDI active patchbay scan...
21:49:03.507 Audio_00: 20:0 Keystation Pro 88 -> 28:0 M Audio Delta 1010LT checked.
21:49:03.565 Post-shutdown script terminated with exit status=256.
21:49:05.315 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Trying old kernel updates : jack is ok

[JAGUT Fr (f-jagut)]

apparent rate = 44100
creating alsa driver ... hw:2|hw:2|128|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:2
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
cannot load driver module alsa
no message buffer overruns
21:49:03.148 JACK was stopped successfully.
21:49:03.148 Post-shutdown script...
21:49:03.148 killall jackd
21:49:03.253 MIDI active patchbay scan...
21:49:03.304 Audio_00: 20:0 Keystation Pro 88 -> 28:0 M Audio Delta 1010LT connected.
21:49:03.306 ALSA connection change.
21:49:03.307 ALSA connection graph change.
jackd: aucun processus tué
21:49:03.507 MIDI active patchbay scan...
21:49:03.507 Audio_00: 20:0 Keystation Pro 88 -> 28:0 M Audio Delta 1010LT checked.
21:49:03.565 Post-shutdown script terminated with exit status=256.
21:49:05.315 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

 trying precedent ubuntu updates (kernel) : jack is ok

[JAGUT Fr (f-jagut)]

Excuse me for the stress : jack now works. I just have to push off my external instruments before pushing on the computer and finally jack...

Excuse me for my stupid precipitation !
Thanks for all.

[Ruben Verhack (ruben-verhack)]

This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
the playback device "hw:0" is already in use. Please stop the application using it and run JACK again
cannot load driver module alsa
no message buffer overruns
23:41:37.237 JACK was stopped successfully.
23:41:37.237 Post-shutdown script...
23:41:37.238 killall jackd
jackd: er is geen proces afgebroken
23:41:37.648 Post-shutdown script terminated with exit status=256.
23:41:39.370 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info.

Ubuntu 8.10, jackd from repos. No instruments or special audio gear. Only virtual midi keyboard.

[Ruben Verhack (ruben-verhack)]

Sorry! I was too quick, I should have read the messages better. It was just Ableton that was still open. Sorry for this.

[Przemek K. (azrael)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[JAGUT Fr (f-jagut)]

2010/4/26 Przemysław Kulczycki <email address hidden>

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering if this is still an issue
> for you. Can you try with the latest Ubuntu release? Thanks in advance.
>
> ** Package changed: ubuntu => jack (Ubuntu)
>
> ** Changed in: jack (Ubuntu)
> Status: New => Incomplete
>
> --
> jack don't start after new ubuntu updates
> https://bugs.launchpad.net/bugs/357953
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “jack” package in Ubuntu: Incomplete
>
> Bug description:
> jack message =
> apparent rate = 44100
> creating alsa driver ... hw:2|hw:2|128|2|44100|0|0|nomon|swmeter|-|32bit
> control device hw:2
> ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to
> capture-only mode
> cannot load driver module alsa
> no message buffer overruns
> 21:49:03.148 JACK was stopped successfully.
> 21:49:03.148 Post-shutdown script...
> 21:49:03.148 killall jackd
> 21:49:03.253 MIDI active patchbay scan...
> 21:49:03.304 Audio_00: 20:0 Keystation Pro 88 -> 28:0 M Audio Delta 1010LT
> connected.
> 21:49:03.306 ALSA connection change.
> 21:49:03.307 ALSA connection graph change.
> jackd: aucun processus tué
> 21:49:03.507 MIDI active patchbay scan...
> 21:49:03.507 Audio_00: 20:0 Keystation Pro 88 -> 28:0 M Audio Delta 1010LT
> checked.
> 21:49:03.565 Post-shutdown script terminated with exit status=256.
> 21:49:05.315 Could not connect to JACK server as client. - Overall
> operation failed. - Unable to connect to server. Please check the messages
> window for more info.
>
> Trying old kernel updates : jack is ok
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/jack/+bug/357953/+subscribe
>

__________________________________________________________

Thank you for keeping trace of all problems that users encounter.

The issue of the bug described above is now finished. Jack is working very
well now on my computer. I remember that the bug has not last a long time
and i have forgotten to contact your service as soon... Excuse me for that!

Thank you for all !

Jagut François

[Przemek K. (azrael)]

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.