[08:33] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2882](https://github.com/MirServer/mir/pull/2882): [mir-libs] bump timeout
[09:39] <Saviq> alan_g hey, `candidate` is now ready for 2.13.0 for you :)
[09:45] <alan_g[m]> https://forum.snapcraft.io/t/call-for-testing-ubuntu-frame-mir-test-tools-mir-kiosk-egmde-mir-2-13-0-update/34522
[09:48] <Saviq> alan_g you'll need to fix the anchor on forum.s.i, I added a ToC to the page last week and modified the anchors to be consistent with other pages:
[09:48] <Saviq> https://mir-server.io/docs/how-to-configure-ubuntu-frame-for-multiple-outputs#heading--ubuntu-frame-98-mir2-13-0
[09:48] <Saviq> (I've already fixed the link on discourse.u.c)
[09:49] <Saviq> (I really hope those will get automated at some point…)
[09:49] <Saviq> *those - the ToC and heading anchors
[09:50] <alan_g[m]> :done:
[10:45] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [pull request #2812](https://github.com/MirServer/mir/pull/2812): Enable bypass by default
[10:49] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [pull request #2835](https://github.com/MirServer/mir/pull/2835): Make sure to call connection_is_allowed on xwayland sessions
[11:42] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2883](https://github.com/MirServer/mir/pull/2883): Drop legacy workaround
[11:42] -GitHub[m]:#mir-server-  
[11:42] -GitHub[m]:#mir-server- > I remember having an old laptop (circa 2006) that needed the `MIR_DRM_CURSOR_64x64` workaround. But I don't think it we've encountered a need for this for a long time
[16:06] <Saviq> Talk later \o
[16:40]  * sophie-w sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/e29e968e09f81165be74fae15106af8f618004a7
[16:40] <sophie-w>  * ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/a53f883430b4c1803526a53225fe83473adb9262>)
[16:40] <sophie-w> (I'm on intel)
[16:41] <alan_g[m]> Just install mesa-core22 and connect graphics-core22
[16:41] <alan_g[m]> We don't have global autoconnect set up yet
[16:46] <sophie-w> > connect graphics-core22
[16:46] <sophie-w> What does this mean specifically? Neither `sudo snap connect mesa-core22:graphics-core22` nor `sudo snap connect confined-shell:graphics-core22` work
[16:47] <alan_g[m]> snap connect confined-shell:graphics-core22 mesa-core22
[17:11] <Saviq> Oh I should fix that TODO, shouldn't I.
[21:27] <alan_g[m]> Someone should