[01:40] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF opened [issue #2612](https://github.com/MirServer/mir/issues/2612): No way to set *actual* clone mode... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/2aa4e578468025467c8acab852f27991bb66c4aa) [02:35] Pleased to announce wayland-debug has been given a new mode. (once the snap builds) you should be able to:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/09530f3f43827335dd7d41cbbd5180791b55ec44) [02:37] If you're not familiar with wayland-debug, the simplest way to see the new feature is by running: [02:37] ``` [02:37] wayland-debug -r weston-terminal [02:37] ``` [03:23] Hmm, the snap recipe doesn't seem to properly include my patched libwayland and lxd has broken itself since the last time I built a snap, that will have to wait. [07:11] I rebuilt mir-kiosk-kodi, egmde-c-d is rebuilt, but should we be sunsetting it in favour of Miriway? [07:11] Good day, too o/ [07:30] The day that starts with a 05:30 meeting is not the most productive day 😴 [07:32] We need to solve timezones somehow. [07:33] Grrr. You can't usefully snap a notification-daemon, because only non-snaps can send DBus to it. [07:38] That sounds weird? https://snapcraft.io/docs/dbus-interface [07:38] > The dbus interface provides a way for snaps to communicate over DBus. The snap providing the DBus service declares a slot with the well-known DBus name and which bus it uses. Snaps wanting to communicate with the providing snap’s service declare a plug for the providing snap. [07:46] "That sounds weird? https://..." <- +1 [07:47] "I rebuilt mir-kiosk-kodi, egmde..." <- Just sunsetting I think. Maybe (re)work Miriway into `confined-desktop`? [07:51] "That sounds weird? https://..." <- Yeah, that would work if (a) every snap which wanted to send notifications declared a plug for `org.freedesktop.Notifications` (which none do), and (b) you manually connected every snap to your notification daemon snap. [07:52] That sounds like a problem with the `desktop` interface, I think [07:53] That should include access to the notifications DBus, wherever it's coming from [07:54] "Just sunsetting I think. Maybe..." <- Yup, that's what I meant - can be in whatever order? [08:04] Oooh, and that's EOW! [08:05] Hopefully that Mir build will be waiting for me on Monday ;) [08:05] 👋 [08:48] "That should include access to..." <- Alternatively you could say that the session provides the notification daemon, so it should come with whatever provides the `desktop` slot? === dot-tobias is now known as dot-tobias[away] === dot-tobias[away] is now known as dot-tobias [10:26] alan_g can you reproduce: (half-)maximizing a Xwayland window on Miriway makes it... invisible? Like, I can Alt+Tab to it, but I can't see it? [10:27] Is that mattermost? [10:27] Or Element [10:27] s/Or/And/ [10:27] https://github.com/MirServer/mir/issues/2509 [10:28] Not seen it with xterm, CLion, ... [10:28] Right, that sounds like it. Electron, then. [10:29] For mattermost: https://forum.snapcraft.io/t/call-for-testing-mattermost-desktop-5-1-0/30403/14 [15:21] -GitHub[m]:#mir-server- **[MirServer/mir]** graysonguarino added enhancement to [issue #2613](https://github.com/MirServer/mir/issues/2613): MirRunner does not expose Alarm functionality from MainLoop [15:21] -GitHub[m]:#mir-server- **[MirServer/mir]** graysonguarino opened [issue #2613](https://github.com/MirServer/mir/issues/2613): MirRunner does not expose Alarm functionality from MainLoop [15:21] -GitHub[m]:#mir-server- [15:21] -GitHub[m]:#mir-server- > MirAL currently has no wrapper for `mir::time::Alarm` and there is no way to create an alarmed callback in a similar vein to `miral::MirRunner::add_start_callback()` and `miral::MirRunner::add_stop_callback()`. This could come in handy for clients that need to delay function calls. [15:21] -GitHub[m]:#mir-server- enhancement [16:22] Good weekend all o/ [16:42] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2614](https://github.com/MirServer/mir/pull/2614): Fix rendering that spans outputs [16:42] -GitHub[m]:#mir-server- [16:42] -GitHub[m]:#mir-server- > Fixes: #1753 [16:44] -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 [16:53] alan_g: Regarding removing those generated files from Git, should they be added to .gitignore? [16:54] grayson-g no need, as they won't be reappearing there [17:04] Goodbye all, until next week... [19:41] Not quite sure why this build is failing https://github.com/MirServer/mir/pull/2611#discussion_r961777201 [19:41] It shows that `logind-seat.h` is being generated, but it isn't detecting it later down the line when it gets included in `/src/server/console/logind_console_services.h`. It builds fine locally after I delete the generated files and let it regenerate them so I'm not sure if this is a CI problem. [19:41] I was trying to snap Mir locally because the snap is also failing in CI, but now snapcraft seems to think I'm out of space on my VM 😵‍💫 I just gave the VM 50GB more space and resized the partition successfully, but I suspect something somewhere has an outdated cache of my old drive size. [22:09] New wayland-debug with run mode is now in the snap store [22:14]

"Not quite sure why this build is..." <- It shows that `logind-seat.h` is being generated, but it isn't detecting it later down the line when it gets included in `/src/server/console/logind_console_services.h`. It builds fine locally after I delete the generated files and let it regenerate them so I'm not sure if this is a CI problem. [22:14] I was trying to snap Mir locally because the snap is also failing in CI, but now snapcraft seems to think I'm out of space on my VM 😵‍💫 I just gave the VM 50GB more space and resized the partition successfully, but I suspect something somewhere has an outdated cache of my old drive size. [22:14] you need to add the generated file directory to the include path