Bug 1418103 - mesa-13.0.3-6.fc25 from "updates-testing" breaks bumblebee
Summary: mesa-13.0.3-6.fc25 from "updates-testing" breaks bumblebee
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 25
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-31 21:22 UTC by Gary Gatling
Modified: 2017-02-03 10:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2017-02-03 10:36:52 UTC
Type: Bug

Attachments (Terms of Use)

Description Gary Gatling 2017-01-31 21:22:42 UTC
Description of problem:
mesa-13.0.3-6.fc25 from "updates-testing" breaks bumblebee on my test machine.

Version-Release number of selected component (if applicable):

How reproducible:

Install system on nvidia optimus hardware and add third party repo as described here:


Steps to Reproduce:
1. test primus on command line with 13.0.3-5 with opengl application like glxgears with optirun -b primus or primusrun
2. update to mesa 13.0.3-6 via updates testing.
3. primus can no longer find the required opengl libraries (it seems) after the update and the window will not open.

Actual results:


Expected results:

Should open a window with spinning gears in it using nvidia openGL.

Additional info:

I believe the problems may be caused by libglvnd. I tried re-compiling primus with the newer mesa*-devel packages but it did not seem to make any difference unfortunately.

Also there is a message on the command line about

/usr/lib64/libGL.so.1: undefined symbol: _glapi_tls_Current

Any ideas about how I can work around this problem? 

I can provide any further logs that might be needed. Thanks.

Comment 1 Hans de Goede 2017-02-01 08:28:44 UTC

Can you please contact the upstream bumblebee / primus developers about this ? Using glvnd actually should make things easier for bumlebee since the nvidia binary driver has been using glvnd for a while now.

I guess that some script is playing ldconfig tricks, and that those are no longer necessary now (and are potentially actually causing problems by injecting e.g. an older libglvnd-libGL into the library path).



Comment 2 Gary Gatling 2017-02-02 14:36:26 UTC
I have opened issue 193 on github.com. Thanks.


Comment 3 Hans de Goede 2017-02-03 10:36:52 UTC
Ok, so lets further track and resolve this upstream.

Note You need to log in before you can comment on or make changes to this bug.