[10:27] <greyback> anpok_: hey, any ETA on silo4 landing?
[10:29] <greyback> hmm seems to be building with lots of failures, I'll assume it'll be a few days at least
[11:37] <anpok_> greyback: yes
[11:37] <anpok_> greyback: waiting on qtubuntu papi .. still need to port the older gtk+ used in vivid..
[12:03] <alf_> anpok_: You said something about making the input stack treat the device as touchscreen instead of touchpad?
[12:03] <anpok_> yes
[12:04] <anpok_> the flags array that indicates the available keys (EV_KEY) needs the BTN_TOUCH bit to be set and the evdev properties array needs the DIRECT_TOUCH (or TOUCH_DIRECT?) to be set.
[12:07] <alf_> anpok_: INPUT_PROP_DIRECT ?
[12:07] <anpok_> ah yes
[12:09]  * alf_ wonders where to use this with the evdev python bindings
[12:12] <kdub> AlbertA, thanks for the vulkan video
[12:13] <anpok_> there is a capabilities property
[12:13] <anpok_> but that seems to be read only
[12:14] <anpok_> alf_: but there is a chance that only setting BTN_TOUCH is enought (provided that the ABS_MT_POSITION_{X,Y} touch axes are configured)
[13:25] <greyback> alf_: hey, when you launch mir with --vt=8, it correctly starts on vt8. But should it also switch the current vt to vt8?
[13:25] <greyback> seb128: ^^
[13:25] <seb128> thanks
[13:25] <seb128> note that on that snappy image, for some reason the lightdm log has warnings like
[13:25] <seb128> "Error using VT_ACTIVATE 7 on /dev/console: Inappropriate ioctl for
[13:25] <seb128> device"
[13:25] <greyback> hmm, sounds relevant
[13:25] <seb128> so maybe that's the issue
[13:26] <seb128> unsure why it's doing that though
[13:26] <greyback> seb128: what hardware you using?
[13:26] <seb128> snappy is using the standard distro/kernel
[13:26] <seb128> inspiron 3000, all intel
[13:26] <greyback> should be ok
[13:26] <seb128> ubuntu standard doesn't have that issue
[13:26] <seb128> unsure why
[13:26] <seb128> or unsure why snappy has it
[13:27] <seb128> it's the same software stack, just the image is built differently
[13:28] <alf_> seb128: greyback: it should normally switch vts
[13:28] <seb128> is there any log that could indicate why it fails it that's not working?
[13:29] <greyback> seb128: is usc definitely being started after the lightdm x session? In case X is preventing the vt switch somehow (guess)
[13:30] <seb128> I think so
[13:30] <seb128> well, usc is not started before I try to log in as far as I can tell
[13:30] <seb128> and logging in unity8 session doesn't start X, does it?
[13:31] <greyback> nope
[13:32] <greyback> well it shouldn't, unless something tries to spawn it
[15:48] <attente> hi. when i run the mir_demo_server using the packaged version in W, mir-demos=0.13.3+15.10.20150617-0ubuntu1, the server just freezes up, no mouse input, no way to switch VTs
[16:01] <AlbertA> attente: ummm... I just tried here in a haswell laptop, using W and same pkg version: "sudo mir_demo_server --vt 1" it worked ok for me
[16:02] <AlbertA> attente: do you have a thread backtrace?
[16:04] <attente> AlbertA: it doesn't crash, and there's very little on output on stdout/stderr
[16:04] <attente> it's almost as if it doesn't respond to any input
[16:04] <attente> including the vt switch shortcut
[16:05] <AlbertA> attente: umm that can happen if you start the server without sudo
[16:06] <attente> AlbertA: doh. thanks :)
[16:48] <dandrader> I'm trying without success to print mir input log for unity8
[16:48] <dandrader> should MIR_SERVER_INPUT_REPORT=log and MIR_SERVER_LEGACY_INPUT_REPORT=log still work?
[16:53] <AlbertA> dandrader: they should
[16:53] <dandrader> oh, wait! I think it did work!
[16:53] <dandrader> AlbertA, sorry for the noise
[16:54] <AlbertA> dandrader: no prob
[17:38] <racarr> Howdy :)
[17:51] <dandrader> racarr, so mir still uses android-input's EventHub and InputReader, right?
[17:51] <racarr> dandrader: For now ;)
[17:52] <dandrader> trying to get that detailed logging android-input has...
[17:52] <racarr> dandrader: You have to enable it with the ifdefs in the files
[17:52] <racarr> then ANDROID_LOG_TAGS=*:v
[17:52] <racarr> MIR_SERVER_LEGACY_INPUT_REPORT=log
[17:52] <dandrader> ahhhh!!!! missed the ANDROID_LOG_TAGS!
[17:53] <racarr> It's so bad :( sorry
[17:53] <dandrader> it's been ages since I last used it
[17:53] <dandrader> racarr, thanks
[17:59] <dandrader> racarr, all those android-input notifications of input devices coming and going etc they will be logged only by usc right? unity8 will get "high level" mir input events from usc like an app, right?
[18:00] <racarr> dandrader: True, yeah...inputreader and eventhub shouldn't be used in U8
[18:02] <dandrader> AlbertA, where does usc logs go?
[18:02] <dandrader> not in .cache/upstart, right
[18:03] <AlbertA> dandrader: they go into  /var/log/lightdm/unity-system-compositor.log
[18:05] <dandrader> AlbertA, wow, would never find it. thanks!
[18:16] <dandrader> AlbertA, do you know how to flush usc log messages? they don't appear in the log file as soon as they happen
[18:16] <dandrader> AlbertA, so I have to touch the screen to get some more log happening so that the log file does get updated
[18:22] <AlbertA> dandrader: I don't know. I usually just do tail -f
[18:22] <AlbertA> messages show up fine....
[18:23] <dandrader> AlbertA, that's what I'm doing. But the log file doens't get updated/written after every single message
[18:23] <dandrader> AlbertA, only after a number of them have been written. and sometimes it even stops in the middle of a log line
[18:28] <AlbertA> dandrader: ummm strange.. these are the android input stack message or everything?
[18:28] <dandrader> AlbertA, android-input.
[18:28] <dandrader> AlbertA, didn't enable other logging to tell
[18:29] <AlbertA> let me see how they print
[18:30] <dandrader> racarr, "[InputDispatcher]Dropping event because there is no focused window or focused application." <- this shouldn't ever happen, right?
[18:30] <dandrader> racarr, in usc while unity8 is running
[18:34] <racarr> dandrader: Hmm. I don't think it should no
[18:36] <AlbertA> dandrader: so it goes through the mir logger which doesn't flush after every line so probably explains the behavior
[18:36] <dandrader> AlbertA, thanks for looking into it. should I report a bug?
[18:37] <dandrader> racarr, this happens when running autopilot tests. as they create a /dev/input/eventX file for the fake keyboard
[18:37] <dandrader> racarr, the first time it works. but from the second time onwards it does not
[18:37] <dandrader> racarr, https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1468029
[18:39] <AlbertA> dandrader: yeah
[18:45] <dandrader> AlbertA, https://bugs.launchpad.net/mir/+bug/1470204
[18:46] <racarr> Trying to figure out what could be going on...
[18:48] <racarr> dandrader: I dunno...unfortunately too a lot of relevant code to key focus selection was just replaced with the new input dispatcher
[18:48] <racarr> unfortunately and or perhaps fortunately
[18:51] <dandrader> racarr, at least it's easy to reproduce
[19:04] <anpok> racarr: hi
[19:04] <anpok> racarr: hm device introspection is kind of required for raw events because clients would observe/receive them per device rather then per surface?
[19:27] <anpok> racarr: could also be someone not focusing the surface
[19:28] <anpok> i mean .. there were more focus related changes in the past
[19:28] <anpok> in usc..
[19:56] <kgunn> racarr: so can i assign you to that bug ?
[19:56] <kgunn> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1468029
[19:56] <kgunn> it needs someone to love and care for it
[20:08] <tedg> I'm getting a "std::exception::what: No appropriate client platform module found"
[20:08] <tedg> How do I tell mir client what backend to use?
[20:28] <tedg> Okay, fixed that.
[20:29] <tedg> RAOF, So I seem to be starting Xmir, and it seems to be happy, but Unity8 isn't rendering anything. I don't think it's getting that first buffer swap.
[20:29] <tedg> RAOF, What am I doing wrong? ;-)
[20:29]  * tedg should be a talk show host.
[20:32] <kgunn> racarr: i went ahead and gave that one to you
[22:07] <racarr> kgunn: Oh you're back, I just sent you an email but, roger re:text crash bug
[22:07] <kgunn> thanks racarr
[23:50] <RAOF> tedg: Have you connected a client to XMir? It's not going to render anything unless a client renders.