Bug 539943

Summary: Fatal error in xf86freeInputList in /usr/sbin/nvidia-config-display
Product: [Fedora] Fedora Reporter: piio <bugzilla>
Component: pyxf86configAssignee: Adam Jackson <ajax>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: ajax, dmalcolm, ivazqueznet, james.antill, jeff.raber, jonathansteffan, katzj, lu9fcx, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:1f895350aef1b48feb9ebeb6a71d37998bdc16c3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-05 06:46:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description piio 2009-11-21 18:01:06 UTC 
abrt detected a crash.

How to reproduce: 1. running nvidia-config-display
Attached file: backtrace
cmdline: /usr/bin/python -tt /usr/sbin/nvidia-config-display
component: python
executable: /usr/bin/python
kernel: 2.6.31.5-127.fc12.x86_64
package: python-2.6.2-2.fc12
rating: 4
reason: Process was terminated by signal 11
Comment 1 piio 2009-11-21 18:01:10 UTC 
Created attachment 372776 [details]
File: backtrace
Comment 2 Dave Malcolm 2009-12-01 03:21:19 UTC 
Thank you for reporting this bug.

How reproducable is this problem?  If you run the program from a terminal, is an error message printed?

What version of pyxf86config do you have installed?

Looking at the backtrace, it looks like the problem occurred in the program's single thread in xf86freeInputList

Reassigning component from "python" to "pyxf86config"
Comment 3 Matěj Cepl 2010-02-26 12:27:08 UTC 
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Comment 4 Jeff Raber 2010-05-05 06:46:53 UTC 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers