So in re-reading your initial message, something raised a red flag:
> On the older laptop there is no problem. On the newer one I get the
> error message in the subject line when I run any command that involves
> some gui-based executable. I have to run "optirun <command>" to get
> around this. This is not sustainable.
If you're getting that error without using vglrun/optirun, then
something is definitely wrong with your installation. In general, that
error would be generated if you are preloading libdlfaker.so without
also preloading libvglfaker.so, so double check your LD_PRELOAD
environment variable. If you use vglrun, libdlfaker.so will never be
preloaded without also preloading libvglfaker.so, so it should be
impossible to get that error on a properly-configured VirtualGL system.
However, it's easily reproducible if you, for instance, do:
LD_PRELOAD=libdlfaker.so {VirtualGL_build_directory}/bin/dlfakerut
On 4/24/18 3:12 AM, Johann wrote:
> The version I showed in my previous post was one I compiled from your
> sources.
> I did that because the official version (I have tried several of the
> older versions also)
> gave the same problem.
>
> I have removed an attempted solution (export
> LD_PRELOAD=/usr/lib/libdlfaker.so) from my shell startup file
> which proved to make the situation worse.
>
> Now I can work despite some error messages from time to time.
>
> Regards.
> Johann
> On Monday, 23 April 2018 17:40:03 UTC+2, DRC wrote:
>
> optirun/Bumblebee is not maintained or supported by us. Can you
> reproduce this problem with our official VirtualGL packages:
> https://sourceforge.net/projects/virtualgl/files/2.5.2/
> ? <https://sourceforge.net/projects/virtualgl/files/2.5.2/?>?
>
> Unfortunately O/S distributors sometimes package VirtualGL incorrectly,
> in ways that cause certain applications to break (particularly when
> those applications try to use dlopen() to load libGL.) This is often a
> result of trying to shoehorn VirtualGL into particular system
> requirements for DSOs without fundamentally understanding that
> VirtualGL
> is an interposer and thus needs to be excepted from those requirements
> in order to avoid breakage.
>
> The fact that libvglfaker.so and libvglfaker-nodl.so are exactly the
> same size on your system makes me immediately suspicious that you're
> using an O/S-supplied or downstream VirtualGL package that was packaged
> incorrectly. Please try again with our official DEB packages. If you
> are still having problems with those packages, then we can go from
> there.
>
> Also, I assume that you have installed the same version of the nVidia
> proprietary drivers on both computers and that everything else is
> mostly
> the same between the two of them.
>
> DRC
>
> On 4/23/18 7:38 AM, Johann wrote:
> > I have installed virtualgl (2.5.2) on Debian on two laptops to
> work with
> > bumblebee and NVIDIA Graphics cards.
> >
> > On the older laptop there is no problem. On the newer one I get the
> > error message in the subject line when I run any command that
> involves
> > some gui-based executable. I have to run "optirun <command>" to get
> > around this. This is not sustainable.
> >
> > In /usr/lib:
> >
> > -rw-r--r-- 1 root root 643544 Apr 23 10:07 libvglfaker.so
> > -rw-r--r-- 1 root root 643544 Apr 23 10:07 libvglfaker-nodl.so
> >
> > Also, while I can run Darktable with the opengl option on the first
> > computer, it tells me on the second one that that option is not
> > available although I run it through optirun or vglrun|.|
> >
> > How do I solve this problem?
> >
> > Regards
> > Johann
--
You received this message because you are subscribed to the Google Groups
"VirtualGL User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/virtualgl-users/a78a941e-4f16-5da5-d04a-e0422e3ade10%40virtualgl.org.
For more options, visit https://groups.google.com/d/optout.
