mirror of
https://github.com/lutris/lutris.git
synced 2026-07-30 15:15:56 -04:00
116916c060
Jammy's WebKit2GTK 4.1 point release (2.42) has a bug that kills the WebKitWebProcess after one input event on the ZOOM Platform login page; once the renderer dies the dialog freezes, stops repainting, and accepts no further input. The dialog frame itself stays alive so it wasn't obvious from the outside — the page just seemed to hang. Non-AppImage runs weren't affected because they load the host's newer WebKit. Noble's 2.44+ point release fixes it. Bump the base image, update apt package names where they've been renamed in the t64 transition (libfuse2 → libfuse2t64, libgnome-desktop-3-19 → libgnome-desktop-3-20t64), switch to apt's meson (Noble's is current enough for meson-python), and pass --break-system-packages to pip since Noble's system Python is PEP 668-managed. Trade-off: glibc floor moves from 2.35 to 2.39, so the AppImage stops running on hosts older than roughly 2024 distros (Ubuntu 22.04 and Debian 12 are too old). Documented in the Dockerfile header. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>