Bug 570138

Summary: [abrt] crash in arts-8:1.5.10-11.fc12: Process /usr/bin/artsd was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: afaucher
Component: artsAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: kevin, rdieter, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:3ecf4e326133cfa22ae0e00d456cbb6298e78220
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-24 17:29:31 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 Flags
File: backtrace none

Description afaucher 2010-03-03 13:09:54 UTC
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/artsd -F 10 -S 4096 -s 60 -m artsmessage -l 3 -f
component: arts
executable: /usr/bin/artsd
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: arts-8:1.5.10-11.fc12
rating: 3
reason: Process /usr/bin/artsd was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 afaucher 2010-03-03 13:09:56 UTC
Created attachment 397550 [details]
File: backtrace

Comment 2 Steven M. Parrish 2010-03-13 02:03:26 UTC
Thank you for taking the time to report this issue to us.  This is an issue which is best addressed by the upstream developers.

Please file a report at bugs.kde.org , and when done add the upstream report info to this report.

We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

Thank you for the bug report.

Comment 3 Kevin Kofler 2010-03-24 17:29:31 UTC
Upstream no longer supports aRts, it makes no sense to report aRts bugs to upstream.

The backtrace matches the one in bug 558570.

*** This bug has been marked as a duplicate of bug 558570 ***