Bug 667801 - [abrt] celestia-1.6.0-1.fc14: nv50_program_validate: Process /usr/bin/celestia was killed by signal 6 (SIGABRT)
Summary: [abrt] celestia-1.6.0-1.fc14: nv50_program_validate: Process /usr/bin/celesti...
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Ben Skeggs
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6467f0eb0efd401109e65f62cce...
: 680756 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-06 20:16 UTC by mariolinux
Modified: 2012-05-03 21:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-03 21:11:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (57.60 KB, text/plain)
2011-01-06 20:16 UTC, mariolinux 		no flags Details
View All

Description mariolinux 2011-01-06 20:16:01 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: celestia
component: celestia
crash_function: nv50_program_validate
executable: /usr/bin/celestia
kernel: 2.6.35.10-74.fc14.x86_64
package: celestia-1.6.0-1.fc14
rating: 4
reason: Process /usr/bin/celestia was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294344690
uid: 500

How to reproduce
-----
1. I was running the demo
2.
3.
Comment 1 mariolinux 2011-01-06 20:16:04 UTC 
Created attachment 472126 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 18:30:05 UTC 
Backtrace analysis of bugs across components suggests the actual bug is in component mesa instead of component celestia, reassigning to mesa.

Bug #680756 from component warzone2100 was found to be similar to this bug.

This comment is automatically generated.
Comment 3 abrt-bot 2012-03-20 18:30:15 UTC 
*** Bug 680756 has been marked as a duplicate of this bug. ***
Comment 4 Adam Jackson 2012-05-03 21:11:22 UTC 
Reassigning to the nouveau maintainer, but F14 is unsupported now.  Please reopen if this still occurs with an updated release.
Note You need to log in before you can comment on or make changes to this bug.