Bug 662763
| Summary: | [abrt] jack-audio-connection-kit-1.9.6-2.fc14: Process /usr/bin/jackd was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | cosmoman | ||||||
| Component: | jack-audio-connection-kit | Assignee: | Orcan Ogetbil <oget.fedora> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 17 | CC: | CronoCloud, fche, fukidid, green, igor.katalnikov, kanelxake, krysolov230, marco, oget.fedora, unclemarcus91, veedgo, web582 | ||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:39f51c0a37e826f6ab5b1a1d3a2af51eb88b2b2c | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-08-01 18:31:34 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
cosmoman
2010-12-13 19:55:52 UTC
Created attachment 468464 [details]
File: backtrace
Hello, in this bugzilla, we communicate in English. Could you please rephrase in English? Thanks! Package: jack-audio-connection-kit-1.9.6-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. switch system inputs from jack-rack in to vocoder_in in jack rack, using qjackctrl 2. 3. Comment ----- I'm was just playing around with vocoder in jack rack and switching system inputs in qjackctrl and then poof. Probably not reproducable. Package: jack-audio-connection-kit-1.9.6-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Unexplained 2. 3. Package: jack-audio-connection-kit-1.9.6-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Run jack_test in terminal 2. Hit ctrl+z, watch error messages scroll 3. Close terminal window Package: jack-audio-connection-kit-1.9.6-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. started JACK keyboard, no problem 2. Connected keyboard to QSynth, no problem but sound was not smooth 3. Stopped QSynth 4. Started and stopped some other programs, probably to fast 5. Crash did not appear immediately, but after roughly 10..20 seconds. *** Bug 672140 has been marked as a duplicate of this bug. *** *** Bug 725303 has been marked as a duplicate of this bug. *** *** Bug 801069 has been marked as a duplicate of this bug. *** Click START in qjackctl graphical interface backtrace_rating: 4 Package: jack-audio-connection-kit-1.9.8-3.fc16 OS Release: Fedora release 16 (Verne) Created attachment 584055 [details]
File: backtrace
I opened ardour backtrace_rating: 4 Package: jack-audio-connection-kit-1.9.8-9.fc17 OS Release: Fedora release 17 (Beefy Miracle) This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping *** Bug 672140 has been marked as a duplicate of this bug. *** This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |