[03:23] <tcuthbert> \o
[03:56] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [pull request #2448](https://github.com/MirServer/mir/pull/2448): Wayland platform size from configure
[03:56] -GitHub[m]:#mir-server-  
[03:56] -GitHub[m]:#mir-server- > Fixes #2447, based on top of #2437 (thus draft PR until that lands). This is also a step towards being able to run the Wayland platform in windowed mode.
[05:32] <Saviq> o/ tcuthbert
[05:32] <Saviq> We are now logged!
[06:14] <RAOF> > <@saviq:matrix.org> o/ tcuthbert
[06:14] <RAOF> > 
[06:14] <RAOF> > We are now logged!
[06:14] <RAOF> Logged?
[06:33] <Saviq> <RAOF> "> <@saviq:matrix.org> o/ tcuthbe..." <- https://irclogs.ubuntu.com/2022/06/01/%23mir-server.html
[06:35] <RAOF> Ah, right. I guess that might be useful for people without Matrix accounts.
[06:38] <RAOF> At least until guest accounts get sorted out.
[08:14] <Saviq> Mo'in
[08:34] <alan_g[m]> @Saviq, FYI I'm going to push the USN based rebuild of mir-test-tools (& ubuntu-frame-osk when it has built) to candidate
[08:42] <Saviq> <alan_g[m]> "@Saviq, FYI I'm going to push..." <- :ack:. I will try and find out if there's an ETA on when that stops…
[08:43] <alan_g> Saviq, this one was genuine: `libcups2`
[08:44] <Saviq> Right, yes. By "that" I meant the spurious ones for m-t-t
[08:44] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq edited [pull request #2448](https://github.com/MirServer/mir/pull/2448): Wayland platform size from configure
[08:45] <Saviq> > <@github:maunium.net> **[MirServer/mir]** wmww opened [pull request #2448](https://github.com/MirServer/mir/pull/2448): Wayland platform size from configure
[08:45] <Saviq> >  
[08:45] <Saviq> > > Fixes #2447, based on top of #2437 (thus draft PR until that lands). This is also a step towards being able to run the Wayland platform in windowed mode.
[08:45] <Saviq> sophie you can base things to "prerequisite" PRs these days - bors will DTRT and retarget before merging. (I've done that for this one)
[08:48] <Saviq> Saviq: This way you can see divergence between the prerequisite and tip - where there's a conflict now
[08:52] <Saviq> I wonder if we should reverse this, have "proper" in master, but patch in CI appropriately when uploading for older releases?
[08:52] <Saviq> This way we could get to where devel PPA is the same as archive?
[08:53] <Saviq> Hmm threads are meh when you reply to one that's a way up in history. Did anyone other than RAOF (he/his) see that I just replied to https://matrix.to/#/!BLqVNwVsifZjueHWjt:libera.chat/$iNFe6dvZ23lDNgnJ7OFmlMog_6DwpLc981qxdNwNVxs?via=libera.chat&via=matrix.org&via=cooperteam.net ?
[08:55] <RAOF> Saviq: You do need to keep an eye on the “threads” pane, yeah.
[08:55] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** SomeDevWeb opened [issue #66](https://github.com/MirServer/ubuntu-frame/issues/66): How to EXIT the locked screen?
[08:55] -GitHub[m]:#mir-server-  
[08:55] -GitHub[m]:#mir-server- > Sorry, it might be a silly question, but I didn't find any info about this. So I installed Ubuntu 22 Desktop (minimal config) and I successfully installed ubuntu-frame and mir server. When I ran "**snap set ubuntu-frame daemon=true**" the screen locked and I have no idea how to get out of it. I restarted it and, as it should do, it comes back to the locked screen, but I didn;t even get to change the URL or anything else, it's just the
[08:55] -GitHub[m]:#mir-server- grey screen. Usually, the kiosk locking apps have a key combination or a touch sequence to show an admin password. How does ubuntu-frame work in that respect? Thank you so much!
[08:59] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq added documentation to [issue #66](https://github.com/MirServer/ubuntu-frame/issues/66): How to EXIT the locked screen?
[09:00] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** Saviq opened [issue #67](https://github.com/MirServer/ubuntu-frame/issues/67): Optionally disable Ctrl+Alt+F* VT switching... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/3e914daa9c4f717c76eee01a000b426610cd093a)
[09:03] <Saviq> <RAOF> "You do need to keep an eye on..." <- I've added feedback about this, and about how the IRC bridge handles threads (i.e. doesn't, at all).
[09:05] <Saviq> Compared to normal replies, which it gives too much context for, IMO. But I suppose if it doesn't quote the whole message being replied to, those on IRC will easily get confused.
[09:14] <RAOF> Yeah, I'm not really sure how you'd do it better; IRC is just not technically capable of rendering that information in a pleasing way.
[09:15] <Saviq> I suppose it's just something to keep in mind - until you change contexts, don't reply. Threads could meaningfully have that treatment in the IRC bridge
[09:17] <Saviq> Same with editing, better use "*correction" than editing in Matrix, as that will show the whole message after editing on IRC
[09:59] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths added enhancement to [issue #67](https://github.com/MirServer/ubuntu-frame/issues/67): Optionally disable Ctrl+Alt+F* VT switching
[10:50] -GitHub[m]:#mir-server- **[MirServer/ubuntu-frame]** AlanGriffiths closed [issue #66](https://github.com/MirServer/ubuntu-frame/issues/66): How to EXIT the locked screen?
[11:34] <RAOF> There's a meta-question here, of course, which is how much we care about the IRC experience.
[13:06] <Saviq> <GitHub[m]> "**[MirServer/ubuntu-frame..." <- I wanted to keep this as a documentation task…
[13:07] <Saviq> Oh well, moved it to "Todo" in the project, looks like the two states are not tightly bound
[13:44] <alan_g[m]> <Saviq> "I wanted to keep this as a..." <- _You_ can open it if that is important. (I felt we were in danger of remaining off topic)
[13:46] <Saviq> Yeah you're quite right, it was going in a weird direction. The line item in the project is good enough.
=== alan_g_ is now known as alan_g
[13:47] <alan_g> But I do wonder if there was an interesting use case hidden in there somewhere
[13:51]  * alan_g wonders if there is a nice Matrix client for Linux. FluffyChat snap works, but not well and Element snap doesn't work (on Wayland at least)
[13:54] <Saviq> I think the deb worked for me: https://element.io/get-started#linux-details
[13:54] <Saviq> The snap is only revision 2, so not surprising it's not polished…
[13:55] <alan_g> Yeah, not keen on adding PPAs, they get out of hand
[13:56] <Saviq> https://snapcraft.io/fractal maybe?
[13:57] <Saviq> Not very up to date, but I know the publisher ;)
[14:01] <alan_g> `(fractal:49897): Gtk-WARNING **: 15:00:37.771: cannot open display: :0`
[14:03] <Saviq> `env -u DISPLAY fractal` worked here
[14:03] <alan_g[m]> `snap connect fractal:wayland` works here
[14:04] <Saviq> Right, I have all my other wayland slots disabled at the moment, so got autoconnected
[14:05] <Saviq> Seems legit. I will try and stick to it for some time. Much more responsive than the web app.
[14:19] <alan_g[m]> Saviq looks like you have the changes you requested:https://github.com/MirServer/mir/pull/2441
[14:21] <Saviq> Right, I was sleeping on that - whether we should prune it even more (`bors.toml`, `tools/ppa-upload.py` etc.)
[14:23] <alan_g[m]> That doesn't need to be this PR
[14:51] <grayson-g[m]> alan_g: when you have a minute, can you take a look at `TextInputV1::focus_on()` (notably the `deactivate(nullptr)`) and the hack I've got in `TextInputV1::show_input_panel()`. Long story short, it seems like Electron wants to call that instead of `commit_state()`, but I'm not sure what to use as the serial so for now I just have it always set as 0. Can you think of a time when this would be a problem, and if this hack is needed, how
[14:51] <grayson-g[m]> would you recommend documenting it?
[14:54] <alan_g[m]> > alan_g: when you have a minute, can you take a look at `TextInputV1::focus_on()` (notably the `deactivate(nullptr)`) and the hack I've got in `TextInputV1::show_input_panel()`. Long story short, it seems like Electron wants to call that instead of `commit_state()`, but I'm not sure what to use as the serial so for now I just have it always set as 0. Can you think of a time when this would be a problem, and if this hack is needed, how
[14:54] <alan_g[m]> would you recommend documenting it?
[14:54] <alan_g[m]> Have you discussed with @sophie? I've not looked at this protocol extension in any detail to know what's expected
[14:55] <grayson-g[m]> > <@alan_g:matrix.org> > alan_g: when you have a minute, can you take a look at `TextInputV1::focus_on()` (notably the `deactivate(nullptr)`) and the hack I've got in `TextInputV1::show_input_panel()`. Long story short, it seems like Electron wants to call that instead of `commit_state()`, but I'm not sure what... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/c47ee9105d377975ddb025487b810de2706a925d)
[16:44] <sophie-w> Where does the style guide live on the web now? https://mir-server.io/doc/cppguide 400s
[16:46] <Saviq> > Where does the style guide live on the web now? https://mir-server.io/doc/cppguide 400s
[16:46] <Saviq> That's a bug.
[16:48] <Saviq> I've filed https://github.com/canonical-web-and-design/mir-server.io/issues/176 and will follow up with the web team
[16:49] <Saviq> > @Saviq, FYI I'm going to push the USN based rebuild of mir-test-tools (& ubuntu-frame-osk when it has built) to candidate
[16:49] <Saviq> The incoming mir-test-tools rebuild should also get that treatment and will hopefully be the last one in a while.
[16:50] <alan_g[m]> > > @Saviq, FYI I'm going to push the USN based rebuild of mir-test-tools (& ubuntu-frame-osk when it has built) to candidate
[16:50] <alan_g[m]> > 
[16:50] <alan_g[m]> > The incoming mir-test-tools rebuild should also get that treatment and will hopefully be the last one in a while.
[16:50] <alan_g[m]> I'll leave that to you to deal with. (I only have a minutes left before the "weekend"
[16:51] <Saviq> Ofc, didn't mean to put that on you :)
[16:51] <alan_g[m]> Talking of the docs, did we update for 2.8?
[16:52]  * Saviq adds an item into the release protocol review
[16:57] <Saviq> https://github.com/canonical-web-and-design/mir-server.io/pull/177
[16:58] <alan_g[m]> One would think there could be tooling to pick up dead links within the site
[17:06] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [pull request #2211](https://github.com/MirServer/mir/pull/2211): Only call extension filter once per app per extension
[17:30] -GitHub[m]:#mir-server- **[MirServer/mir]** graysonguarino marked [pull request #2443](https://github.com/MirServer/mir/pull/2443): Fix OSK on Electron apps as ready for review
[21:40] -GitHub[m]:#mir-server- **[MirServer/mir]** wmww opened [pull request #2449](https://github.com/MirServer/mir/pull/2449): Make all death tests threadsafe... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/fe8f22bdd0fdff3a91f684f5d2549677975f7837)
[21:42] <sophie-w> RAOF (he/his): FYI in our sync today we decided to standardize on passing shared pointers by value with std::move() in new code
[21:52] <sophie-w> grayson-g: if you're not too busy, https://github.com/MirServer/mir/pull/2437 could use a review and a bors if it looks good
[21:53] <sophie-w> Don't mind the massive diff size, it's mostly generated code that can be ignored
[21:55] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2439](https://github.com/MirServer/mir/pull/2439): Wayland platform: improve failed to connect error
[23:50] <RAOF> New plan: go inside and wait for tradies, so I don't need to keep the doors open!