[Paraview] Depth rendering issues on ParaView Desktop 5.1.0

[Júlio Hoffimann]

Hi David,

On my laptop, the command pkgfile doesn't find any repo for the drivers
i965_dri.so and swrast_dri.so.

*This is what I have installed from the list of open-source drivers:*

extra/xf86-video-fbdev 0.4.4-5 (xorg-drivers xorg) [installed]
    X.org framebuffer video driver

extra/xf86-video-intel 1:2.99.917+691+ga77397a-1 (xorg-drivers xorg)
[installed]
    X.org Intel i810/i830/i915/945G/G965+ video drivers

extra/xf86-video-vesa 2.3.4-2 (xorg-drivers xorg) [installed]
    X.org vesa video driver

*This is the relevant section of my /var/log/Xorg.0.log:*

[     4.483] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[     4.483] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[     4.483] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200,
6200, P6300
[     4.483] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     4.483] (II) FBDEV: driver for framebuffer: fbdev
[     4.483] (II) VESA: driver for VESA chipsets: vesa
[     4.494] (II) intel(0): Using Kernel Mode Setting driver: i915, version
1.6.0 20160229
[     4.494] (II) intel(0): SNA compiled from 2.99.917-691-ga77397a
[     4.494] (WW) Falling back to old probe method for modesetting
[     4.494] (WW) Falling back to old probe method for fbdev
[     4.494] (II) Loading sub module "fbdevhw"
[     4.494] (II) LoadModule: "fbdevhw"
[     4.494] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     4.495] (II) Module fbdevhw: vendor="X.Org Foundation"
[     4.495] compiled for 1.18.4, module version = 0.0.2
[     4.495] ABI class: X.Org Video Driver, version 20.0
[     4.495] (WW) Falling back to old probe method for vesa

According to the Arch Linux documentation (
https://wiki.archlinux.org/index.php/xorg#Driver_installation), the Intel
driver has priority over the others, is it being picked up in the log?

I updated ParaView from AUR, could you confirm that 5.x.x releases are
working with Arch? I only have another machine with Ubuntu to test on.

-Júlio

2016-08-08 7:46 GMT-05:00 David Lonie <david.lonie at kitware.com>:

> Hi Julio,
>
> On Sun, Aug 7, 2016 at 2:01 PM, Júlio Hoffimann
> <julio.hoffimann at gmail.com> wrote:
> > Hi David,
> >
> > I downloaded all 4.x.x releases and everything works as expected. I
> > downloaded ParaView 5.0.1 and ParaView 5.1.2, both give me the following
> > error message about the driver:
> >
> > libGL error: unable to load driver: i965_dri.so
> > libGL error: driver pointer missing
> > libGL error: failed to load driver: i965
> > libGL error: unable to load driver: i965_dri.so
> > libGL error: driver pointer missing
> > libGL error: failed to load driver: i965
> > libGL error: unable to load driver: swrast_dri.so
> > libGL error: failed to load driver: swrast
> > Segmentation fault (core dumped)
> >
> > Based on that outcome, I confirm that this is a bug introduced somewhere
> in
> > between the 4.x.x and 5.x.x releases. How can we go and investigate this
> > further? I can print more information about my system in case it is
> needed.
>
> Are those drivers installed correctly? Looks like they're provided by
> the intel-dri and mesa packages on archlinux:
>
> $ pkgfile i965_dri.so
> extra/intel-dri
> $ pkgfile swrast_dri.so
> extra/mesa
>
> Those errors, and that the 5.x releases are working on other archlinux
> installs, make me think this is a configuration issue with this
> specific machine. The X log file /var/log/Xorg.0.log may have some
> clues if there's a problem initializing the driver support needed for
> the newer paraview. I'm not convinced this is a bug in ParaView just
> yet -- the 5.x versions require different OpenGL contexts than the 4.x
> versions, so it may be that something is not quite right for the newer
> contexts.
>
> Have you tried building from source and setting VTK_RENDERING_BACKEND
> to OpenGL (instead of OpenGL2) in cmake? That would build paraview
> with the older backend used by the 4.x line, and might work better for
> you.
>
> The only other idea that comes to mind would be to grab the
> development branch from git and use 'git bisect' to identify the
> commit that introduced the functionality that's failing on this
> installation:
>
> Getting the sources from git:
> https://gitlab.kitware.com/paraview/paraview/blob/master/
> Documentation/dev/git/develop.md
>
> Git bisect:
> http://stackoverflow.com/questions/4713088/how-to-use-git-bisect
>
> Hope this helps,
> Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160808/352cf4a5/attachment.html>