VirtualGL-3.1-3.el9.x86_64.rpm

[Roland S]

Hi,

I'm trying to install VirtualGL.
I need the one provided for RHEL9 (EPEL) to maintain versions.

# dnf install /tmp/VirtualGL-3.1-3.el9.x86_64.rpm
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register.

Last metadata expiration check: 2:08:00 ago on Thu Jan  8 11:42:21 2026.
Error:  
Problem: conflicting requests
 - nothing provides libturbojpeg.so.0()(64bit) needed by VirtualGL-3.1-3.el9.x86_64 from @commandline
 - nothing provides libturbojpeg.so.0(TURBOJPEG_1.0)(64bit) needed by VirtualGL-3.1-3.el9.x86_64 from @commandline
 - nothing provides libturbojpeg.so.0(TURBOJPEG_1.2)(64bit) needed by VirtualGL-3.1-3.el9.x86_64 from @commandline
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

I think it's just a packet mismatch
# rpm -q --whatprovides /usr/lib64/libjpeg.so.62.3.0
libjpeg-turbo-2.0.90-7.el9.x86_64

I tried to cheat my way around with a link but it didn't work
# ls -la /usr/lib64/libturbojpeg.so.0
lrwxrwxrwx. 1 root root 28 Jan  7 09:16 /usr/lib64/libturbojpeg.so.0 -> /usr/lib64/libjpeg.so.62.3.0

Any ideas how I can fix this?

Cheers,

Roland Soderstrom

[DRC]

1. You don't need to use the package provided by RHEL in order to "maintain versions."  You can use our YUM repository:

   https://virtualgl.org/Downloads/YUM

2. We don't support distribution-supplied VirtualGL packages, because those packages often break things due to misunderstanding how VirtualGL is supposed to work.  We only support our official packages.  Distribution-supplied VirtualGL packages will probably work for the most common use cases, but they may not work with 3D applications that load libGL in uncommon ways.

3. 'dnf install' should pick up the necessary dependencies, but I guess it isn't doing that.  Try searching for a package that contains /usr/lib64/libturbojpeg.so.0.  Note that libjpeg and libturbojpeg are separate libraries provided by libjpeg-turbo.  They implement different APIs.  VirtualGL needs the TurboJPEG API library (libturbojpeg), not the libjpeg API library (libjpeg.)  The TurboJPEG API library is usually distributed in a package called 'turbojpeg'.

Also note that the version of libjpeg-turbo provided by RHEL 9 (2.1 beta1) is EOL.  This highlights a problem with Red Hat's version management.  They freeze RHEL on a specific upstream version, even if the upstream version is in beta, and they don't necessarily integrate upstream bug fixes unless someone reports those bugs through the Red Hat system.  The libjpeg-turbo 2.1.x branch has received over 50 bug fixes since 2.1 beta1, and I doubt that RHEL 9 has all of those.  Similarly, VirtualGL 3.1.4 has 16 bug fixes relative to VirtualGL 3.1 (the version that EPEL provides.)

tl;dr: If you choose to use distribution-supplied packages, then The VirtualGL Project (and The libjpeg-turbo Project, which I also maintain) can only support the intersection between those packages and our official ones.  If a bug is only reproducible with the distribution-supplied packages and not the official packages, then it is the distributor's responsibility to fix it.

DRC

--
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 virtualgl-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/virtualgl-users/b20d45c5-582e-4e04-9877-6ec0a6a4f6c3n%40googlegroups.com.

[Roland S]

Hi,

Yes, we actually had the VirtualGL repo configured but not for rhel9...
We use SUSE Manager for our repos, and that is the only valid repo source.
Now it's installing nicely.

Cheers
Roland Soderstrom