Xvfb fails with new mesa, results in ubiquity FTBFS

this bug is in libepoxy

https://bugzilla.redhat.com/show_bug.cgi?id=1395366

This bug was fixed in the package libepoxy - 1.3.1-1ubuntu1

---------------
libepoxy (1.3.1-1ubuntu1) zesty; urgency=medium

  * add-null-checks.diff: Fix gtk apps crashings on Xvfb. (LP: #1647600)

 -- Timo Aaltonen <email address hidden> Thu, 08 Dec 2016 14:49:13 +0200

I did a sync and rebased the above patch, would be nice to recheck it on artful

Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance!

can anybody please test my ppa?
I pushed no change rebuilds for ubiquity and the fixes for libepoxy there
https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa

I don't think this is needed for yakkety, since it won't get a new mesa backport, and is soon EOL anyway.

Hello Dimitri, or anyone else affected,

Accepted libepoxy into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libepoxy/1.3.1-1ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Ping, can anybody please verify this?

I can see that ubiquity now is building correctly, and nobody reported regressions so far

Get:333 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 libepoxy-dev amd64 1.3.1-1ubuntu0.16.04.1 [112 kB]
[...]
dh_md5sums
NO_PNG_PKG_MANGLE=1 dh_builddeb -- -Zxz
dpkg-deb: building package 'ubiquity' in '../ubiquity_2.21.63.3_amd64.deb'.
dpkg-deb: building package 'ubiquity-frontend-debconf' in '../ubiquity-frontend-debconf_2.21.63.3_amd64.deb'.
dpkg-deb: building package 'ubiquity-frontend-gtk' in '../ubiquity-frontend-gtk_2.21.63.3_amd64.deb'.
 dpkg-genchanges >../ubiquity_2.21.63.3_amd64.changes

seems good

This bug was fixed in the package libepoxy - 1.3.1-1ubuntu0.16.04.1

---------------
libepoxy (1.3.1-1ubuntu0.16.04.1) xenial; urgency=medium

  * Fix mesa crash (NPE) when no GL is available on X server
    LP: #1647600

 -- Gianfranco Costamagna <email address hidden> Tue, 06 Jun 2017 11:28:19 +0200

The verification of the Stable Release Update for libepoxy has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Hello Dimitri, or anyone else affected,

Accepted libepoxy into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libepoxy/1.3.1-1ubuntu1.17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

dpkg-deb: building package 'ubiquity-frontend-gtk' in '../ubiquity-frontend-gtk_17.04.9_amd64.deb'.
dpkg-deb: building package 'ubiquity' in '../ubiquity_17.04.9_amd64.deb'.
dpkg-deb: building package 'ubiquity-frontend-debconf' in '../ubiquity-frontend-debconf_17.04.9_amd64.deb'.

it builds fine!

This bug was fixed in the package libepoxy - 1.3.1-1ubuntu1.17.04.1

---------------
libepoxy (1.3.1-1ubuntu1.17.04.1) zesty; urgency=medium

  * Fix mesa crash (NPE) when no GL is available on X server
    LP: #1647600

 -- Gianfranco Costamagna <email address hidden> Tue, 06 Jun 2017 11:36:27 +0200

Anyone getting the segmentation fault bug in 17.10, would it still be libepoxy or could it be something else?

Was this fix applied in 17.10? I'm still getting Segmentation fault (core dumped) when trying to run a non-root synaptic (basically for browsing purposes only) in Wayland.

sorry, didn't realize I had already posted here...

https://bugs.launchpad.net/ubuntu/+source/ettercap/+bug/1713313

@Fadi