Bug 562073

Summary: [abrt] crash in paraview-3.6.2-1.fc12
Product: [Fedora] Fedora Reporter: Gökhan Sever <gokhansever>
Component: paraviewAssignee: Orion Poplawski <orion>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: orion, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:e0a156caa92ef7841574968040bcfb48d51f56d6
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-08 16:28:35 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 Gökhan Sever 2010-02-05 07:16:32 UTC 
abrt 1.0.4 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/paraview/paraview-real
component: paraview
executable: /usr/lib/paraview/paraview-real
kernel: 2.6.31.9-174.fc12.i686.PAE
package: paraview-3.6.2-1.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Install latest VTK or update
2. Install Paraview and run
3. Crash (Similar to Mayavi's)
Comment 1 Gökhan Sever 2010-02-05 07:16:34 UTC 
Created attachment 389005 [details]
File: backtrace
Comment 2 Orion Poplawski 2010-02-05 22:46:32 UTC 
Hmm, apparently it couldn't create a GLX context so it aborted.

Some searching indicates that re-installing video drivers may be the ticket.  What video card and driver are you using?
Does glxinfo work?
Comment 3 Gökhan Sever 2010-02-06 04:30:36 UTC 
I re-installed the latest NVIDIA (v190.53) from http://www.nvidia.com/object/unix.html and the errors disappeared.

Before I was getting the same error from the glxinfo and glxgears commands.

Even though I haven't updated the kernel after I previously built the NVIDIA drivers, I installed the new Xorg updates. Those must have mis-configured my system.

Thanks for the quick feedback.

This bug could be closed.