Bug 562073 - [abrt] crash in paraview-3.6.2-1.fc12
[abrt] crash in paraview-3.6.2-1.fc12
Product: Fedora
Classification: Fedora
Component: paraview (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Orion Poplawski
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-02-05 02:16 EST by Gökhan Sever
Modified: 2010-02-08 11:28 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-02-08 11:28:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (25.50 KB, text/plain)
2010-02-05 02:16 EST, Gökhan Sever
no flags Details

  None (edit)
Description Gökhan Sever 2010-02-05 02:16:32 EST
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
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 02:16:34 EST
Created attachment 389005 [details]
File: backtrace
Comment 2 Orion Poplawski 2010-02-05 17:46:32 EST
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-05 23:30:36 EST
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.

Note You need to log in before you can comment on or make changes to this bug.