Bug 593794

Summary: [abrt] crash in rosegarden4-10.02.1-1.fc12: ~_Rb_tree: Process /usr/bin/rosegarden was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jean.seyral
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: i686   
OS: Linux   
Whiteboard: abrt_hash:daf04d561215a3d357bfdae91a09ee9faad8e4dc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:33:10 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 jean.seyral 2010-05-19 17:42:24 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rosegarden
comment: crash occur each time i close rosegarden.
component: rosegarden4
crash_function: ~_Rb_tree
executable: /usr/bin/rosegarden
global_uuid: daf04d561215a3d357bfdae91a09ee9faad8e4dc
kernel: 2.6.31.12-1.rt20.1.fc12.ccrma.i686.rtPAE
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. Open rosegarden
2. Close rosegarden

Comment 1 jean.seyral 2010-05-19 17:42:34 UTC
Created attachment 415212 [details]
File: backtrace

Comment 2 Orcan Ogetbil 2010-05-19 17:47:45 UTC
Can you test the update that is on the testing repo? thanks.

# yum --enablerepo updates-testing update rosegarden4

Comment 3 jean.seyral 2010-05-20 12:33:27 UTC
Hello,
i just tried the testing repo version (rosegarden4-10.04.2-1.fc12) and reproduced the same error. I reported the backtrace of the test repo version here :
https://bugzilla.redhat.com/show_bug.cgi?id=594042

Comment 4 Bug Zapper 2010-11-03 14:34:54 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 Bug Zapper 2010-12-03 14:33:10 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.