[00:50] -GitHub[m]:#mir-server- **[MirServer/mir]** graysonguarino marked [pull request #2646](https://github.com/MirServer/mir/pull/2646): Expose wait features as ready for review
[02:44] <RAOF> Woo! Now with a drivers licence that hasn't been exposed by someone enumerating an unauthenticated API endpoint of my telco!
[11:05] <Saviq> Hey dot-tobias - I can't find anything documented, with WPE Cog, is there any way to control its window size / state (e.g. fullscreen, on which output), or is that all left to the compositor?
[11:25] <Saviq> Now this is fun. I caught the SIGTERM in gdb (wanted to confirm where it came from), unfortunately I managed to `continue` through a previous Enter press.
[11:25] <Saviq> Anyway, because I set it to `nopass`, Miriway didn't exit. But if I switch to its VT, only the internal display does. The external one is stuck with the text console I switched from o.O (without the caret blinking).
[11:26] <alan_g[m]> Saviq: Anyway, because I set it to `nopass`, Miriway didn't exit. But if I switch to its VT, only the internal display does. The external one is stuck with the text console I switched from o.O (without the caret blinking).
[11:26] <alan_g[m]> Yeah, the CRTC is actually needed to composite to the device. So ignoring the error doesn't actually help
[14:06] <Saviq> alan_g: got a trapped SIGTERM, anything you'd be interested in?
[14:07] <alan_g[m]> No, unless the stack trace is different to the one I have: https://github.com/MirServer/mir/issues/2661#issuecomment-1262524582
[14:12] <Saviq> I got 114 threads… none of them like that.
[14:12] <Saviq> I've collected the backtraces, but will also add the breakpoint, as I've only caught the signal and that might've been too late
[14:13] <alan_g[m]> Oh, right yeah. By that time the thread will probably be dead.
[14:14] <alan_g[m]> The question is really how we get to this state...
[15:33] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned AlanGriffiths to [issue #2661](https://github.com/MirServer/mir/issues/2661): Mir sometimes shuts down when moving to a different TTY when logind-driven
[15:45] <Saviq> Soft EOW here o/
[16:17] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths drafted [pull request #2684](https://github.com/MirServer/mir/pull/2684): Deal with confused state of KMS outputs better
[16:17] -GitHub[m]:#mir-server-  
[16:17] -GitHub[m]:#mir-server- > Fixes: #2661
[16:22] <alan_g[m]> Saviq I have a POC for fixing the SIGTERM :this:, but still have to search for a way to avoid getting into this mess
[16:50] <grayson-g[m]> For the documentation on Frame Diagnostic, should I only focus  on documenting use within the Snap? I can't imagine there's any practical use to running it unconfined besides development and I feel it would just bloat the docs.
[16:58] <alan_g[m]> Yes, it is "how to use from your snap"
[17:00] <alan_g[m]> You can use https://github.com/AlanGriffiths/ubuntu-frame-diagnostic as an example
[17:01] <Saviq> IMO there's value in mentioning how to write _from_ outside a snap (e.g. directly from a systemd unit), but Frame itself doesn't really exist outside of snap
[17:42] <grayson-g[m]> One accidental keypress later and I've posted a wildly incomplete tutorial to Discourse 😵‍💫 If only there was a way to temporarily hide posts!
[17:43] <Saviq> Can you not edit/delete?
[17:43] <Saviq> I can help, if you need
[17:45] <grayson-g[m]> I can edit/delete! I just like using the editor to see my formatting and wish it wasn't so easy to post incoherency to the public.
[17:46] <Saviq> https://stackedit.io/ may help to draft
[17:46] <grayson-g[m]> Saviq: This is perfect! Thank you (:
[19:59] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2683](https://github.com/MirServer/mir/pull/2683): XWaylandClipboardSource: do not clear source just before a new one is set
[19:59] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] closed [issue #2677](https://github.com/MirServer/mir/issues/2677): In CLion cut & paste only works up to the last `\n` in the source text
[20:35]  * grayson-g[m] posted a file: (5KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/NRypEOklMrTjbNpEmaUMqoDC/Ubuntu%20Frame%20Tutorial.html >
[20:36] <grayson-g[m]> Here's a draft of the Ubuntu Frame Diagnostic tutorial. I'll avoid posting to Discourse until the next Frame release.
[20:41] <grayson-g[m]> * Frame release. (I've swapped "color" for "colour" since this draft 😉)