Kai Mühlbauer

@mateo4778 Just checking in. Is this issue still relevant?

@asteppke Thanks for bringing this up here. I can't say much about the `test_frame_buffer_helper` problem. But for the `pillow` problem we should definitely skip those tests if pillow isn't installed.

@asteppke I've created a new issue for the `pillow`-part, so we can concentrate on the frame buffer problem here.

How did you install VisPy? Seems, that `fontconfig` is not installed.

OK. Can you check with your system's package manager if `fontconfig` is installed in your system? If not, check if installation of `fontconfig` will fix it.

What system are you on? You would use your system package manager (eg. apt, zypper etc. depending on system) and install `fontconfig` through this.

@djhoese @larsoner This seems to be a problem for users. `fontconfig` isn't mentioned in the docs, if it is missing, users will get these notifications. But we also have this...

@larsoner Thanks for looking into this. But glumpy doesn't use `fontconfig`.

@djhoese Wasn't meant to blame vispy doing something wrong. But currently we do not know, if `fontconfig` is really missing in the OP's system or if vispy just isn't finding...

Does this have a solution yet, @djhoese ?