[13:51] <dandrader> ltinkl, in https://code.launchpad.net/~lukas-kde/unity8/keyboardIndicator/+merge/297920 , why did you have to turn qml/Components/KeymapSwitcher.qml into an Item?
[13:52] <ltinkl> dandrader, because of the QDBusActionGroup and the properties inside
[13:53] <ltinkl> dandrader, didn't work for me as a QtObject
[13:56] <dandrader> ltinkl, wonder if it's a bug in qmenumodel
[13:59] <dandrader> ltinkl, talking to renato, who wrote that code.
[14:00] <dandrader> ltinkl, he says it's weird that it didn't work when put inside a QtObject
[14:00] <ltinkl> dandrader, hmm wonder why, don't recall the details
[14:19] <mterry> dednick, indicator-keyboard under u7 apparently provides u7 with the fully rendered icon.  But u8 apparently doesn't support that, and uses just the icon name from the indicator.  Why don't we support using an indicator's provided binary icon?  (info from ltinkl)
[14:23] <dednick> mterry: please hole
[14:23] <dednick> hold :)
[14:23] <mterry> dednick, too late, am holing
[14:26] <dednick> mterry: i'm not entirely sure. if the icon is transmitted as a byte icon (serialized gicon data) it should be given to unity8 as a srting in the format "data://BASE64HEXCODE"
[14:27] <dednick> if i remember correctly we should be picking that up in an icon provider.
[14:27] <mterry> ltinkl, ^ ?
[14:27] <dednick> thats how it worked at some point i'm sure
[14:29] <ltinkl> dednick, mterry: will check it out again
[14:30] <dednick> i can't seem to find the icon provider though...
[14:31] <dednick> maybe somebody removed it because they thought it wasnt used.
[14:43] <ltinkl> dandrader, all good, back to a QtObject :)
[19:10] <mterry> josharenson, bad news.  Testing silo 32, I see a crash/something: I logged in as mike, went back to greeter.  Tried to log into mike again (i.e. unlock my current session).  lightdm/unity8-greeter freak the heck out at this point.  Session, greeter, and lightdm all close?  And then lightdm restarts itself
[19:11] <josharenson> mterry: yikes, logs?
[19:12] <mterry> josharenson, http://paste.ubuntu.com/19104252/
[19:13] <mterry> josharenson, look at end of log (minus recent successful lightdm run)
[19:13] <mterry> josharenson, "WARNING: Error using VT_WAITACTIVE 8 on /dev/tty0: Interrupted system call" ?
[19:13] <mterry> josharenson, that seems like where it went bad
[19:13] <mterry> josharenson, can you try and see if you have same behavior
[19:14] <josharenson> mterry: yeah, 1 min, updating
[19:29] <josharenson> mterry: you logged out, or locked the screen?
[19:29]  * josharenson tries both, brb
[20:29] <mterry> josharenson, going to distro version of lightdm, I don't see the crash problem with silo 32 anymore
[20:29] <josharenson> yay
[21:55] <mterry> robert_ancell, ah!  thanks for fixing the in-session lightdm thing.  Only working on autologins makes sense with what I was seeing
[21:55] <robert_ancell> mterry, np
[21:56] <mterry> will test the new stuff tomorrow
[21:56] <robert_ancell> mterry, you using yakkety or building the packages yourself?
[22:09] <mterry> robert_ancell, I'm on yakkety, only building packages myself if I need to debug (but am happy to build myself tomorrow in advance of a release)
[22:09] <robert_ancell> if you're on yakkety I'll make a release
[22:11] <mterry> just for me!  :)
[22:13] <robert_ancell> An mterry special