Bug 683726 - [abrt] vegastrike-0.5.0-18.fc14: run_vp: Process /usr/bin/vegastrike was killed by signal 11 (SIGSEGV)
Summary: [abrt] vegastrike-0.5.0-18.fc14: run_vp: Process /usr/bin/vegastrike was kill...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5f94e228d44a1d01374cc69c2f5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-10 07:36 UTC by Tristan Moody
Modified: 2012-01-03 19:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-03 19:25:56 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (48.35 KB, text/plain)
2011-03-10 07:36 UTC, Tristan Moody 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Tristan Moody 2011-03-10 07:36:47 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 49514 bytes
cmdline: vegastrike
comment: Will look into it more in the next few days.
component: vegastrike
Attached file: coredump, 166789120 bytes
crash_function: run_vp
executable: /usr/bin/vegastrike
kernel: 2.6.35.11-83.fc14.i686.PAE
package: vegastrike-0.5.0-18.fc14
rating: 4
reason: Process /usr/bin/vegastrike was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299741010
uid: 500

How to reproduce
-----
1.Choose Introduction
2.Move the mouse to the scroll down button
3.Program segfaults before mouse reaches button
Reproducible: always.
Comment 1 Tristan Moody 2011-03-10 07:36:49 UTC 
Created attachment 483374 [details]
File: backtrace
Comment 2 Hans de Goede 2011-03-10 08:47:54 UTC 
This seems to be an issue with mesa, changing component.
Comment 3 Adam Jackson 2012-01-03 19:25:56 UTC 
Mass close of abrt reports against F14.  Please update to at least F15, and reopen if this issue still occurs for you.
Note You need to log in before you can comment on or make changes to this bug.