Version-Release number of selected component: jack-audio-connection-kit-1.9.10-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/jackd -T -ndefault -dalsa -dhw:SB,0 -r48000 -p1024 -n2 -Xseq -P -o2 crash_function: Jack::JackLockedEngine::ClientKill executable: /usr/bin/jackd kernel: 3.17.6-300.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #6 Jack::JackLockedEngine::ClientKill at /usr/src/debug/jack-1.9.10/common/JackLockedEngine.h:168 #7 Jack::JackSocketServerChannel::ClientKill at ../posix/JackSocketServerChannel.cpp:177 #8 Jack::JackSocketServerChannel::Execute at ../posix/JackSocketServerChannel.cpp:236 #9 Jack::JackPosixThread::ThreadHandler at ../posix/JackPosixThread.cpp:59
Created attachment 968325 [details] File: backtrace
Created attachment 968326 [details] File: cgroup
Created attachment 968327 [details] File: core_backtrace
Created attachment 968328 [details] File: dso_list
Created attachment 968329 [details] File: environ
Created attachment 968330 [details] File: limits
Created attachment 968331 [details] File: maps
Created attachment 968332 [details] File: open_fds
Created attachment 968333 [details] File: proc_pid_status
Created attachment 968334 [details] File: var_log_messages
I just submitted this from testing to stable. I wonder if I should pull my request. Is this a one-off crash? How reproducible is it? Does it happen with the old version?
I'd upgraded this due to a libreport bug. I was using QJackctl, Alsa Modular Synth and the Jack keyboard and the error occured once. I've not seen it again.
I see. Thanks. Looks like some low-level deadlock or race condition issue. I don't know the jack implementation internals to tell the cause of this. Please let us know if you find a way to reproduce the crash. We can then forward this to the jack developers.
When using latest ardour3 nightly build and calf git from today, it crashes everytime I want to load sidechain gate. While crashing there's a lot of that: JackEngine::XRun: client = ardour was not finished, state = Running JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = ardour was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = ardour was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = ardour was not finished, state = Triggered JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackAudioDriver::ProcessGraphAsyncMaster: Process error JackEngine::XRun: client = ardour was not finished, state = Triggered [...] Cannot write socket fd = 24 err = Connection reset by peer CheckRes error Could not write notification ClientNotify fails name = ardour notification = 3 val1 = 0 val2 = 0 Cannot write socket fd = 24 err = Broken pipe CheckRes error Could not write notification ClientNotify fails name = ardour notification = 3 val1 = 0 val2 = 0 Speicherzugriffsfehler (Speicherabzug geschrieben) Cannot write socket fd = 24 err = Broken pipe CheckRes error Could not write notification ClientNotify fails name = ardour notification = 12 val1 = 1 val2 = 9 Cannot write socket fd = 24 err = Broken pipe CheckRes error Could not write notification ClientNotify fails name = ardour notification = 12 val1 = 48 val2 = 23 Cannot write socket fd = 24 err = Broken pipe [...] Unknown error... terminate called after throwing an instance of 'Jack::JackTemporaryException' what():
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.