[06:52] <Mirv> duflu: do you have a chromebook with the gfxboot issue or just polishing bugs?
[06:54] <Mirv> I was meaning to try to figure out how to rip off gfxboot from image (like unetbootin does, but unetbootin does not work for 16.04 images anymore), but then again my main problem with my chromebook is that the seabios cannot boot from internal SSD which makes installing Ubuntu there a bit useless.. (even though it works, I used 14.04.4). so I'm using chroot for now.
[06:56] <duflu> Mirv: Yes I have one, but have other priorities than hacking it right now. My previous experiences told me not to install Ubuntu onto the Chromebook itself. Because unless you can access the hardware write-protect switch it will default to giving you a warning on boot up... and then hitting the wrong key will clobber the Ubuntu setup
[06:57] <duflu> Better to install Ubuntu to USB or SD or something
[06:59] <Mirv> duflu: that's true too, you can't disable the easy-to-push-destroy without disabling the write protect. then again, it seems quite well documented what screw to unscrew to disable write protection. but your idea of using Ubuntu from USB/SD would actually be the solution for my SeaBIOS problem too, so maybe I should actually try to find time to modify 16.04 image to be bootable.. or I could use the unetboo
[07:00] <Mirv> tin for 14.04.4/.5 and upgrade that to xenial
[07:00] <Mirv> I'd like to run Unity 8 / Mir / everything over there since it's a touch enabled chromebook too
[07:00] <duflu> Yeah Chromebooks are handy hardware. It would be good for Ubuntu if we supported them a bit better
[07:01] <Mirv> the SUSE's gfxboot developer did his best. then again if we would get _UEFI_ boot working (whatever it needs) instead of legacy we wouldn't be using gfxboot in the first place
[07:02] <duflu> Mirv: Chromebooks have EFI??
[07:02] <Mirv> but it seems it's still TODO and not WIP for eg GalliumOS too
[07:02] <Mirv> duflu: AFAIK that's what it tries to boot when pressing "Ctrl+U" instead of "Ctrl+L", but I really do not have slightest idea what kind of Coreboot payloads or such it'd need
[07:03] <duflu> Mirv: I thought Ctrl+U was for ChromeOS USB sticks only?
[07:03] <duflu> U for USB, not UEFI
[07:03] <duflu> L for legacy (Ubuntu)
[07:04] <Mirv> duflu: well hmm at least some have certainly hacked TianoCore (UEFI) on top of Coreboot and have Xubuntu running https://github.com/GalliumOS/galliumos-distro/issues/112
[07:05] <duflu> Mirv: BTW don't expect Mir to start just yet: https://bugs.launchpad.net/mir/+bug/1169020
[07:05] <duflu> Mir doesn't support VT-less kernels (ChromeOS)
[07:06] <duflu> I hope that's the only hurdle
[07:06] <Mirv> oh, ok. well Unity 8 on X.org for starters then would be my goal..
[07:07] <duflu> Also Mir has at least two other minor kernel requirements that ChromeOS may not meet
[07:07] <duflu> They would all need workarounds
[07:07] <Mirv> ...a goal for some rainy day I get that chromebook out of the drawer
[07:08] <Mirv> duflu: well if we're booting Ubuntu we're not running ChromeOS?
[07:08] <Mirv> only coreboot + seabios and then normal kernels and everything
[07:08] <duflu> Mirv: I mean the Crouton option... which is better for armhf chromebooks
[07:09] <Mirv> ah well crouton is totally else yes, that's what I have at the moment
[07:11] <Mirv> my chromebook is x86, similar to https://www.amazon.com/Acer-Chromebook-CB5-132T-C1LK-Certified-Refurbished/dp/B01GK8URL2/ - 4GB, 32GB, quad-core 14nm Atom with Broadwell era graphics
[07:12] <Mirv> with crouton I only got KDE Plasma 5 working with xenial, and even that needed some hacking. the script is badly out of date but Unity(7) wouldn't start even after removing the unity-2d referrals
[07:14] <duflu> Mirv: I recall last time I tried the only workable option was either 12.04 or 14.04 and then partially successful upgrade
[07:24] <Mirv> duflu: it's still the same unless you do some fixing in /tmp where crouton unpacks its scripts, and run then from there
[07:24] <Mirv> but with a couple of fixes xenial installation is possible
[07:24] <Mirv> for KDE I was simple fixing the plasma-desktop package name to point to the current KDE5  name
[07:24] <duflu> I feel Ubuntu should be keeping up with consumer devices like Chromebooks and Windows tablets better than it is...
[07:25] <Mirv> Plasma is useful for me since I can test Qt 5 with that at least
[10:08] <alan_g> namecheck for anpok - https://who-t.blogspot.co.uk/2016/07/libinput-is-done.html - congrats
[12:15] <anpok> oh wow
[16:38] <alan_g> camako: this has changed again since you approved, still happy? https://code.launchpad.net/~alan-griffiths/mir/add-mir_surface_spec_attach/+merge/300202
[16:38]  * camako looks
[16:39] <camako> alan_g, LGTM
[16:40] <alan_g> camako: thanks
[17:26] <greyback> alan_g: "placement" is a funny word instead of position. How come?