Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 13971 bytes cmdline: /usr/bin/jackd -T -ndefault -dalsa -dhw:M1010LT -r44100 -p256 -n3 -Xseq -zt component: jack-audio-connection-kit Attached file: coredump, 36540416 bytes crash_function: Jack::JackGraphManager::AssertPort executable: /usr/bin/jackd kernel: 2.6.35.13-92.fc14.x86_64 package: jack-audio-connection-kit-1.9.7-2.fc14 rating: 4 reason: Process /usr/bin/jackd was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1311563734 uid: 500 How to reproduce ----- 1. After logging in to my system 2. 3.
Created attachment 514962 [details] File: backtrace
Package: jack-audio-connection-kit-1.9.7-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crashed right after login. 2. 3.
Package: jack-audio-connection-kit-1.9.7-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Happened while booting up my computer 2. 3.
From the backtrace you attached, I suspect that jack is not configured properly. Did you follow /usr/share/doc/jack-audio-connection-kit-1.9.7/README.Fedora ?
(In reply to comment #4) > From the backtrace you attached, I suspect that jack is not configured > properly. Did you follow > /usr/share/doc/jack-audio-connection-kit-1.9.7/README.Fedora > ? I am starting to now. Since my son set up pulseaudio for me to start with jackd on start up, I am using that as well. I did the first step of adding username to the jackuser group and I will see if that helps. I'll let you know if I still get crashes in the future. Thanks, David
Package: jack-audio-connection-kit-1.9.7-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Was playing a song in Ardour 2. 3.
Package: jack-audio-connection-kit-1.9.7-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. change latency 2. restart jack 3.
Backtrace analysis found this bug to be similar to bug #662763, closing as duplicate. Bugs which were found to be similar to this bug: bug #662763, bug #672140 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 662763 ***