[06:35] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** cluemaster-robert opened [issue #130](https://github.com/MirServer/ubuntu-frame/issues/130): Latest Version 95-mir2.12.1 released on 8 March 2023. just bricked all my customer tv displays... (full message at ) [06:57] -GitHub[m]:#mir-server- **[MirServer/wlcs]** RAOF edited [issue #278](https://github.com/MirServer/wlcs/issues/278): WLCS depends on compositor-specific behaviour [06:57] -GitHub[m]:#mir-server- **[MirServer/wlcs]** RAOF closed [issue #280](https://github.com/MirServer/wlcs/issues/280): WLCS assumes that clicking outside a non-grabbing xdg_popup dismisses the popup tree [07:52] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq added bug to [issue #130](https://github.com/MirServer/ubuntu-frame/issues/130): Latest Version 95-mir2.12.1 released on 8 March 2023. just bricked all my customer tv displays [09:24] "Saviq I'm still tweaking, but..." <- Saviq I think I've done enough for a PoC here. WDYT? [09:26] I'll look [12:35] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq edited [issue #130](https://github.com/MirServer/ubuntu-frame/issues/130): Frame racing on boot with clients using incomplete `wayland-launch` [13:51] alan_g off the top of your head, any idea what could be missing that `eglinfo` goes like this?... (full message at ) [14:00] Nvm, got it [14:01] WFM [14:46] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths opened [pull request #131](https://github.com/MirServer/ubuntu-frame/pull/131): Unblock clients with a racy `wayland-launch` script [14:46] -GitHub[m]:#mir-server- [14:46] -GitHub[m]:#mir-server- > Fixes: #130 [15:00] alan_g so for graphics-core22 cleanup… my thinking is to provide source for a part that would include a cleanup script… but can't decide on where to get the list to clean up from. I could use the build-snap approach you worked out, or we could maintain list(s) of files along with the cleanup script. [15:00] The latter would allow us to a) review what gets cleaned up and b) clean up more than is primed in the snap c) include multiple providers' file lists (like Nvidia). [15:00] WDYT? [15:06] I think there is the potential for problems with both approaches, but I don't have a good idea. So I have a slight preference for the build snap approach as it doesn't require maintaining lists. [15:08] Hurmf.... (full message at ) [15:21] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths marked [pull request #131](https://github.com/MirServer/ubuntu-frame/pull/131): Unblock clients with a racy `wayland-launch` script as ready for review [16:34] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq assigned to [pull request #131](https://github.com/MirServer/ubuntu-frame/pull/131): Unblock clients with a racy `wayland-launch` script [16:34] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq assigned AlanGriffiths to [issue #130](https://github.com/MirServer/ubuntu-frame/issues/130): Frame racing on boot with clients using incomplete `wayland-launch` [16:36] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] closed [pull request #131](https://github.com/MirServer/ubuntu-frame/pull/131): [Merged by Bors] - Unblock clients with a racy `wayland-launch` script [16:36] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] edited [pull request #131](https://github.com/MirServer/ubuntu-frame/pull/131): [Merged by Bors] - Unblock clients with a racy `wayland-launch` script [16:36] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** bors[bot] closed [issue #130](https://github.com/MirServer/ubuntu-frame/issues/130): Frame racing on boot with clients using incomplete `wayland-launch` [18:15] Gotcha!... (full message at ) [18:16] We never had eglstream working between snaps, did we. [19:18] Time o/ [19:22] But:... (full message at )