[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#879583: libgl1-mesa-glx: Couldn't open libGL.so.1, undefined symbol _giapi_tls_Current



Control: tags -1 moreinfo

On Mon, Oct 23, 2017 at 05:45:56AM +0000, Paul Lou wrote:
> Package: libgl1-mesa-glx
> Version: 17.2.2-1
> Severity: important
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
> Performed aptitude upgrade today, upgraded libgl1-mesa-glx from
> 13.0.6-1+b2, and rebooted.
> 
>    * What was the outcome of this action?
> Now xinit fails to start due to error
> xf86EnableIOPorts: failed to set IOPL for I/O (operation not permitted)
> Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined
> symbol: _giapi_tls_Current
> xinit: giving up
> 
> Another computer with very similar setup, except with nVidia graphics card,
> failed to upgrade today from 13.0.6-1 to 17.2.2-1 (due to dependency issues
> with libegl1-glvnd-nvidia [375.82-5], libgl1-glvnd-nvidia-glx [375.82-5],
> libglx0-glvnd-nvidia[375.82-5]) does not have the reported issues.
> 
> On the affected computer, `ldd -r /usr/lib/x86_64-linux-gnu/libGL.so.1`
> returns the same undefined symbol error.
> 
>    * What outcome did you expect instead?
> Successfully launch startx.
> 

Is this still an issue? I think this was fixed in a newer version of
nvidia-graphics-drivers.

Thanks,
Andreas


Reply to: