Bug 652524
| Summary: | [abrt] rakarrack-0.5.8-2.fc14: Process /usr/bin/rakarrack was killed by signal 6 (SIGABRT) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | savailonei | ||||||
| Component: | rakarrack | Assignee: | David Timms <dtimms> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 14 | CC: | dtimms | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:3b8d0aef2d633fe05f7373b56bdc50cd84b14d34 | ||||||||
| Fixed In Version: | rakarrack-0.6.1-2.fc13 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2010-12-13 11:57:16 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
savailonei
2010-11-12 06:05:49 UTC
Created attachment 459924 [details]
File: backtrace
Created attachment 460241 [details] rakarrack death when jack server "stop"ed (In reply to comment #0) > How to reproduce > ----- > 1. start jack server > 2. start rakarrack > 3. stop jack server When you did this, did you see the dialog, "Warning - Jack Audio Connection Kit: Some client audio applications are still active and connected. Do you want to stop the JACK audio server ?" Did you hit Yes to this dialog ? When I did I got a different backtrace. I did see the dialog. And yes I hit 'Yes'. I checked it again just now, to be sure, but the backtrace remains the same as the one I've already posted. I think the differences in backtraces may be caused by different timing - rakarrack was interrupted in different moments. By the way, the version of my rakarrack is 0.5.8-2 and it runs on latest Fedora 14, maybe your setup differs a little bit? I've updated rakarrack locally to 0.6.1, which continues to close in the above way when the jack server is stopped. I have made a feature request of the upstream developers, in the hope that there is a nicer way to exit rakarrack should the jack server exit. If you know of other jack clients that do this nicely, we mght be able to hunt down some existing shutdown/exception handling code. Ref: https://sourceforge.net/tracker/?group_id=215888&atid=1035485 Closing this as upstream, and hoping for a future upstream resolution. rakarrack-0.6.1-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/rakarrack-0.6.1-2.fc13 rakarrack-0.6.1-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/rakarrack-0.6.1-2.fc14 rakarrack-0.6.1-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. rakarrack-0.6.1-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report. |