Fonts not working in Ubuntu 14.04

[cjb]

Hi! Thanks for an amazing code contribution.

Fonts aren't working here in latest Chrome or Firefox, screenshot below:

There are some WebGL errors on the console:

Can't find symbol 'glXCreateContextAttribsARB'.
"initnew: 559" fn.js:614
Error: WebGL: enableVertexAttribArray: index -1 is invalid. That probably comes from a getAttribLocation() call, where this return value -1 means that the passed name didn't correspond to an active attribute in the specified program. gl.js:33
Error: WebGL: vertexAttribPointer: index -1 is invalid. That probably comes from a getAttribLocation() call, where this return value -1 means that the passed name didn't correspond to an active attribute in the specified program. gl.js:76

In case it matters, I'm using a very high DPI screen (260 dpi; 3200x1800 at 14").

[rikarends]

Hi, yeah apparently texturing particles properly is one of those cases where GL just fails bigtime, in this case its just garbling texture coordinates probably, i tried everything to fix it but failed. I use textured particles because they are 6 times smaller in typed array interaction than quads (1 vertex instead of six). Problem is this is a lot of work to fix since it changes how the text rendering, and shaders operates quite significantly. Im doing a new kind of text rendering engine now, on which i will rebuild a trace-like UI. so who knows. In the mean time i cant really help you.

[rikarends]

Although your case might be a different bug, i dont know. the garbling looks slightly different than ive seen before. Maybe its the dpi-thing. TraceGL was also an experiment in a radically different codestyle for me, which i have since abandoned (which is: one character is enough for everything!) and the shader compiler in there i have also since completely redone properly since its one ginormous hack and not really nice to fix these kinds of things in. You could try to hack the textshaders and see whatsup.. or try to dump the font texture to screen and see if thats screwed.

[donpark]

Same problem occurs on Chrome (v38) running on Yosemite.
Firefox (v33) works fine however.