Bug 615657 - [abrt] crash in rosegarden4-10.04.2-1.fc13: raise: Process /usr/bin/rosegarden was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in rosegarden4-10.04.2-1.fc13: raise: Process /usr/bin/rosegarde...
Alias: None
Product: Fedora
Classification: Fedora
Component: rosegarden4   
(Show other bugs)
Version: 13
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Callum Lerwick
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:854797357facff3a5e06cfdc75c...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-17 19:57 UTC by chuck elliot
Modified: 2011-06-29 13:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-29 13:21:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (18.27 KB, text/plain)
2010-07-17 19:57 UTC, chuck elliot
no flags Details

Description chuck elliot 2010-07-17 19:57:39 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: rosegarden
component: rosegarden4
crash_function: raise
executable: /usr/bin/rosegarden
global_uuid: 854797357facff3a5e06cfdc75c8c520676b5c09
package: rosegarden4-10.04.2-1.fc13
rating: 4
reason: Process /usr/bin/rosegarden was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. use grid editor to delete notes
2. one particular note causes crash

Comment 1 chuck elliot 2010-07-17 19:57:45 UTC
Created attachment 432627 [details]
File: backtrace

Comment 2 Orcan Ogetbil 2010-11-06 05:49:18 UTC
Could you try the new 10.10 build and see if you still have the problem?

You can get it from koji
   For Fedora 13: http://koji.fedoraproject.org/koji/buildinfo?buildID=203634
   For Fedora 14: http://koji.fedoraproject.org/koji/buildinfo?buildID=203633
Note that you need to download both the rosegarden4.x86_64 and the 2 noarch fonts packages.

Alternatively, you can wait a day or two until this build gets into the updates-testing repo.


Comment 3 Orcan Ogetbil 2010-11-06 05:50:23 UTC
> Note that you need to download both the rosegarden4.x86_64 and the 2 noarch
> fonts packages.

Sorry. I meant rosegarden4.i686

Comment 4 chuck elliot 2011-01-01 23:10:57 UTC
The new 10.10 build seems to check out o.k.
Actions which appeared to cause the crash 
now appear not to do so, although I have not
carried out particularly thorough testing.
'sorry for the delay in responding - facilities
out of action owing to bad weather.

Comment 5 Bug Zapper 2011-06-01 13:36:15 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13'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 13 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: 

Comment 6 Bug Zapper 2011-06-29 13:21:53 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.