Bug#878948:

2017-10-23 Thread Javi Legido 
I can confirm the issue and the fix, installing libglvnd0 package.

Cheers.

Javier

Processed: Re: Bug#878948: Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

2017-10-18 Thread Debian Bug Tracking System 
Processing control commands:

> reassign -1 libglvnd0-nvidia
Bug #878948 [libgl1-mesa-glx] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
Bug reassigned from package 'libgl1-mesa-glx' to 'libglvnd0-nvidia'.
No longer marked as found in versions mesa/17.2.2-1.
Ignoring request to alter fixed versions of bug #878948 to the same values 
previously set
> forcemerge 878968 -1
Bug #878968 [libglvnd0-nvidia] libglvnd0-nvidia: undefined symbol: 
_glapi_tls_Current makes system unusable
Bug #878948 [libglvnd0-nvidia] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
Severity set to 'critical' from 'serious'
Marked as found in versions nvidia-graphics-drivers/375.82-5.
Merged 878948 878968

-- 
878948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878948
878968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#878948: Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

2017-10-18 Thread Sven Joachim 
Control: reassign -1 libglvnd0-nvidia
Control: forcemerge 878968 -1

On 2017-10-18 00:31 +0200, Arturo Borrero Gonzalez wrote:

> Package: libgl1-mesa-glx
> Version: 13.0.6-1+b2
> Severity: serious
>
> Dear maintainers,
>
> thanks for your work with the X stack, it's really appreciated :-)
>
> I had today a very disapointing experience with Debian.
> I did the daily aptitude update && aptitude upgrade of testing buster
> in a laptop (XFCE) to find that the system would show no graphical interface
> no longer. In fact, the behaviour is a complete freeze of the machine.
>
> This is what I did to point to libgl1-mesa-glx as the main problem.
>
> 1) I upgraded a bunch of packages, usual daily update:
>
> --- 8< ---
> Aptitude 0.8.9: log report
> Tue, Oct 17 2017 19:26:20 +0200
>
>   IMPORTANT: this log only lists intended actions; actions which fail
>   due to dpkg problems may not be completed.
>
> Will install 50 packages, and remove 1 packages.
> 27.1 MB of disk space will be used
> 
> [REMOVE, NOT USED] libllvm3.9:amd64 1:3.9.1-10
> [INSTALL, DEPENDENCIES] libegl-mesa0:amd64 17.2.2-1
> [INSTALL, DEPENDENCIES] libegl1:amd64 0.2.999+git20170802-5
> [INSTALL, DEPENDENCIES] libgl1:amd64 0.2.999+git20170802-5
> [INSTALL, DEPENDENCIES] libgles2:amd64 0.2.999+git20170802-5
> [INSTALL, DEPENDENCIES] libglvnd0-nvidia:amd64 375.82-5

This is the problem, why did aptitude not install the libglvnd0 package
instead?  The libglvnd0-nvidia package is hardly the right one if you
have a Radeon card.

Cheers,
   Sven

Bug#878948: merging with a duplicate bug

2017-10-18 Thread Lorenzo Pinelli 
Control: forcemerge -1 878851

Dear Arturo,

I think the problem is the one described in bug #878851

I'm therefore merging the two bugs.


Regards,
Lorenzo Pinelli

Bug#878948:

2017-10-17 Thread Sebastian Wyngaard 
I can also confirm encountering this bug on testing.

Downgrading the above-mentioned packages works for me too. Thanks!

Bug#878948:

2017-10-17 Thread Arturo Borrero Gonzalez 
Control: found -1 17.2.2-1