Thank you for the bug report. It seems like a fix worth cherrypicking but could you maybe give an example of impact the issue has which is user visible? It would help especially for a stable update to have a testcase to verify the fix and to justify the importance. If it's not impacting anyone in a visible fashion then maybe it's not such an issue
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1966334 Title: GLVND: Set current thread state to NULL in teardown Status in libglvnd package in Ubuntu: Confirmed Bug description: A new fix has been merged into the libglvnd repo at https://gitlab.freedesktop.org/glvnd/libglvnd This change fixes an issue where if eglReleaseThread gets externally called after the EGL destructor, a double free occurs due to the threadState that eglReleaseThread checks is not null being not null despite being freed by the destuctor. The change makes the threadState null in the destructor to fix this. Can this make it into the libs in 20.04 LTS? Source package where the issue is encountered: https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1966334/+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
