RAOFSaviq: oh, by the way, I worked out (half of) why you need the aufs `sed`dery in your local spread thing.07:35
RAOFIf the lxd storage is on zfs, then it lacks a feature needed for schroot to use an overlay filesystem.07:37
SaviqAh, so that's the same you encountered07:38
RAOFLXD seems to no longer set up a zfs loop mount by default, so CI works and my more recent setup works 07:39
RAOFThere's ways to get schroot to not try overlay filesystems, and it's not useful in ephemeral LXD containers.07:40
SaviqI'm actually on ZFS root, do that's what's used, but same problem07:40
SaviqCould be simply --type=directory for mk-sbuild?08:03
SaviqOh here's a new one from the lab:08:06
Saviq> Mir fatal error: mir::graphics::wayland::Display not initialized08:06
Saviq<Saviq> "Could be simply --type=..." <- Nope.08:14
Saviq> <@saviq:matrix.org> Oh here's a new one from the lab:10:27
Saviq> > Mir fatal error: mir::graphics::wayland::Display not initialized10:27
SaviqHmm this is happening consistently now on particular HW in the lab, but I can't see anything that's changed software-wise.10:27
alan_g[m]If you have logs I'll take a look once I'm out of current rabbithole10:28
SaviqLast success on this hardware:10:34
SaviqBut downgrading mir* to the versions from the successful one doesn't solve.10:35
SaviqAlso another (non-nested) test run on the same hardware is fine:10:35
SaviqSo yeah. So far no clue.10:36
SaviqI was able to reproduce, and non-nested failed as well. Only difference at that point was mir-kiosk being installed (but not running). Next I'll start from the working non-nested setup and see if/how I can get to a broken state10:37
SaviqBut that's in ~2h10:37
SaviqOh I see, it's because mir-kiosk dies12:29
SaviqThat "Display not initialized" is b/c the tests don't get access to the device12:30
SaviqOK. This is GAH. Based on my findings, the offending mir-kiosk changes are… drumroll… 16:16
SaviqEverything else is the same between the two snaps. The dependencies Mir built with. The things packaged into the snaps. Yet, one reliably (4 tries now) fails, the other, I've not seen fail yet.16:26
-GitHub[m]:#mir-server- **[MirServer/mir]** Saviq assigned AlanGriffiths to [issue #2632](https://github.com/MirServer/mir/issues/2632): Miriway frequently crashes to GDM after exiting powersave16:34
-GitHub[m]:#mir-server- **[MirServer/mir]** Saviq unassigned RAOF from [issue #2632](https://github.com/MirServer/mir/issues/2632): Miriway frequently crashes to GDM after exiting powersave16:34
sophie-wWhy am I getting std::exception::what: Failed to find any platforms for current system when trying to run a simple Mir-based server? I have mir-platform-graphics-x installed.17:10
sophie-wI feel like this should be super obvious17:11
alan_g[m]The rest of the log should show which platforms are tried and (hopefully) why they aren't usable17:12
* sophie-w sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/d58cc978c66c7d3de02a0c9ef59cb25280bc674a17:15
sophie-w$ ls /usr/lib/x86_64-linux-gnu/mir/server-platform/17:16
sophie-wgraphics-gbm-kms.so.19  graphics-wayland.so.19  input-evdev.so.8  server-x11.so.1917:16
alan_g[m]"<information> mirserver: Found graphics driver: mir:x11 (version 2.7.0) Support priority: 0" - no DISPLAY variable?17:16
sophie-wok fixed it17:17
sophie-wDISPLAY was set to wayland-117:18
alan_g[m]Ah! Mate likes to do that for weird reasons17:18
sophie-wIt seems to happen only when right-clicking in thunar and clicking "open terminal here"17:19
alan_g[m]So XFCE does it too?17:19
sophie-wAnd thunar is only opened when I open the downloads directory from FF17:19
sophie-wApparently 17:20

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!