| View previous topic :: View next topic |
| Author |
Message |
davydm
n00b
Joined: 06 Jan 2017
Posts: 73
|
 Posted: Thu Aug 16, 2018 3:54 pm Post subject: Celestia issues |
 |
|
I hope this is the right place to post this; please shout if I should move this somewhere else, but it seemed like the closest fit:
OpenGL is working fine on my system -- Steam games, glxgears, glxinfo (reports NVIDIA vendor, so all good). I'm using x11-drivers/nvidia-drivers=396.51 from official gentoo sources.
Today I installed Celestia so my son could check it out. The app shows the splash screen, then exits. From a console, I get a little more info by running:
| Code: |
# LIBGL_DEBUG=verbose celestia
libGL: screen 0 does not appear to be DRI2 capable
libGL: OpenDriver: trying /usr/lib64/dri/tls/swrast_dri.so
libGL: OpenDriver: trying /usr/lib64/dri/swrast_dri.so
libGL: Can't open configuration file /home/daf/.drirc: No such file or directory.
libGL: Can't open configuration file /home/daf/.drirc: No such file or directory.
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
*** Cannot find the double-buffered visual.
*** Trying single-buffered visual.
*** No appropriate OpenGL-capable visual found.
|
Everything my google-fu has brought me suggests that I should get this error for anything attempting to use opengl if I'm getting it for one. The mentioned .so files under /usr/lib64 exist. I apparently have the correct opengl selected:
| Code: |
# eselect opengl list
[1] nvidia *
[2] xorg-x11
|
As far as I can tell, Celestia should just run; yet stubbornly, it refuses to. Any help appreciated. |
|
| Back to top |
|
 |
davydm
n00b
Joined: 06 Jan 2017
Posts: 73
|
| Posted: Thu Aug 16, 2018 4:08 pm Post subject: |
|
|
| (update) I can work around this by changing /usr/lib64/libGL.so and /usr/lib64/libGL.so.1 to point at nvidia's libGL.so (they were pointing at mesa's) -- the question is: shouldn't be doing this? Or is there a another better (more official) way to do this? And what repercussions can I face by manualy fiddling with these two links? |
|
| Back to top |
|
|
iandoug
l33t
Joined: 11 Feb 2005
Posts: 832
Location: Cape Town, South Africa
|
| Posted: Mon Mar 25, 2019 12:50 pm Post subject: |
|
|
| davydm wrote: | | (update) I can work around this by changing /usr/lib64/libGL.so and /usr/lib64/libGL.so.1 to point at nvidia's libGL.so (they were pointing at mesa's) -- the question is: shouldn't be doing this? Or is there a another better (more official) way to do this? And what repercussions can I face by manualy fiddling with these two links? |
You ever get it to work?
Have similar issues here, and I know it used to work in the past.
Am using Nvidia.
Thanks, Ian
_________________
Asus X570-PRO, Ryzen 7 5800X, GeForce GTX 1650, 32 GB RAM | Asus Sabertooth P990, AMD FX-8150, GeForce GTX 560, 16GB Ram |
|
| Back to top |
|
|
davydm
n00b
Joined: 06 Jan 2017
Posts: 73
|
| Posted: Mon Mar 25, 2019 1:25 pm Post subject: |
|
|
| iandoug wrote: | | davydm wrote: | | (update) I can work around this by changing /usr/lib64/libGL.so and /usr/lib64/libGL.so.1 to point at nvidia's libGL.so (they were pointing at mesa's) -- the question is: shouldn't be doing this? Or is there a another better (more official) way to do this? And what repercussions can I face by manualy fiddling with these two links? |
You ever get it to work?
Have similar issues here, and I know it used to work in the past.
Am using Nvidia.
Thanks, Ian |
No, unfortunately not. I had good intentions of filing a bug against the package, and forgot about it. However, I have filed a bug now: https://bugs.gentoo.org/681732 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Gamers & Players
