From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libGL symlinks vs `eselect opengl`
Date: Wed, 29 Aug 2018 19:19:10 +0300 [thread overview]
Message-ID: <20180829191910.30a0fa70de6c7fa720b148c5@gentoo.org> (raw)
In-Reply-To: <CAJjP=BvzmGkFor4n1p0dWtQ_yQtOYTKgjwjhL16cMVr_p2Bhcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2100 bytes --]
Hi!
On Wed, 22 Aug 2018 20:33:00 +0200 Davyd McColl wrote:
> The other day I installed Celestia for the entertainment of my son, who is
> delighted with anything stellar / planetary. Celestia wouldn't start up,
> and, long-story-short, I tracked down the issue to the symlinks:
>
> /usr/lib64/libGL.so
> /usr/lib64/libGL.so.1
>
> which ultimately point to
>
> /usr/lib64/libGL.so.1.2.0,
>
> provided by media-libs/mesa. Naturally, I assumed I'd made a mistake with
> `eselect` at some point, so I checked with `eselect opengl list` and found
> that, as expected, my selected opengl implementation was nvidia. Just in
> case, I switched over to xorg-x11 (mesa) and back again, but this didn't
> fix the problem.
>
> Manually redirecting these to /usr/lib64/opengl/nvidia/lib/libGL.so
> (provided by x11-drivers/nvidia-drivers) works, however, of course, portage
> doesn't know anything about this, so the update I received today for
> media-libs/mesa reverted these symlinks back to pointing at mesa libs.
>
> So the questions I have are these:
> 1) Am I reasonable in expecting `eselect opengl` to maintain these
> symlinks? I feel like it's a reasonable expectation, but perhaps there's
> just yet another thing I have to learn / understand.
No, eselect opengl works differently. It uses /etc/env.d to alter
LDPATH and OPENGL_PROFILE environment variables. It also changes
xorg.conf.
So you may need to restart your X server and source /etc/profile in
active shells for changes to take effect.
> 2) Should I be logging a bug (against eselect, or perhaps celestia, since
> this is the only app which seems to have suffered this fate -- games like
> Torchlight 2 and utils like glxgears work just fine; glxinfo reports NVIDIA
> extensions), or is there just something I've fundamentally missed or messed
> up here?
If glxinfo reports correct data and glxgears works fine, then this
may be a bug and please report it. You may CC both celestia and
opengl since right now it is not obvious which is the culprit.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-29 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 18:33 [gentoo-user] libGL symlinks vs `eselect opengl` Davyd McColl
2018-08-29 16:19 ` Andrew Savchenko [this message]
2018-08-29 18:20 ` Davyd McColl
2018-12-23 15:12 ` Andrew Savchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180829191910.30a0fa70de6c7fa720b148c5@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox