[01:56] <kdskr> have i ubuntu to my samsung gakaxy s7 edge
[01:56] <kdskr> ?
[02:56] <black_pixel> hi
[02:58] <duflu> Hi. I thought holding conversations in 4 channels at once wasn't enough so let's do five
[03:14] <black_pixel> LOL
[03:15] <black_pixel> weee 5 hours of using unity8 on the desktop
[03:15] <black_pixel> new record
[10:48] <mcphail> Has there been a decision made on whether snaps are coming to the e4.5? Presumably the kernel issues are insurmountable?
[11:02] <DanChapman> mcphail: I think it's still early days on that decision, but i would have thought your assumptions on the kernel limitations are correct
[11:21] <mcphail> DanChapman: thanks
[11:27] <Saviq> Elleo, hey, I'm getting http://pastebin.ubuntu.com/23751762/ and transparent OSK, ideas?
[11:28] <Saviq> the wizard didn't set something?
[11:41] <Saviq> Elleo, huh, changing it to "en" via gsettings didn't help, now it's saying that en isn't enabled O.o
[11:41] <Elleo> Saviq: what platform is that on? Desktop?
[11:41] <Saviq> Elleo, frieza
[11:42] <Saviq> arm64
[11:42] <Saviq> xenial
[11:43] <Elleo> ah, I haven't tried flashing a device with frieza's arm64 image yet, I had heard that the current image was pretty broken from people that had
[11:43] <SebthreeBQM10HD> hey
[11:43] <SebthreeBQM10HD> anyone around ?
[11:43] <SebthreeBQM10HD> bregma, to early ? ogra_  ping
[11:44] <SebthreeBQM10HD> anyway
[11:45] <SebthreeBQM10HD> just been reading omgubuntu about  how apparntly UBUNTU Touch is dead, well thats not what the blog post actsually says, but how certain people seem to interupt things in the comments
[11:45] <Elleo> Saviq: I don't think the subview error is anything to worry about though, that's just due to us not using maliit's subview system for actually handling the plugin switching
[11:45] <SebthreeBQM10HD> since wont have usual ota updats etc.  the transiting to new things etc :)
[11:45] <SebthreeBQM10HD> response to mailing list
[11:46] <SebthreeBQM10HD> Elleo, dev or user ?
[11:46] <SebthreeBQM10HD> some people really dont get it it seems
[11:46] <Saviq> SebthreeBQM10HD, check out the mailing list
[11:46] <Saviq> the discussion's been going there for a few weeks
[11:47] <SebthreeBQM10HD> Saviq, yeah there was a mailing list post that got linked to explaining things nicely,  but this omgubuntu link.  I am just generally commenting
[11:47] <SebthreeBQM10HD> I Know thing aren' dead, things are coming etc
[11:48] <SebthreeBQM10HD> Saviq, makes sense to drop new features for the 15.04 base I guess though, since thats on the verge of being completly dropped a
[11:48] <Saviq> yes, that's definitely part of the picture, maintaining click/15.04-based releases was a pain
[11:49] <SebthreeBQM10HD> oh actsually can the bq 4.5  ubuntu support the new snaps Ubuntu that is coming ?
[11:49] <SebthreeBQM10HD> or are those phones going to get dropped
[11:49] <Elleo> Saviq: one idea, maybe try disabling unity's keyboard supression by changing oskEnabled to true in OrientedShell.qml to see if there's anything on that xenial image presenting itself as a hardware keyboard and so preventing the OSK from displaying?
[11:50] <Saviq> Elleo, it's not suppressed, things are actually moving around, it's just that it's transparent... the QSG errros say "expect rendering issues", maybe that's that?
[11:50] <SebthreeBQM10HD> Saviq, seems going by things I just read, its not so clear, if the BQ 4.5 will be able to support a new snappy ubuntu
[11:50] <Elleo> Saviq: maybe, does that show up in the logs for any other apps?
[11:51] <Saviq> Elleo, not that I've seen
[11:54] <Saviq> SebthreeBQM10HD, we'd need vendor support to get there, need newer kernels, and those we're getting from the OEMs - couldn't say, really
[11:55] <Elleo> Saviq: are you able to press keys on the invisible keyboard?
[11:55] <Saviq> Elleo, good question, will try in a sec
[11:55] <SebthreeBQM10HD> Saviq, you mean the phones would need some actsual later manufacture firmwire ?
[11:56] <Saviq> SebthreeBQM10HD, well, newer kernel - we can update those on existing devices, but we'd need to get it from the OEM
[11:57] <SebthreeBQM10HD> Saviq, BQ probably don't really care much about the 4.5 and EF HD now.  Meizu MX4 better hardware, but again if that were to be a issue phone. Meizu woudn't realy care about it now
[11:57] <SebthreeBQM10HD> Saviq, you mean their kernel, with their drivers etc
[11:57] <SebthreeBQM10HD> ?
[11:57] <Saviq> SebthreeBQM10HD, that's where we're getting the kernel and drivers from, yes
[11:58] <SebthreeBQM10HD> Saviq, so for those devices to have support with Snap based Ubuntu,  the OEM's would have to provide kernel and drivers, oh ok
[12:01] <Saviq> Elleo, no, no interaction with the keyboard
[12:01] <ogra_> if it is an invisible keyboard you probably have to close your eyes to interact with it
[12:01] <ogra_> :P
[12:21] <Elleo> Saviq: maybe not just a rendering issue then; I'm wondering if it's possible that the surface is ending up behind everything else?
[12:22] <Saviq> Elleo, unlikely, but not impossible - also one important data point is that it was fine until I completed the wizard... bootstrapped now so will let you know if that reproduces
[12:23] <black_pixel> welp does anyone know if frieza_arm64/staging/r116 is bootable?
[12:23] <Elleo> Saviq: interesting
[12:23] <Saviq> black_pixel, bootable, yes, but that's about it...
[12:23] <black_pixel> thanks Saviq :D then i'll wait for a new image
[12:24] <Elleo> Saviq: it'd be good to know if you get those rendering error messages while it's working in the wizard too
[12:25] <black_pixel> Saviq: what is in that image? it's just xenial+overlay and maybe unity8 snap? last time i looked it didn't seem like something you see in personal
[12:26] <Saviq> black_pixel, no snap, not for a while still
[12:26] <black_pixel> so it's just xenial+overlay :D
[12:26] <black_pixel> Saviq:  ok thanks :D
[12:26] <Saviq> yes, "traditional" still, we're working on a snap-based image
[12:30] <black_pixel> nice :D
[12:43] <Saviq> Elleo, same messages, OSK fine in wizard... and then after wizard ever touch makes it slide down O.o
[12:43] <Saviq> might be somewhat related to the fact that orientation sensor is nowhere to be found...
[12:44] <Saviq> jibel, has anything changed in device tarball and such? think it would be possible to go back to a working image and start upgrading packages one by one?
[12:44] <Saviq> there seem to be just too many issues...
[12:47] <Elleo> Saviq: okay, guess I'll try and get my m10 flashed to that image and see if I can figure anything out :/
[12:48] <Saviq> Elleo, note device is frieza_arm64
[12:49] <Elleo> Saviq: right
[12:51] <Elleo> Saviq: does it need to be a specific image? I seem to remember someone mentioning that some of the more recent ones don't boot
[12:52] <Saviq> Elleo, the newest one does boot, but there's *issues* - downgrade dbus* to the released version, that gets you most of the way towards a working thing
[12:52] <Saviq> not sure yet why we got proposed enabled in there
[12:52] <Elleo> okay, which channel?
[12:53] <Saviq> Elleo, ubuntu-touch/ubuntu/staging
[12:53] <Elleo> thanks
[13:02] <Saviq> Elleo, found something in unity8.log
[13:02] <Saviq> greyback, [2017-01-06:13:04:45.216] qtmir.surfaces: MirSurface[0x1f811190,"-"]::dropPendingBuffer() dropped=0 left=1 - failed to upate texture
[13:02] <Saviq> ring a bell?
[13:03] <Saviq> yeah that has to be it
[13:03] <Saviq> happens every time maliit tries to draw
[13:03] <greyback> Saviq: usually means the surface isn't made visible in the shell
[13:04] <greyback> i.e. a MirSurfaceItem for it was not created, or set visible
[13:04] <Saviq> that would be our bug then
[13:05] <Elleo> Saviq: never seen that before
[13:05] <Saviq> Elleo, ↑ we need some investigation on our side
[13:05] <Elleo> Saviq: okay cool, I'll hold off on breaking my m10 then :P
[13:05] <greyback> something funky going on alright
[13:06] <greyback> is there a bug with a quick summary of how to repro?
[13:18] <Saviq> greyback, yeah, flash frieza ;)
[13:18] <Saviq> filing a bug in a mo
[13:19] <Saviq> Elleo, just realized maliit-server.conf is only an upstart job in ubuntu-touch-session... shouldn't we have it in unity8-desktop-session, too?
[13:20] <greyback> would be sensible
[13:22] <greyback> Saviq: what channel has the xenial image?
[13:23] <greyback> devel-prpposed?
[13:23] <jibel> greyback, staging/ubuntu
[13:23] <Elleo> Saviq: yeah, I'd have thought so
[13:24] <Saviq> greyback, --device frieza_arm64
[13:24] <Saviq> Elleo, TBH it shouldn't be in any -session at all, should it - should be shipped with the keyboard?
[13:24] <Saviq> yay, reproduced OSK jumping jacks
[13:24] <Saviq> on desktop
[13:24] <greyback> Saviq: ack thanks, fetching image 116
[13:25] <Elleo> Saviq: maybe, I'm not sure what the original reasoning was behind sticking it in the -session packages was, that predates me :)
[13:25] <Saviq> yeah, there probably wasn't any, except for "it'll do, will fix that later"
[13:25] <Elleo> heh
[13:25] <Saviq> the definition of tech debt, really
[13:29] <Saviq> greyback, note you'll need to downgrade dbus to the !proposed version to get *anywhere*
[13:29] <greyback> ok
[13:29]  * greyback goes for lunch while it flashes
[13:47] <mterry> morphis_: hello!  I was interested in checking out how the pulseaudio snap works -- is there source somewhere?
[13:47] <mterry> morphis_: I'm interested in relying on it for the unity8 snap
[13:47] <mterry> morphis_: do I just need to add the slot "pulseaudio"?  (is that autoconnected for me?)
[13:48] <Saviq> Elleo, it's the OSK that's dealing with the drag-down-to-dismiss gesture, right? I've managed to reproduce a jumping-jack-OSK on a zesty desktop (using http://paste.ubuntu.com/23752185/ to force it to show in the first place)
[13:49] <Elleo> Saviq: yeah, it is; I don't get that behaviour on my xenial desktop though
[13:50] <Elleo> Saviq: actually, could you expand on what you mean by jumping-jack OSK to make sure I'm understanding the issue right? Is it dismissing when you attempt to press a key?
[13:50] <Saviq> Elleo, yes, and coming right back up
[13:51] <Elleo> Saviq: and is the keyboard actually displaying or is it invisible like on the m10?
[13:51] <Saviq> Elleo, displaying
[13:52] <taiebot> With all the negativity of the mailing list i cannot still made up my mind if there will be a new phone with UT.  Is  it worth waiting for wmc ? My nexus 4 stopped charging and I ended up replacing battery and charging port but i feel they were not as good  as originals, so my UT device is near end of life. :'(
[13:55] <taiebot> New charging port has made the notification led blue instead of green :P
[13:55] <Saviq> Elleo, check out the two videos https://owncloud.sawicz.net/index.php/s/OK21qJqovYb5X0w
[13:56] <morphis_> mterry: hey!
[13:57] <morphis_> mterry: sounds great! however the pulseaudio snap currently doesn't support running pulseaudio in a user session but only in system wide mode
[13:57] <morphis_> so I don't know how well this works with the unity8 session snap
[13:57] <mterry> morphis_: yeah I was also curious about that  :)
[13:57]  * mterry isn't familiar with system wide mode
[13:57] <mterry> Just root can play sounds?
[13:57] <morphis_> for IoT devices we don't have any other chance but for personal devices we should add support for that
[13:57] <morphis_> mterry: right now, yes
[13:57] <Saviq> Elleo, bug #1654563
[13:57] <ubot5`> bug 1654563 in ubuntu-keyboard (Ubuntu) "OSK jumping up and down on click/touch" [Undecided,New] https://launchpad.net/bugs/1654563
[13:57] <Elleo> Saviq: I'll setup a zesty vm and see if I can reproduce it there
[13:58] <morphis_> mterry: but its a valid use case to support untiy8 as well we just didn't had a requirement for that yet
[13:58] <morphis_> mterry: source is at https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/pulseaudio/+ref/master
[13:58] <Saviq> Elleo, FWIW I saw the same on frieza@xenial...
[13:58] <mterry> morphis_: how do I add one?  :P
[13:58] <morphis_> mterry: you have access on https://trello.com/b/6xj9V2bb/system-enablement-backlog ?
[13:58] <mterry> morphis_: I wish snaps had "Source:" metadata for open source ones  :)
[13:59] <mterry> morphis_: yes
[13:59] <morphis_> mterry: me too, we include the source link in the description of all our snaps
[13:59] <morphis_> mterry: you should see it with $ snap info pulseaudio
[13:59] <mterry> morphis_: ah very cool thanks
[14:00] <Elleo> Saviq: odd, as I don't get it in unity8 on my xenial desktop system :/
[14:01] <mterry> morphis_: I add to dartboard?
[14:01] <morphis_> mterry: yes, just add it at the bottom
[14:02] <morphis_> jhodapp: can you invite mterry to our stakeholder meeting?
[14:02] <jhodapp> morphis_, sure
[14:02] <morphis_> jhodapp: thanks
[14:03] <jhodapp> np
[14:03] <jhodapp> mterry, invited
[14:09] <Saviq> greyback, bug #1654568 btw
[14:09] <ubot5`> bug 1654568 in unity8 (Ubuntu) "OSK transparent - buffer not updated" [Undecided,New] https://launchpad.net/bugs/1654568
[14:09] <greyback> ta
[14:13] <greyback> Saviq: how do I make the filesystem writable? phablet-config writable-image didn't work, nor has touch /userdata/.writable_image
[14:14] <greyback> or should I just muck with mount?
[14:15] <Saviq> greyback, mount -o remount,rw /
[14:15] <greyback> yep alright
[14:50] <black_pixel> https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1654578
[14:50] <ubot5`> Ubuntu bug 1654578 in webbrowser-app (Ubuntu) "webbrowser-app - Network error 301 protocol "filesystem" is unknown" [Undecided,New]
[14:51] <greyback> Saviq: have your tablet handy? I've got mine set up, and yes OSK surface appears "missing" on first boot. But if I open indicators (makes OSK go away), then close them, OSK re-appears and this time draws
[14:52] <Saviq> greyback, nope, still blank
[14:52] <greyback> hrmph
[14:52]  * greyback reboots and tries again
[14:53] <Saviq> greyback, but yeah it did show up at some point in a similar situation
[20:13] <diddledan> I'm saddened by the ML of late. So much vitriole.
[20:22] <mcphail> diddledan: I think there is inevitable frustration at this point. So near, yet so far