Bug 742232 - [abrt] brasero-2.30.2-1.fc13: strcmp: Process /usr/bin/brasero was killed by signal 11 (SIGSEGV)
Summary: [abrt] brasero-2.30.2-1.fc13: strcmp: Process /usr/bin/brasero was killed by ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: brasero
Version: 13
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:17770ee809a58927762ee187541...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-29 13:14 UTC by Florian van Oudgaarden
Modified: 2011-11-10 19:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-10 19:46:43 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (84.69 KB, text/plain)
2011-09-29 13:14 UTC, Florian van Oudgaarden
no flags Details

Description Florian van Oudgaarden 2011-09-29 13:14:34 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: brasero /media/Elements/done/dvds/Solomon-DVD-CTCA-.ISO
component: brasero
crash_function: strcmp
executable: /usr/bin/brasero
kernel: 2.6.34.9-69.fc13.x86_64
package: brasero-2.30.2-1.fc13
rating: 4
reason: Process /usr/bin/brasero was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1317297017
uid: 500

How to reproduce
-----
1.did not see it happen
2.
3.

Comment 1 Florian van Oudgaarden 2011-09-29 13:14:38 UTC
Created attachment 525564 [details]
File: backtrace

Comment 2 Jake Shipton 2011-11-10 19:46:43 UTC
Thank you for your bug report. 

We are sorry, but the Fedora Project is no longer releasing bug fixes or any
other updates for this version of Fedora. This bug will be set to
CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists
after upgrading to the latest version of Fedora, which is available from: 

http://fedoraproject.org/get-fedora

---

Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


Note You need to log in before you can comment on or make changes to this bug.