Bug 712770

Summary: [abrt] glx-utils-7.8.2-1.fc13: XF86DRIQueryExtension: Process /usr/bin/glxinfo was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: German Jurado Cano <elpaisita.med>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: ajax
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:0b88e9dea609bc5735110c06e702a26c1d25f818
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 11:40:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description German Jurado Cano 2011-06-13 05:03:47 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: glxinfo
component: mesa
crash_function: XF86DRIQueryExtension
executable: /usr/bin/glxinfo
kernel: 2.6.34.8-68.fc13.i686.PAE
package: glx-utils-7.8.2-1.fc13
rating: 4
reason: Process /usr/bin/glxinfo was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1307941063
uid: 500

How to reproduce
-----
1.Estaba ejecutando el icon de compiz-fusion
2.
3.
Comment 1 German Jurado Cano 2011-06-13 05:03:50 UTC 
Created attachment 504358 [details]
File: backtrace
Comment 2 Adam Jackson 2011-06-15 18:36:32 UTC 
Please attach the output of 'rpm -qvV mesa-libGL'
Comment 3 Bug Zapper 2011-06-27 11:40:45 UTC 
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.