Bug 584543

Summary: [abrt] crash in rosegarden4-10.02.1-1.fc12: Process /usr/bin/rosegarden was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dave Atkinson <da>
Component: rosegarden4Assignee: Callum Lerwick <seg>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: oget.fedora, seg
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:248cdb34dcb307197d065cb3695b2e3a55abb40d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 15:36:25 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 Dave Atkinson 2010-04-21 20:06:18 UTC
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: rosegarden
comment: Starting rosegarden crashes. Jackd was running as /usr/bin/jackd -v -dalsa -dhw:0 -r48000 -p512 -n2
component: rosegarden4
executable: /usr/bin/rosegarden
kernel: 2.6.32.11-99.fc12.x86_64
package: rosegarden4-10.02.1-1.fc12
rating: 4
reason: Process /usr/bin/rosegarden was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Start rosegarden
2. ...
3. It crashes :-(

Comment 1 Dave Atkinson 2010-04-21 20:06:21 UTC
Created attachment 408163 [details]
File: backtrace

Comment 2 Bug Zapper 2010-11-03 16:37:11 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 3 Dave Atkinson 2010-11-03 18:04:21 UTC
Oops, forgot about this - I fixed it by removing some unnecessary cruft from the command line contained in the gnome panel object I was starting rosegarden with.  Please update the status accordingly (and the behaviour's gone away at F13).

Comment 4 Bug Zapper 2010-12-03 15:36:25 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.