[05:11] <mvo> kyrofa: hi, the latest os update should contain an updated snappy (iirc you asked about this last week)
[07:53] <zyga> good morning
[07:55] <mvo> hey zyga, good morning
[08:19] <dholbach> good morning
[08:27] <noizer> good morning :D
[10:19] <clobrano> hi all! Is it possible to connect to webdm server from a kvm virtual machine with snappy? I tried but it does not seem to work.
[10:27] <stevebiscuit> clobrano: do you have a route to port 4200 setup? I'm not using KVM myself but there's some info in the README: http://bazaar.launchpad.net/~snappy-dev/webdm/trunk/view/head:/README.md#L53
[10:30] <clobrano> thanks stevebiscuit! Sure, I saw that bug and I run the KVM with this command kvm -m 768 -redir :8022::22 -redir :4200::4200 -hda snappy.img, but I still couldn't connect. I saw that the syslog shows an error like "job webdm failed with result 'dependency' http://paste.ubuntu.com/15169482/
[10:31] <clobrano> stevebiscuit: but no idea about what does that mean
[10:31] <ogra_> looks broken
[10:42] <stevebiscuit> clobrano, ogra_: yeah, that systemd error seems ominous, looks like it might not be able to start the web app
[10:42] <stevebiscuit> clobrano: is there a `snappyd` running?
[10:44] <clobrano> stevebiscuit: yes systemd is running
[10:45] <clobrano> stevebiscuit: well, I'm basically able to do everything I need, just can't connect to webdm
[10:46] <stevebiscuit> clobrano: systemd or snappyd ?
[10:46] <ogra_> how did you install it ... and is that a 16.04 or the old 15.04 ?
[10:46] <clobrano> stevebiscuit: sorry a typo, snappyd is running
[10:47] <clobrano> ogra_: is a kvm virtual machine with 15.04
[10:47] <clobrano> ogra_: I created it with this command kvm -m 768 -redir :8022::22 -redir :4200::4200 -hda snappy.img
[10:47] <ogra_> why the -hda ?
[10:48] <ogra_> (i doubt it breaks anything, butu not needed)
[10:57] <clobrano> ogra_: I tried also without -hda, I took it from Bug #1425021
[12:19] <noizer> zyga can you help for building the snappy environment with your branch?
[12:38] <kyrofa> Good morning
[12:38] <kyrofa> mvo, indeed, thank you!
[12:41] <noizer> Does anyone know when zyga will be back?
[13:13] <noizer> is it normal that i can't install webdm on 16.04?
[13:27] <noizer> kyrofa?
[13:27] <kyrofa> Hey noizer. Can you be more specific? How does it not install? An error? Can it not be found?
[13:28] <kyrofa> What architecture are you using?
[13:28] <noizer> webdm failed to install: can not open /tmp/webdm995163236: cannot open snap: unknown header: "!<arch>\ndebian-binar"
[13:28] <noizer> I'm using 16.04 roling rpi2
[13:29] <kyrofa> noizer, it's possible that webdm needs to be repackaged and re-uploaded after some snappy changes
[13:30] <ogra_> noizer, webdm is 15.04 onlyyet ... i think stevebiscuit works on a 16.04 version
[13:30] <noizer> ok xD
[13:31] <noizer> thx
[13:32] <kyrofa> stevebiscuit, do you know anything about that? ^^
[13:32] <kyrofa> Oh, thanks ogra_
[13:32] <kyrofa> I just spent far too long trying to figure out what his handle was :P
[13:50] <stevebiscuit> kyrofa: that's pretty much the last piece of functionality I've to migrate over to the snapd API
[13:52] <kyrofa> stevebiscuit, excellent. Is the progress feedback still a poll-only interface?
[13:54] <stevebiscuit> kyrofa: the API will soon be using websockets though the front-end JavaScript will likely still poll the WebDM backend
[13:54] <kyrofa> stevebiscuit, ah, okay
[14:36] <kyrofa> dholbach, you know when you're an elite, dedicated member of the Snappy team when...
[14:36]  * dholbach hugs kyrofa  :)
[14:37]  * kyrofa hugs dholbach 
[14:49] <davmor2> kyrofa: put him down you don't know where dholbach 's been ;)
[14:49] <kyrofa> davmor2, don't be jealous
[14:51] <davmor2> kyrofa: dholbach's awesome and he knows it, I tell him too many times for it to of not sunk in :)
[14:56]  * dholbach hugs you all :)
[15:22] <kyrofa> jdstrand, did you ever figure out anything more regarding bug #1467595?
[15:23] <jdstrand> kyrofa: it stopped in later releases
[15:23] <kyrofa> jdstrand, urgh... so wily it wasn't an issue?
[15:23] <jdstrand> I feel like wily was good. xenial still is
[15:23] <jdstrand> let me check something
[15:24] <kyrofa> jdstrand, definitely reason enough to update, then
[15:24] <kyrofa> jdstrand, I'm still on trusty and it's killing me
[15:25] <jdstrand> yeah that bug is seriously annoying
[15:28] <jdstrand> kyrofa: I have in my notes "this seems to be improved with the 4.2 kernel"
[15:28] <jdstrand> kyrofa: that is what is in wily btw
[15:28] <jdstrand> I also commented in the bug
[15:29] <kyrofa> jdstrand, you commented to that effect with 4.1, but then you later commented saying nevermind
[15:29] <jdstrand> I did
[15:29] <jdstrand> I did, and I have notes that say that 4.1 was better but still happened
[15:30] <kyrofa> jdstrand, and 4.2 it hasn't happened at all?
[15:30] <jdstrand> I think wily was ok-- I upgraded to xenial a while ago though, so I can't recall. I never see it any more
[15:30] <jdstrand> kyrofa: I *think* so
[15:30] <kyrofa> jdstrand, alright, good to know
[15:30] <jdstrand> you could try the wily lts kernel
[15:31] <kyrofa> jdstrand, yeah good plan
[15:31] <jdstrand> you might need to snag some other stuff too-- eg the bcmwl modules and maybe linux-firmware
[15:32] <kyrofa> jdstrand, there's another issue that's been killing me too-- occasionally when coming back from sleep (or when initially logging in) and plugged into my external 4k monitor, X just crashes. Did that ever happen to you?
[15:32] <jdstrand> I think I just needed bcmwl for my wifi and linux-firmware wasn't needed
[15:32] <kyrofa> jdstrand, yeah I'll need bcmwl as well
[15:32] <jdstrand> kyrofa: yes. that still sometimes happens. I feel like perhaps less on xenial, but quite sure I've seen it
[15:33] <kyrofa> jdstrand, did you ever make an issue for that? Or shall I?
[15:33] <jdstrand> kyrofa: this is my latest annoyance: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547619
[15:33] <kyrofa> Ugh, that sounds awful
[15:33] <kyrofa> Hahaha, 4k is so bad
[15:33] <jdstrand> 4.3 didn't have that behavior
[15:34] <jdstrand> (or 4.2)
[15:34] <kyrofa> 4.2-4.3 is the sweet spot, eh?
[15:34] <jdstrand> thus far
[15:34] <jdstrand> 4.4 has been ok except for that new bug, and I'm testing bisected kernels, etc
[15:35] <jdstrand> xenial should be decent in the end
[15:35] <jdstrand> kyrofa: I didn't create a bug
[15:35] <jdstrand> (for the crash)
[15:35] <jdstrand> I couldn't find a solid reproducer
[15:36] <kyrofa> jdstrand, oh man, that's easy-- unplug and plug the external until crash. I'll make one :)
[15:36] <kyrofa> jdstrand, I'll make it for trusty, and then perhaps you can comment and whine about wily and xenial too
[15:37] <jdstrand> I don't think I've seena crash with 4.4-- what happens is coming back from suspend the external monitor blanks and unblanks a few times and comes back. of course, the the crash is pretty infrequent for me, so I just might not have hit it yet
[15:38] <jdstrand> hotplugging is the next bug I plan to file-- if I hotplug the xrandr stuff doesn't work right and I get a dialog saying so and the screen stretched all weird. if I press 'Enter' to dismiss the dialog, it all snaps back
[15:38] <jdstrand> I wonder if that is the same bug and the dialog is preventing the crash by stopping before it would crash...
[15:39] <kyrofa> jdstrand, huh, yeah that's interesting. I'm not sure I've ever seen a popup about that
[15:39] <jdstrand> yeah, new in xenial
[15:39] <jdstrand> wily didn't have it
[15:39] <kyrofa> jdstrand, yeah I bet so then!
[15:39] <jdstrand> (and I definitely recall crashes on wily)
[15:39] <kyrofa> Veeery interesting...
[15:40]  * jdstrand nods
[15:40] <kyrofa> jdstrand, maybe we can compare logs. I'll get back to you when I make the bug
[15:40] <jdstrand> ok
[15:41] <kyrofa> jdstrand, it's nice to have someone else who can share my pain
[15:41] <kyrofa> Now if you'll excuse me, I need to logout so my mouse pointer comes back from vacation
[15:43] <jdstrand> kyrofa: heh, :\
[15:43] <jdstrand> kyrofa: good luck!
[15:44] <kyrofa> jdstrand, all good now. Time to fire everything back up now...
[15:50] <Sweet5hark> snapcraft 2.2.2/xenial: I have lots of libs in stage/usr/lib/x86_64-linux-gnu and "snap: - usr/lib/x86_64-linux-gnu/*" in snapcraft.yaml. why are those not in the image
[15:50] <Sweet5hark> ?
[15:53] <Sweet5hark> ogra_: ^^ any hints?
[15:57] <kyrofa> Sweet5hark, check the snap folder
[15:58] <kyrofa> Sweet5hark, let me turn that into a question. Are you placing those libs manually?
[15:59] <kyrofa> Sweet5hark, or is it via stage-packages?
[15:59] <kyrofa> (or from src)
[16:38] <Sweet5hark> kyrofa: https://bugs.launchpad.net/snapcraft/+bug/1548376 <- filed it as a bug. IMHO this needs a whole matrix of "in build-pkg"/"in stage-pkg"/"dep of build-pkg"/"dep of stage-pkg"/"in snap glob"/"in directory matched by snap glob" for "ends up in stage" and "ends up in snap" each ...
[22:17] <wigleworm> anyone around that can help with a snapcraft question
[22:49] <miken> wigleworm: Hi - try just asking your question perhaps. I'm not sure if there are people around who can answer, but you'll have more chance of getting an answer if there are :)
[22:51] <qengho> wigleworm: Yeah, just ask. Don't demand someone commit to answering something in advance.
[23:23] <jdstrand> pindonga (and beuno): hi! can you pull the review tools? this adds all the snap v2 checks I've been working on