[20:08] -GitHub[m]:#mir-server- **[MirServer/mir]** cat-master21 opened [issue #2746](https://github.com/MirServer/mir/issues/2746): Segment fault when launching Mir on release/1.8... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/dacbe4b9ebfd866946de8456a3c2bb0889745c51>)
[21:35] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths closed [issue #2746](https://github.com/MirServer/mir/issues/2746): Segment fault when launching Mir on release/1.8
 "**[MirServer/mir]** AlanGriffith..." <- Hm. How do we want to handle Mir 1.8 series bugs?
[22:45] <RAOF> RAOF: We certainly don't want to promise to *do* anything with them, but do we want to immediately close them? This will probably become particularly relevant as it seems some distros are getting a full Lomiri stack, which will probably result in more 1.x usage and hence more bugs.
[23:50] <alan_g[m]> How does that work? E.g. mirclient, the only reason to use 1.x, needs a distro patch to Mesa.