For what it's worth, I installed libepoxy0 (1.3.1-1ubuntu1) from zesty manually by downloading the right deb for my architecture (https://packages.ubuntu.com/zesty/libs/libepoxy0), and then installing with "dpkg -i". It seems that the newer package in zesty has a fix for the bug you referenced.
This cleared up the segfaults. So, I'm not sure the ldconfig issues you mentioned are a problem in their own right; at least, they don't manifest as a crash on my setup.
I'm not an Ubuntu developer, but I'm trying to figure out how to get them to basically get the zesty package (with the null-pointer dereference fix) into 16.04 LTS. I e-mailed the bug team, hopefully they can get the ball rolling.
For what it's worth, I installed libepoxy0 (1.3.1-1ubuntu1) from zesty manually by downloading the right deb for my architecture (https:/ /packages. ubuntu. com/zesty/ libs/libepoxy0), and then installing with "dpkg -i". It seems that the newer package in zesty has a fix for the bug you referenced.
This cleared up the segfaults. So, I'm not sure the ldconfig issues you mentioned are a problem in their own right; at least, they don't manifest as a crash on my setup.
I'm not an Ubuntu developer, but I'm trying to figure out how to get them to basically get the zesty package (with the null-pointer dereference fix) into 16.04 LTS. I e-mailed the bug team, hopefully they can get the ball rolling.