Bug 592521 - [abrt] crash in jack-audio-connection-kit-0.118.0-1.fc12: jack_watchdog_thread: Process /usr/bin/jackd was killed by signal 11 (SIGSEGV)
[abrt] crash in jack-audio-connection-kit-0.118.0-1.fc12: jack_watchdog_threa...
Status: CLOSED DUPLICATE of bug 571024
Product: Fedora
Classification: Fedora
Component: jack-audio-connection-kit (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Andy Shevchenko
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-15 00:51 EDT by Matt McCutchen
Modified: 2010-05-15 01:02 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-15 01:02:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (14.17 KB, text/plain)
2010-05-15 00:51 EDT, Matt McCutchen
no flags Details

  None (edit)
Description Matt McCutchen 2010-05-15 00:51:32 EDT
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/jackd -T -ndefault -T -d alsa
component: jack-audio-connection-kit
crash_function: jack_watchdog_thread
executable: /usr/bin/jackd
global_uuid: deb323f5f84ece3ecbadbc91ad8aca5bbc8d4b91
package: jack-audio-connection-kit-0.118.0-1.fc12
rating: 2
reason: Process /usr/bin/jackd was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. From a GNOME session, run "rosegarden" in the terminal.
2. Quit Rosegarden.  The following appears in the terminal:
    jack main caught signal 12
A few seconds later, the following appears in the terminal and abrt is triggered:
    jackd watchdog: timeout - killing jackd
Comment 1 Matt McCutchen 2010-05-15 00:51:34 EDT
Created attachment 414210 [details]
File: backtrace
Comment 2 Matt McCutchen 2010-05-15 01:02:58 EDT
Note that I had to hack abrt in order to report this due to abrt bug 592523.

*** This bug has been marked as a duplicate of bug 571024 ***

Note You need to log in before you can comment on or make changes to this bug.