Andreas, that got it.
Thanks for sticking with me on this. It's been an issue since 11/4.
Not enough complaints about this, so it probably my one-off. Thanks again.
On Mon, Dec 18, 2017 at 11:15 AM, Andreas Beckmann wrote:
> Hi,
>
> I think I found it. You have some cruft MESA libGL that i
Hi,
I think I found it. You have some cruft MESA libGL that is being used:
On 2017-12-18 16:14, Chris Manougian wrote:
> /usr/lib/mesa-diverted/x86_64-linux-gnu/:
> total 1172
> lrwxrwxrwx 1 root root 10 Nov 18 14:31 libGL.so -> libGL.so.1
> lrwxrwxrwx 1 root root 14 Nov 18 09:01 libGL.so
On 2017-12-18 03:36, Chris Manougian wrote:
> Andreas, here's the result of reportbug -N 879041:
That is absolutely not what I expected. (reportbug should have sent an
email with all the gathered information to the bug report)
But it shows that something is seriously broken.
Please send the outpu
Andreas, here's the result of reportbug -N 879041:
chris@asus:~$ reportbug -N 879041
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[4369:4369:1217/212813.695099:ERROR:gl_context_glx.cc(232)] Couldn't
make context current with X drawable.
[4369:4369:
On 2017-12-17 23:28, Chris Manougian wrote:
> chris@asus:~$ DISPLAY=:0 glxinfo -B
> name of display: :0
> libGL error: No matching fbConfigs or visuals found
That error is from MESA's libGL.so.1
> libGL error: failed to load driver: swrast
> X Error of failed request: GLXBadContext
> Major opc
On Sun, 17 Dec 2017 05:53:57 +0100 Andreas Beckmann wrote:
> On 2017-12-16 05:34, Chris Manougian wrote:
> >>> root@asus:/home/chris# glxinfo | grep OpenGL
> >>> libGL error: No matching fbConfigs or visuals found
> >>> libGL error: failed to load driver: swrast
> >>> X Error of failed request: G
On 2017-12-16 05:34, Chris Manougian wrote:
>>> root@asus:/home/chris# glxinfo | grep OpenGL
>>> libGL error: No matching fbConfigs or visuals found
>>> libGL error: failed to load driver: swrast
>>> X Error of failed request: GLXBadContext
>>> Major opcode of failed request: 154 (GLX)
>>> Mi
I searched libglvnd and this is what comes up:
libglvnd-core-dev [This is Installed]
libglvnd-dev [This is installed]
libglvnd0 [This is installed]
libglvnd0-nvidia [Not Installed]
libglvnd0:i386 [This is installed]
libglvnd0-nvidia is version 384.98-3, and it makes sense that it should be
insta
Andreas, mesa 17.3.0-1 has dropped into sid, and I'm still getting the same
glxinfo, so this does look like an upstream nvidia driver issue. Thanks
for following up.
On Thu, Dec 14, 2017 at 10:09 AM, Andreas Boll
wrote:
> Control: reassign -1 src:nvidia-graphics-drivers
>
> On Fri, Dec 01, 2017
Control: reassign -1 src:nvidia-graphics-drivers
On Fri, Dec 01, 2017 at 08:27:05AM -0500, Chris Manougian wrote:
> 384.98-2 dropped into sid this morning. It installed.
>
> This last weekend, I purged nvidia, and reinstalled. What was available in
> sid was 375.82, and it stalled. Then 378 cam
384.98-2 dropped into sid this morning. It installed.
This last weekend, I purged nvidia, and reinstalled. What was available in
sid was 375.82, and it stalled. Then 378 came into sid, and it was
installable. Then this morning, I was able to install 384.98-2.
Still having a mesa-related error:
Andreas, the experimental 384.98 driver failed. Sid's 375.82 is
installable. This all started with the last Xorg and Mesa updates.
There's a new Mesa at RC5 in experimental. I guess I'm going to wait
for that to drop into sid.
On Wed, 18 Oct 2017 19:07:41 +0200 Dirk Lehmann wrote:
> During installing the Nvidia Geforce driver version 384.90 the
> following error occurs:
Please use the 384.xx nvidia-graphics-drivers packages from experimental.
Andreas
Package: libglvnd0
Version: 0.2.999+git2
Severity: normal
Dear Maintainer,
During installing the Nvidia Geforce driver version 384.90 the
following error occurs:
"An incomplete installation of libglvnd was found. Do you want to
install a full copy of libglvnd? This will overwrite any exist
14 matches
Mail list logo