abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: rakarrack comment: i try use rock amp component: rakarrack executable: /usr/bin/rakarrack global_uuid: 7d756e899460d745b0e1840c7b50fd24583e7647 kernel: 2.6.32.14-127.fc12.x86_64 package: rakarrack-0.5.8-2.fc12 rating: 4 reason: Process /usr/bin/rakarrack was killed by signal 6 (SIGABRT) release: Fedora release 12 (Constantine) How to reproduce ----- 1. try to change preset from bank 2. 3.
Created attachment 434536 [details] File: backtrace
Hi Kajetan, Rakarrack preset 17 Hard rock amp is a preset that uses the Convolotron effect. Even with decent CPU speeds, it is set with values that will cause calculations that don't complete quickly enough to keep the audio real-time, and will lead to the crash you have seen. This is known upstream, and while I would hope that future development would attempt to detect that issue and warn nicely, perhaps turning off effect, or similar. In the meantime, trying the safe mode button, and reducing the oversampling quality in the preferences may allow this effect to work on your machine. The upstream response is: <http://sourceforge.net/tracker/?func=detail&aid=3030872&group_id=215888&atid=1035482> . Closing the bug as upstream, although if anyone can provide patches to resolve the problem, either post them here or the upstream bug. You can learn more about the DSP processing by reading the help file (Help|Help Contents|General), heading "Warning". Another approach might to use rakarrack with jack running on a real-time patched kernel (eg planetCCRMA).
*** Bug 641164 has been marked as a duplicate of this bug. ***
Thanks for the update, abrt makes it very easy to report a bug without checking first... is there any way for it to recognise a crash? I do find upstream's "You can learn more about..." rather amusing.
(In reply to comment #4) > Thanks for the update, abrt makes it very easy to report a bug without checking > first... is there any way for it to recognise a crash? Usually abort's abrt_hash is used to detect duplicate crashes, and it then attaches to existing report. I guess the backtrace was different enough (hence possibly died at a different point), that it created a different hash.