[07:48] <Mirv> duflu: oh, I forgot the fun part of my Chromebook. since as you remember I did the original installation from USB stick to USB stick. I copied the contents of USB stick to SSD without partitioning or anything, and then just configured grub long enough inside chroot to that partition so that Ubuntu booted. but the thing is the directories of ChromeOS and Ubuntu on that biggest (26GB) partition don't
[07:48] <Mirv> clash, so I have a working dual-boot (Ctrl-D vs Ctrl-L) from the same partition..
[07:49] <Mirv> duflu: it doesn't help though that if I press the space button in the boot screen, everything would be deleted of course (if not canceling before timer is up)
[07:50] <Mirv> but ChromeOS doesn't detect anything being "corrupted" or anything while I have a booting Ubuntu installation there and grub installed
[07:51] <Mirv> ...and now back to testing the Mir inputinfo thing on the chromebook
[08:02] <duflu> Mirv: Sorry, back now. Cool...
[08:45] <tsdgeos> anpok: you around? i have a touchpad question and mzanetti sent me to you :D
[08:46]  * duflu 's ears prick up
[08:46] <tsdgeos> i got a new laptop and the touchpad "tap" doesn't work under unity8 while it works under unity7
[08:47] <tsdgeos> i.e. mouse click is not registered
[08:47] <tsdgeos> i've played with the N settings of system-settings to no difference
[08:47] <tsdgeos> i was wondering how to start to debug it
[08:47]  * duflu shouts at apport for innocently reporting many crashes
[08:50] <duflu> tsdgeos: The tick box "Tap to click" in System Settings is ticked right?
[08:50] <tsdgeos> duflu: yes
[08:50] <duflu> Just tried Apple Magic Trackpad and tap to click works fine. Although I'm not sure who implements it where
[08:52] <tsdgeos> duflu: otoh this laptop has a separate button, a "button inside the touchpad" and the tapping in the touchpad
[08:52] <tsdgeos> the first two work, the third no
[08:52] <tsdgeos> maybe it is confusing something with so many "buttons"
[08:53] <duflu> tsdgeos: Very weird. Tap to click works in U8 but not in Mir demo servers and the input report shows no events for it (!?)
[08:53] <tsdgeos> magic!
[08:53] <duflu> Indeed
[08:55] <duflu> Hmm, it's a server configuration thing. I guess U8 sets tap_to_click but not our demos
[08:55] <duflu> tsdgeos: Often it's a sensitivity problem with many laptops... try a very long tap or very short
[08:56] <duflu> Many times...
[08:58] <tsdgeos> duflu: it's weird because the system settings settings seem to do nothing basically
[08:58] <tsdgeos> there's also a "two finger swipe" setting
[08:58] <tsdgeos> that i can either have enabled or disabled
[08:58] <tsdgeos> and two finger swipe will work anyway
[08:59] <duflu> tsdgeos: Sounds plausible.. the settings themselves not working. And the default is no tap to click so it's not getting applied
[08:59] <duflu> I think I've seen that happen too. Mouse & Touchpad settings sometimes ignored
[10:58] <anpok> tsdgeos: re .. libinput tries to come up with defaults for the touchpad based on its hwdb. I have no idea yet why changing that configuration does not work.
[13:38] <alan_g> greyback: is the only thing "needs fixing" the spurious space character? https://code.launchpad.net/~alan-griffiths/miral/initial-gdk_window_move_to_rect-inspired-placement-logic/+merge/304236/comments/786595
[13:39] <greyback> alan_g: not necessarily. As you say, it can be left for the following branches, since you've chained them.
[13:40] <greyback> branch approved
[13:41] <alan_g> Fixed in lp:~alan-griffiths/miral/connect-gdk_window_move_to_rect-inspired-placement-logic-to-Mir-0.25-API
[13:54] <TheKit> I tried exactly the same EGL_CONFIG_ID as used by SFOS (7), but still getting EGL_BAD_DISPLAY error
[13:54] <TheKit> anything else I can try? - http://pastebin.com/X4Y8egEg
[21:39] <TheKit> kdub, anpok_, it turns out EGL_BAD_DISPLAY wasn't because of bad EGL config
[21:39] <TheKit> suddenly remembered about apitrace and used it to check
[21:39] <TheKit> eglMakeCurrent(dpy = NULL, draw = NULL, read = NULL, ctx = NULL) = EGL_FALSE
[21:40] <TheKit> eglMakeCurrent gets called with NULL display for some reason