abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 52994 bytes cmdline: /usr/bin/qjackctl component: qjackctl Attached file: coredump, 19480576 bytes crash_function: ___vsprintf_chk executable: /usr/bin/qjackctl kernel: 2.6.35.14-95.fc14.x86_64 package: qjackctl-0.3.8-1.fc14 rating: 4 reason: Process /usr/bin/qjackctl was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1315176871 uid: 500 How to reproduce ----- 1. When I went to open Hydrogen with all instrument outputs on. 2. I also had Ardour already open connected to several outputs in qjackctl. 3.
Created attachment 521407 [details] File: backtrace
hmm, interesting. do you have a non-standard character in your hostname of your jack server/client?
> hmm, interesting. do you have a non-standard character in your hostname of your > jack server/client? I am not sure what you mean. I am not that good at debugging these kinds of things. Where would I look to find out? I looked in qjackctl and it shows the Server Path as "jackd". Preset name and server name are "(default)".(In reply to comment #2)
Package: qjackctl-0.3.8-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. When I went to open Hydrogen with all instrument outputs on. 2. I also had Ardour already open connected to several outputs in qjackctl. 3. Similar to the last crash.
Package: qjackctl-0.3.8-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. qjackctl crashed while I was opening up Hydrogen. 2. 3.
*** Bug 678437 has been marked as a duplicate of this bug. ***
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