Bug 249195
Summary: | vtk using libOSmesa seg-fault on i915_dri | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Ed Hill <ed> |
Component: | mesa | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | axel.thimm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-08-12 15:58:05 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: |
Description
Ed Hill
2007-07-22 13:11:56 UTC
I just installed the vtk packages from updates-testing on an F-7 i386 machine with an ATI M10 chipset (FireGL Mobility T2) and vtk programs (eg. some python scripts) work nicely on it -- no segfaults. So I suppose this bug is some sort of interaction between vtk and the i915_dri bits. I'll try other machines and building VTK with and without OSMesa next to see if that narrows it down. Oh wow. Symbol resolution conflicts hooray! I'd really like to see if this is reproducable on 6.5.2-6 or later. F7 contained 6.5.2-10 so that'd be a good place to start. Comment #1 already indicated that the problem vanished on F7, so the check is already done. What would you suggest to do with FC6? Just not build against osmesa? I don't have the time today but this weekend (at the latest!) I'll install F7-x86_64 on the Dell D820 that triggers this problem. I can verify that locally built VTK rpms that don't include OSMesa work fine so it seems very likely that disabling OSMesa will help the (few?) folks trying to use VTK with the i915_dri driver on FC-6. Other than the move to F7 (which I intended to do anyway) is there anything else (e.g., back-traces or library symbol lists?) that I can do to help pin down this problem? (In reply to comment #4) > Other than the move to F7 (which I intended to do anyway) is there anything > else (e.g., back-traces or library symbol lists?) that I can do to help pin > down this problem? If you are adventurous enough you could try rebuilding mesa >= 6.5.2-6 on FC6 (for example F7's mesa) and rebuild vtk against that. According to comment #2 this should work then, and maybe ajax would even issue an update for FC6's mesa :) I installed F7 on the machine that triggered this problem (a Dell Latitude D820 with the "Intel 945GM/GMS, 943/940GML" integrated graphics controller) and the VTK segfaults are now gone -- all the VTK programs I use and write seem to be working as they should. FWIW, I noticed that F7 selected (by default) the "intel" X driver and not the i810 as used in FC6. I'm closing this bug as WORKSFORME. If someone really needs VTK on FC6 with an Intel graphics chipset then please re-open it. |