Bug 593176

Summary: [abrt] crash in totem-2.28.5-1.fc12: pre_resample: Process /usr/bin/totem was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: robert fairb <rob2098>
Component: timidity++Assignee: Jindrich Novy <jnovy>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bnocera, hdegoede, jnovy, otte, pknirsch
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:44c8e559cc91aa13dd82b0989e6c769ccd6de550
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 14:36:05 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
File: cmdline none

Description robert fairb 2010-05-18 04:59:36 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
Attached file: cmdline
comment: a text opened up with inflexible determination
component: totem
crash_function: pre_resample
executable: /usr/bin/totem
global_uuid: 44c8e559cc91aa13dd82b0989e6c769ccd6de550
kernel: 2.6.32.11-99.fc12.i686
package: totem-2.28.5-1.fc12
rating: 4
reason: Process /usr/bin/totem was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.i was just playing some midi files
2.
3.

Comment 1 robert fairb 2010-05-18 04:59:38 UTC
Created attachment 414726 [details]
File: backtrace

Comment 2 robert fairb 2010-05-18 04:59:39 UTC
Created attachment 414727 [details]
File: cmdline

Comment 3 robert fairb 2010-05-18 04:59:57 UTC
Package: totem-2.28.5-1.fc12
Architecture: i686
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1.i was just playing some midi files
2.
3.


Comment
-----
a text opened up with inflexible determination

Comment 4 Bastien Nocera 2010-05-18 09:56:35 UTC
Crash in timidity.

Comment 5 Bastien Nocera 2010-05-18 09:57:02 UTC
*** Bug 593170 has been marked as a duplicate of this bug. ***

Comment 6 Benjamin Otte 2010-05-18 12:53:31 UTC
(In reply to comment #4)
> Crash in timidity. 
>
Looks like it, yeah.

Comment 7 Bug Zapper 2010-11-03 14:41:10 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 8 Bug Zapper 2010-12-03 14:36:05 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.