If only there was a way to force libepoxy to use GLESv2 (which it understands also) then it would not try to call the offending glGetStringi().
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1494240 Title: Xmir crashes immediately on startup using glamor on Nexus4 Status in libhybris package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Xmir crashes immediately on startup using glamor on Nexus4. glamor GL version: OpenGL ES 3.0 V@53.0 AU@ (CL@) ... glamor GLSL version: OpenGL ES GLSL ES 3.00 (EE) (EE) Backtrace: (EE) (EE) Segmentation fault at address 0x0 (EE) Fatal server error: (EE) Caught signal 11 (Segmentation fault). Server aborting (EE) The stack trace is lost. However the problem appears to be the glGetStringi() function. This function is new in GLESv3 and libepoxy only uses it because the GLES version is 3.0 on mako. However, libhybris fails to implement glGetStringi() and forward it to the driver correctly. At least that seems to be the problem. Our hybris GLESv2 is missing the function but the Android GLESv2 on the device has it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1494240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
