Bug 679774 - Process /usr/bin/glxgears was killed by signal 11
Summary: Process /usr/bin/glxgears was killed by signal 11
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa-demos
Version: 15
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 13:50 UTC by Dmitriy Pomerantsev
Modified: 2018-04-11 16:29 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-05 08:22:29 UTC
Type: ---

Attachments (Terms of Use)
abrt log of glxgears crash (1.24 KB, application/x-gzip)
2011-02-23 13:50 UTC, Dmitriy Pomerantsev 		no flags Details
uncompressed empty backtrace (3.10 KB, text/plain)
2011-03-05 08:22 UTC, Matěj Cepl 		no flags Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Description Dmitriy Pomerantsev 2011-02-23 13:50:20 UTC 
Created attachment 480452 [details]
abrt log of glxgears crash

Description of problem:
Glxgears crashed on attempt of draw of gears. But -info key is working well.

Version-Release number of selected component (if applicable):
Fedora 15 radeon test day Live CD. With this hardware: http://www.smolts.org/client/show/pub_c647d0b3-b8fb-4fa5-b7b5-b9b9c8584abf

How reproducible:
Just start start glxgears

Steps to Reproduce:
1. Open gnome terminal.
2. Start gxlgears.
  
Actual results:
Glxgears is crashed.

Expected results:
Glxgears is working.
Comment 1 Matěj Cepl 2011-03-05 08:22:29 UTC 
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded. Would be able to get better crash report by using abrt?

Unfortunately, we cannot use this backtrace.

Closing as INSUFFICIENT_DATA.
Comment 2 Matěj Cepl 2011-03-05 08:22:55 UTC 
Created attachment 482419 [details]
uncompressed empty backtrace
Comment 3 Dmitriy Pomerantsev 2011-03-06 13:23:00 UTC 
I can't. The computer hanging before I can complete full trace...
Note You need to log in before you can comment on or make changes to this bug.