Bug 592729 - [abrt] crash in calf-0.0.18.5-3.fc12: pa_atomic_store: Process /usr/bin/calfjackhost was killed by signal 7 (SIGBUS)
Summary: [abrt] crash in calf-0.0.18.5-3.fc12: pa_atomic_store: Process /usr/bin/calfj...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: calf
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Orcan Ogetbil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1d26ed11037b96ca6590dd540ea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-16 15:03 UTC by Retlaw Dlawso
Modified: 2010-12-03 14:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 14:39:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (34.96 KB, text/plain)
2010-05-16 15:03 UTC, Retlaw Dlawso
no flags Details

Description Retlaw Dlawso 2010-05-16 15:03:01 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: calfjackhost
component: calf
crash_function: pa_atomic_store
executable: /usr/bin/calfjackhost
global_uuid: 1d26ed11037b96ca6590dd540ea4546e7da0ee09
kernel: 2.6.32.11-99.fc12.x86_64
package: calf-0.0.18.5-3.fc12
rating: 4
reason: Process /usr/bin/calfjackhost was killed by signal 7 (SIGBUS)
release: Fedora release 12 (Constantine)

Comment 1 Retlaw Dlawso 2010-05-16 15:03:04 UTC
Created attachment 414368 [details]
File: backtrace

Comment 2 Orcan Ogetbil 2010-05-16 15:19:23 UTC
Hi,

abrt should have a field where you can put how to reproduce the bug. If it did not, please let us know.

Meanwhile, can you tell us

* How to reproduce the crash?
* Does the crash occur when you remove pulseaudio?

Thanks.

Comment 3 Retlaw Dlawso 2010-05-16 18:23:04 UTC
Hi
no pulseaudio installed, but alsa
just installed QjackCtl, which appeared to work well
tried to launch "Calf Plugin Pack for Jack", which produced the crash directly
this arrived with other applications, too
however, Jack reports:
- cannot use real-time scheduling (FIFO at priority 35) [for thread 1979016976, from thread 1979016976] (1: Operation not permitted)
- cannot use real-time scheduling (FIFO at priority 25) [for thread 1978488592, from thread 1978488592] (1: Operation not permitted)
I do not know if this affects.
cheers

Comment 4 Bug Zapper 2010-11-03 14:47:51 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 5 Retlaw Dlawso 2010-11-06 15:46:49 UTC
Yes, close this bug; the newest Fedora versions are ever in use, anyway. Thanks.

Comment 6 Bug Zapper 2010-12-03 14:39:56 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


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