[01:11] <blmvxer> Hello, I have a couple questions about mir and unity8 on x86
[01:18] <duflu> blmvxer: Hi, yes?
[01:21] <blmvxer> I've been trying to force rotation on My baytrail tablet as it's stuck in portrait until I get the gyro drivers up.
[01:21] <blmvxer> is there a command line or config way of doing that?
[01:29] <duflu> blmvxer: Yes, but the command line for it isn't introduced till Mir 0.26.0 :)
[01:30] <duflu> blmvxer: If you have Mir 0.26 or later then run 'mirout -h' to see the commands
[01:31] <blmvxer> Ugh dang it, well one last question. Maliit keyboard doesn't display either, is there a way to manually invoke that?
[01:31] <duflu> blmvxer: Not sure about that one. Maybe try #ubuntu-unity
[01:33] <blmvxer> Installing mir-utils aws and I'll check with them. I just recently got Ubuntu "hacked" on my baytrail and was hoping to mess around with Unity8 since there's an x compatibility layer and such
[01:33] <blmvxer> It's apparently mir 0.24
[01:34] <duflu> blmvxer: Yeah I maintain Xmir also. If you're running Mir 0.24 then it sounds like you're not up to date. I suggest Ubuntu 17.04 for the latest Unity8+Mir
[01:35] <duflu> (which is Mir 0.25)
[01:35] <blmvxer> That probably won't allow me to force landscape mode though, right? That's the only issue other than maliit I'm facing
[01:38] <duflu> blmvxer: Yes and no. Mir 0.26.0 will be released to Ubuntu 17.04 in the coming weeks, which will solve it. However earlier Ubuntu versions won't ever get the newer Mir
[01:39] <blmvxer> Dang, I'm just not looking forward to building the kernel since I require so many patches and drivers to even boot on this tablet lol
[01:40] <blmvxer> Thanks though for your help, I'll check with the other channel for help on Maliit
[01:41] <duflu> Ok, no problem
[11:31] <alan_g> greyback: this is potentially useful to you - https://code.launchpad.net/~alan-griffiths/miral/trace-exceptions/+merge/315112
[11:34] <greyback> yep looks like it could come in handy
[13:36] <dandrader> alan_g: what's the silo with miral's upcoming release?
[13:37] <dandrader> alan_g: think I found it https://bileto.ubuntu.com/#/ticket/2382
[13:37] <alan_g> dandrader: 2382 - it's in QA ATM
[13:37] <alan_g> yeah, that's it. :)
[14:32] <tjaalton> is mir in xenial older so that newer xmir can't be used there, and will stay like that?
[14:32] <tjaalton> wondering what to do with lts-hwe
[14:33] <tjaalton> drop xmir entirely from it and rely on the original one, or forward-port the old xmir patch to lts-hwe version..
[14:35] <tjaalton> looks like xenial is just missing mir_event_type_input_device_state
[14:40] <alan_g> tjaalton: AFAIK there's no current intent to update xenial with a new Mir
[14:40] <tjaalton> alan_g: ok, that's fine
[14:40] <tjaalton> looks like I've fixed this build fail in the past too :)
[14:41] <alan_g> It is remotely possible that the whole stack will be SRU'd at some point. (But not before 17.04 ships.)