The crash (bug 2062146) is now awkwardly entangled with this bug. It occurs at the same time as, or usually instead of corruption. Bisected in Mesa:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033#note_2385595 Prior to that regression, I still believe the corruption probably started around: https://github.com/WebKit/WebKit/commit/8b0ce3683045d93cd365e91a4299f7e9babfc126 If you need a workaround for both issues then the best I have found is environment: WEBKIT_DMABUF_RENDERER_FORCE_SHM=1 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11033 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp