OSX: GL displays garble in both 2D and 3D

[Chad Parker]

On OSX 10.10, everything in the canvas is garbled. Compiled from git on 20160205. All of the GTK buttons and things are displayed fine, only the PCB canvas is garbled. In the console the following errors are thrown any time the canvas is redrawn:

No stencil bits available.
Cannot mask polygon holes or subcomposite layers
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned
No more stencil bits available, total of 0 already assigned

Screenshot: https://drive.google.com/file/d/0B3k6ZsL60zPuNzBHVU54QUs0X0k/view?usp=sharing

Compiling without GL, the canvas displays fine in 2D.

[Chad Parker (parker-charles)]

I'm not exactly sure what I did or when I fixed this, but I can no longer reproduce this. Seeing as how no one else has reported that this affects them, I'd say we should just close it.

[Bert Timmerman (bert-timmerman)]

Hi Chad,

There is another bug report, filed on 05-feb-2016, (https://bugs.launchpad.net/pcb/+bug/1542859) which might be affected by a faulty build process on OSX (due to whatever reason).

Could you please check if the above mentioned bug still exists.

Thanks and kind regards,

Bert Timmerman