[09:14] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths requested a review from RAOF for [pull request #2614](https://github.com/MirServer/mir/pull/2614): Fix rendering that spans outputs [10:05] * Saviq on a kernel bug (HDMI output unstable) tracking spree this morning… [10:05] This is on your new fangled kit? [10:06] Yeah, external monitor goes off and on multiple times a minute [10:06] Until a kernel upgrade (a big one, 5.15 → 5.19 for some reason) it was maybe once an hour, and I blamed cables / HW. But the fact that kernel influences it, and other seeing it, made me reconsider. [10:11] *others [10:44] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2623](https://github.com/MirServer/mir/pull/2623): Modernize touch events [12:44] Yay. So installing 22.10 from a USB stick onto a USB drive still zeroes out the grub configuration on the internal drive. Of course. [12:44] And of course recovery with a ZFS encrypted setup is trivial. Except not. [13:21] Saviq, when you need a break from unbreaking your kit, do you want to re-review https://github.com/MirServer/mir/pull/2611? [13:22] ...and I hope testing my Mir compositing hacks wasn't the trigger for this [13:33] No no, it was https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988989 [13:33] And I did unbreak myself already, was just whining [13:34] I still need to test your two PRs dealing with messed up buffers, together, but will re-review the above first [13:36] My first PR just awaits blessing by Chris, the second is just a BFI hack to prove we're looking at the right codepath [13:36] But it might need more F [13:54] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [pull request #2591](https://github.com/MirServer/mir/pull/2591): Don't try to calibrate timestamps [14:25] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2602](https://github.com/MirServer/mir/pull/2602): Simplify timestamp calibration [14:59] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] closed [issue #2607](https://github.com/MirServer/mir/issues/2607): Building Mir modifies the logind source [14:59] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2611](https://github.com/MirServer/mir/pull/2611): Fix #2607 modification of logind source [16:13] sophie so e.g. this is what you would expect to not work? [16:13] ``` [16:13] env -u WAYLAND_DISPLAY gnome-screenshot [16:13] ``` [16:14] Seems to work on Mutter on 22.10 at least [16:14] Unless it then assumes `wayland-0` 🤷‍♂️ [16:14] I generally set `WAYLAND_DISPLAY=no`, but I don't think gnome-screenshot goes through Wayland at all [16:14] Saviq `GDK_BACKEND=x11` [16:15] I think GNOME has a D-Bus API for screenshots, and that might be why it's working [16:15] But as Sophie says, it probably uses dbus [16:15] It does trigger XWayland at least [16:15] Try something like `scrot` [16:15] But yeah doubt it's actually grabbing through X [16:16] Yeah `scrot`'s all black [16:16] (tested again and scrot doesn't work for me on Sway) [16:21] OK, folks. I was wrong and Sophie was right: I accept it doesn't work [16:21] (But I still don't care) [16:22] I'm glad it wasn't a thing anyone was trying to do in the first place (at least this time around) [16:26] Ok that's time here o/ [17:01] And time here also o/ [19:15] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [issue #2624](https://github.com/MirServer/mir/issues/2624): mgx::X11Window::r_mask used uninitialized [19:15] -GitHub[m]:#mir-server- [19:15] -GitHub[m]:#mir-server- > It is used, but it is never set. Spotted in Valgrind. [21:19] Does anyone know how to make wlcs.asan work? I've tried a bunch of things and haven't made any progress [21:20] Or how to run wlcs in valgrind (I'm getting `Valgrind: debuginfo reader: Possibly corrupted debuginfo file.`) [23:28] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2614](https://github.com/MirServer/mir/pull/2614): Fix rendering that spans outputs [23:29] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] closed [issue #1753](https://github.com/MirServer/mir/issues/1753): Incorrect rendering when a surface spans multiple outputs