Bug 630940 - [abrt] xmp-3.1.0-2.fc13: raise: Process /usr/bin/xmp was killed by signal 6 (SIGABRT)
Summary: [abrt] xmp-3.1.0-2.fc13: raise: Process /usr/bin/xmp was killed by signal 6 (...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xmp
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dominik 'Rathann' Mierzejewski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e38896e53575cfd93dbd450d4fa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-07 12:43 UTC by marty
Modified: 2010-12-10 11:25 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-10 11:25:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (6.71 KB, text/plain)
2010-09-07 12:43 UTC, marty 		no flags Details
View All

Description marty 2010-09-07 12:43:46 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: xmp mod/dreamfish-parallax.mod
component: xmp
crash_function: raise
executable: /usr/bin/xmp
kernel: 2.6.33.8-149.fc13.i686
package: xmp-3.1.0-2.fc13
rating: 4
reason: Process /usr/bin/xmp was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1283863196
uid: 501

How to reproduce
-----
1. played one chiptune (should be the same as http://chipmods.free.fr/32-64K/dreamfish/dreamfish-parallax.mod ) for some time
2.hit q
3.hit C-c
Comment 1 marty 2010-09-07 12:43:48 UTC 
Created an attachment (id=443500)
File: backtrace
Comment 2 Dominik 'Rathann' Mierzejewski 2010-12-04 17:42:31 UTC 
Hm, I can't seem to reproduce it. xmp quits after pressing 'q' immediately, so I never get the chance to press Ctrl+C after that.
Comment 3 Dominik 'Rathann' Mierzejewski 2010-12-04 22:36:34 UTC 
Could you try this build and see if it fixes it for you?
https://admin.fedoraproject.org/updates/xmp-3.3.0-1.fc13
Comment 4 Dominik 'Rathann' Mierzejewski 2010-12-10 11:25:43 UTC 
I'm assuming this is fixed. Feel free to reopen if not.
Note You need to log in before you can comment on or make changes to this bug.