https://bugs.freedesktop.org/show_bug.cgi?id=99987
Emil Velikov changed:
What|Removed |Added
Status|NEEDINFO|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #22 from Pierre Ossman ---
Is there a symlink in place by default now? If so then I'd say the issue is
resolved.
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=99987
Timothy Arceri changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment #21 from Timothy A
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #20 from Pierre Ossman ---
Sorry, you're right. I misread this part when it was originally posted:
"Libglvnd relies on a GLX extension to..."
I interpreted it as "Libglvnd relies on ...", which was
obviously present in my test cases
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #19 from Dennis Schridde ---
(In reply to Pierre Ossman from comment #16)
> And it didn't explain why it is needed?
If it is not clear from the comments on this bug, please read the Red Hat bug I
referenced.
--
You are receiving th
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #18 from Pierre Ossman ---
For reference, NVIDIA claims that you need to have libGLX_indirect.so.0
pointing at their driver:
https://devtalk.nvidia.com/default/topic/915640/multiple-glx-client-libraries-in-the-nvidia-linux-driver-ins
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #17 from Pierre Ossman ---
So I found the code that handles this:
https://github.com/NVIDIA/libglvnd/blob/470fc824a38521a52707c6c0f59d827aa5e0f45a/src/GLX/libglxmapping.c#L519-L600
And "indirect" is indeed a poorly named fallback.
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #16 from Pierre Ossman ---
I'm afraid that didn't really make things clearer for me. Should I read your
answer as "Yes, libGLX_fallback.so is a fallback mechanism"?
And it didn't explain why it is needed?
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #15 from Dennis Schridde ---
(In reply to Pierre Ossman from comment #14)
> b) If it is indeed a fallback, why is that needed? I.e. why isn't Mesa being
> chosen? It does not seem robust and future proof to rely on a fallback
> mechan
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #14 from Pierre Ossman ---
That does make things work. But I'm hesitant to consider the issue closed
though. There are some outstanding questions:
a) I'm still getting direct rendering, despite the file being called
libGLX_indirect.s
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #13 from Hans de Goede ---
At least x2go and presumably also thinlinc can be fixed by doing:
sudo ln -s /usr/lib64/libGLX_mesa.so.0 /usr/lib64/libGLX_indirect.so.0
At least on a 64 bit Fedora, on 32 bit Fedora / other distros you w
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #12 from Pierre Ossman ---
I've made a new build here with xorg-server 1.19.1 and Mesa 9.2.5 (the oldest
that xorg-server 1.19 will allow), and that makes glxgears work fine. So GLVND
requires something newer than 1.14 it seems.
--
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #11 from Pierre Ossman ---
I can confirm that it works fine with Fedora's Xvnc. However it does not work
with my own build of TigerVNC:
> $ ./builddir/x86_64/unix/xserver/hw/vnc/Xvnc -ac -SecurityTypes=None :2
>
> Xvnc TigerVNC 1.7.
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #10 from Hans de Goede ---
I cannot reproduce this I've tried both:
Xvnc :1 -rfbauth /home/hans/.vnc/passwd
And then started an xterm on DISPLAY=:1 and in that xterm run glxgears as well
as glxinfo fine using lvmpipe.
As well as ru
https://bugs.freedesktop.org/show_bug.cgi?id=99987
Dennis Schridde changed:
What|Removed |Added
CC||devuran...@gmx.net
--
You are receivi
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #9 from Samuel Mannehed ---
Seeing as Ubuntu 17.04 also will have Mesa 13, I installed their nightly build
to test. My tests show that the problem does not exist on Ubuntu 17.04.
Applications such as glxgears work fine in ThinLinc, an
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #8 from Samuel Mannehed ---
To clarify, I have the above issues while using ThinLinc.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #7 from Samuel Mannehed ---
I have the same issue as the people above using Fedora 25. Upgrading libepoxy
solves the segmentation fault issues, but desktops or applications that need
OpenGL still do not work. Examples of desktops that
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #6 from Norman Gaywood ---
On Fedora under x2go, updated to libepoxy-1.4.1-1.fc25.x86_64 and the segfaults
have gone away in xfce4-terminal and gnome-terminal
However, with mesa-libGL-13.0.4-1.fc25.x86_64, glxinfo gives:
$ glxinfo
n
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #5 from Pierre Ossman ---
The analysis on bug 99027 seems to be only about why it is crashing, and not
why Mesa has changed its requirements on the X server. There is some talk about
8 bit depth, but the issue occurs on standard bit d
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #4 from Emil Velikov ---
(In reply to Pierre Ossman from comment #3)
> Bug 99027 looks like it's the same thing, but I don't agree with NOTOURBUG.
> The segfault might be GTK+'s fault, but the fact that Mesa 12 was quite
> content wit
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #3 from Pierre Ossman ---
Bug 99027 looks like it's the same thing, but I don't agree with NOTOURBUG. The
segfault might be GTK+'s fault, but the fact that Mesa 12 was quite content
with Xvfb/Xvnc/x2go and Mesa 13 isn't means more jus
https://bugs.freedesktop.org/show_bug.cgi?id=99987
--- Comment #2 from Emil Velikov ---
I would suggest building mesa w/o the glvnd stuff and ensuring the mesa
libGL/friends are picked.
That aside it seems similar to bug 99027 ? Admittedly I've got limited
experience with !Xorg so if you think a
https://bugs.freedesktop.org/show_bug.cgi?id=99987
Norman Gaywood changed:
What|Removed |Added
CC||ngayw...@une.edu.au
--- Comment #1 from
https://bugs.freedesktop.org/show_bug.cgi?id=99987
Bug ID: 99987
Summary: Mesa 13+ breaks Xvnc (and similar X servers)
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: norma
25 matches
Mail list logo
