[04:43] <pitti> Good morning
[08:02] <Laney> hey hey!
[08:09] <seb128> hey Laney, how are you? happy friday!
[08:10] <Laney> hey seb128, happy friday!
[08:10] <Laney> I just got rained on while having my breakfast outside
[08:11] <seb128> :-/
[08:12] <Laney> how's nlfrnlfr?
[08:14] <seb128> good! no rain on us here
[08:14] <seb128> oh, mterry is still on european tz ;-)
[08:15] <mterry> seb128, :)
[08:16] <mterry> seb128, my mir packaging (~mir-team/mir/snappy-packaging) has a top-level wrapper script that waits until agetty is up
[08:16] <seb128> mterry, is there an easy way to tell if that's the issue I'm having?
[08:16] <seb128> I get a working unity-greeter
[08:17] <mterry> seb128, I thought mir wasn't working for you?
[08:17] <mterry> seb128, do you have a VT1 that you can physically see?
[08:17] <mterry> seb128, the issue I saw was that on startup, mir would come up (see cursor), then the login prompt would appear
[08:17] <mterry> seb128, that means we lost the race
[08:18] <seb128> mterry, it's just that logging into an unity8 session fails, .cache/upstart/unity8.log complains about "ERROR: QMirServer - Mir failed to start"
[08:18] <seb128> mterry, http://paste.ubuntu.com/11763124/
[08:18] <seb128> mterry, well define "mir"
[08:19] <seb128> the system boots to a greeter
[08:19] <seb128> that it working but X
[08:19] <seb128> it's unity-greeter
[08:19] <seb128> u-s-c is started
[08:20] <seb128> the usc log is http://paste.ubuntu.com/11773781/
[08:20] <seb128> mterry, I've been able to start manually unity8 yesterday rendering to a mir_demo_server
[08:20] <seb128> just using usc doesn't work
[08:21] <seb128> but lightdm has warnings about "Error using VT_ACTIVATE 7 on /dev/console: Inappropriate ioctl for device"
[08:21] <seb128> so maybe it's an issue with vt changes...
[08:23] <mterry> seb128, sorry, in IoM and in meetings off and on
[08:23] <seb128> mterry, yeah, I assumed so, no worry
[08:24] <seb128> I would still appreciate if you read the backlog when you have spare cycles, and maybe comment ;-)
[09:33] <seb128> pitti, hey, any hint on debugging systemd start hanging?
[09:33] <chrisccoulson> seb128, I fixed that Oxide / Unity 8 bug yesterday http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/1147 :)
[09:33] <seb128> chrisccoulson, hey, excellent!
[09:33] <seb128> chrisccoulson, how are you btw? happy friday ;-)
[09:34] <seb128> pitti, I booted with systemd.debug-shell and on vt9 I did systemctl status and get
[09:34] <chrisccoulson> seb128, I'm not too bad thanks. Had a late night last night, so a bit tired
[09:34] <chrisccoulson> how about you?
[09:34] <seb128> "starting; 15 queued jobs"
[09:34] <seb128> chrisccoulson, I'm good thanks ;-)
[09:34] <seb128> pitti, ok, it eventually started, so I guess a 90s timeout somewhere
[09:35] <pitti> seb128: "systemctl list-jobs" shows you what's hanging
[09:35] <pitti> seb128: then you can inspect the "running" ones with status -l foo.service
[09:37] <seb128> pitti, now it booted, I guess I need to go through the journal
[09:37] <pitti> seb128: if you have a persistant one, yes; you should see the 90s gap in the log
[09:37] <pitti> if not, it shoudl also be in syslog
[09:44] <seb128> seems to be cloud-init hitting connection refused and timeouts
[09:44] <seb128> pitti, danke
[09:44] <pitti> seb128: or searching for an user-data ISO which isn't there?
[09:44] <seb128> chrisccoulson, when is that fix going to land in wily?
[09:46] <seb128> pitti, nothing like that in the logs
[09:46] <seb128> but url_helper warnings about trying to call http://109-04-04/...instance-id
[09:47] <chrisccoulson> seb128, I've added a task to backport it to the 1.8 branch, which is the next release
[09:47] <seb128> which gives request error connection aborted no route
[09:47] <chrisccoulson> That's still a could of weeks away though
[09:47] <seb128> chrisccoulson, k
[09:47] <chrisccoulson> (whenever Chrome 44 is released, basically)
[09:53] <seb128> bah, snappy personal regressed somehow this week :-/
[09:53] <seb128> boot timeout, login with ubuntu user doesn't work :-/
[17:01] <Laney> happy weekend all!
[17:01] <Laney> busy day ;-)
[17:04] <ogra_> enjoy !
[17:05] <seb128> Laney, thanks, you too!
[18:04] <bregma> seb128, did you get those Unity8 startup issues resolved?
[18:04] <seb128> bregma, yes, unity8 starts fine in fact
[18:05] <seb128> it's a stupid bug
[18:05] <bregma> what was it?
[18:05] <seb128> you start on vt7, enter your password, it acts like it was logging in, display blank screen and cursor and back to greeter
[18:05] <seb128> so it looks like login/session failed
[18:05] <seb128> in fact usc starts on vt8 and wait there
[18:05] <seb128> if you switch to vt8 unity8 loads
[18:06] <seb128> now unsure why the vt switch doesn't happen
[18:06] <seb128> I just emailed robert_ancell in case he has some debugging suggestion
[18:06] <bregma> hmm, problem description rings a bell though
[18:08] <bregma> seb128, does that means there is a snappy personal image that runs if you manually switch VTs?
[18:14] <seb128> bregma, yes
[18:14] <bregma> sweet, thanks
[18:15] <seb128> well I didn't unlock but the greeter works
[18:15] <seb128> I didn't unlock because I'm working in a virtual-manager and swipe from the side to display the unlock doesn't seem to work
[18:15] <seb128> need to try later on real hwd
[18:15] <seb128> "greeter" being the in session unity8 lock
[18:15] <seb128> yw!
[18:16] <seb128> bregma, you can "udf personal rolling --channel edge --output img.img" on wily to build an image
[18:16] <seb128> or on vivid, just need to goget-ubuntu-touch from wily
[18:17] <seb128> if it rings enough bell to remember what is causing the non vt switch or how to fix it let me know ;-)