[03:33] <pitti> Good morning
[03:33] <pitti> arges, bdmurray: can I somehow bribe you to process the systemd SRU in vivid? people keep asking for the fixes
[07:00] <dholbach> good morning
[07:03] <seb128> hey dholbach
[07:04] <dholbach> salut seb128
[08:30] <pitti> smoser, infinity: wolfe-* are all AWOL; can you please hit the magic reboot button?
[09:01] <jamespage> @pilot in
[09:01]  * dholbach hugs jamespage
[11:21] <jamespage> cyphermox, hey - are you intending on sponsoring the SRU's for bug 1401141 ?
[11:21] <jamespage> I took a look through but I'm not competent enough to assess them from a regression potential perspective.
[12:15] <popey> Is there any way to debug long shutdown times? My desktop takes anything up to 30 minutes to shutdown
[12:17] <mgedmin> popey, for me it was swapoff -a taking AGES
[12:18] <mgedmin> but anyway /usr/share/doc/systemd/README.Debian has a section titled "Debugging boot/shutdown problems"
[12:18] <mgedmin> (AGES = ~25 minutes to free up 4 gigs of swap space from my SSD)
[12:24] <popey> interesting!
[12:25] <popey> mgedmin: I just manually did a "sudo swapoff -a" then "sudo reboot" and it rebooted instantly!
[12:29] <xnox> popey: reboot != shutdown... in systemd...
[12:30] <xnox> it does tricks.
[12:30] <popey> ah
[12:36] <popey> I may have fixed it! Removed bootchart.
[12:37] <doko> pitti, https://jenkins.qa.ubuntu.com/job/wily-adt-python2.7/lastBuild/ retry?
[12:37] <xnox> popey: horum, old or new one?
[12:37] <xnox> we probably should remove the old one.
[12:37] <popey> uh
[12:37] <popey> I'm on wily
[12:37] <popey> so I'd hope it's "new"?
[12:37] <xnox> popey: systemd-bootchart or bootchart =)
[12:37] <popey> bootchart
[12:38] <xnox> popey: it got rewritten and merged into src:systemd
[12:38] <xnox> ack.
[12:38] <popey> Fancy that.
[12:38] <popey> ok, so during the upgrade, why didn't bootchart get removed?
[12:38] <ogra_> systemd has builtin bootchart
[12:38] <popey> and replaced?
[12:38] <xnox> pitti: we should probably make bootchart not do anything when booting systemd.... if that can be detected. ^
[12:38] <ogra_> sadly the most important info (iowait) is missing from that
[12:38] <popey> my pc has been slow to boot up/down for months, didn't realise it was this.
[12:39] <xnox> popey: because we need old bootchart for upstart. new one is only usable with systemd as pid1.
[12:39] <ogra_> the only actual useful info you get in bootchart are the graphs at the top
[12:39] <popey> right, so it shouldn't run when systemd is in use then?
[12:39] <popey> (ideally)
[12:39] <ogra_> the rest is just shiny shiny
[12:39] <popey> yeah, and it doesn't even generate images anymore
[12:39] <popey> you have to post-process
[12:39]  * ogra_ hopes someone extenbds the systemd tool to that one day
[12:39] <popey> last bootchart I have is 2 months ago.
[12:40] <popey> ah well, fast boot time and shutdown trumps charts telling me it's slow :)
[12:40]  * ogra_ notes popey doesnt seem to read ubuntu-users anymore 
[12:40] <popey> nope
[12:41] <ogra_> popey, https://lists.ubuntu.com/archives/ubuntu-users/2015-May/280956.html
[12:41] <cyphermox> jamespage: I was, but you can sponsor it if you want, that was blocked by another trusty SRU as I recall
[12:41] <cyphermox> (no longer is)
[12:54] <pitti> doko: running
[13:07] <pitti> doko: succeeded now (that is, until we switch back to running tests in the cloud :) )
[13:08] <doko> quick, quick, migrate ...
[13:23] <jamespage> cyphermox, ack - so from your perspective the proposed changes looks sane?
[13:23] <cyphermox> jamespage: yup
[13:23] <jamespage> cyphermox, ok
[13:23]  * jamespage puts pilot hat on
[13:23] <pitti> xnox: does it anything? I thought it just had an upstart job
[13:24] <xnox> pitti: i believe it has init scripts as well, and initramfs hooks no? for popey it delays shutdown.
[13:24] <pitti> xnox: ah, then this should indeed be fixed :)
[13:29] <jamespage> tinoco, hey - dealing with your IB dhcp updates now
[13:30] <tinoco> jamespage: awesome. let me know if you need anything
[13:30] <tinoco> tks
[13:41] <smoser> pitti, looking
[13:58] <smoser> pitti, all should be back up
[14:02] <pitti> smoser: great, thank you!
[14:03] <pitti> smoser: what was it, OOI?
[14:03] <smoser> there was (apparently announced) power downtime
[14:03] <smoser> and that system only has single power
[14:03] <smoser> so it went down this wekeend.
[14:09] <pitti> smoser: ah, so good old mundane "real physics" problem, not another one of these pesky kernel hangs that used to haunt us :)
[14:09] <attente> hi, i just did a dist-upgrade, but my machine is no longer passing the boot stage
[14:10] <attente> wondering if anyone else has this problem? this is my boot.log: http://paste.ubuntu.com/11521041/
[14:10] <smoser> pitti, yeah, the wireless power in that lab is flakey
[14:10] <pitti> smoser: wireless .. power? AKA "everyone who walks through gets their brain fried"? :-)
[14:11] <pitti> attente: err, a phone with systemd? or a desktop with powerd? (both is rather unusual)
[14:11] <attente> pitti: it's a desktop
[14:11] <pitti> attente: that powerd.service will time out after 90s, then it should continue to boot, doesn't it?
[14:11] <seb128> pitti, desktop with powerd is not un-usual if you work on unity8
[14:11] <pitti> attente: and please do purge powerd -- it doesn't work without android
[14:12] <attente> pitti: it times out but doesn't continue on
[14:12] <attente> pitti: i had to manually start lightdm
[14:12] <pitti> Reached target Graphical Interface
[14:12] <pitti> hmm
[14:12] <pitti> attente: then something else is wrong, too -- systemctl status lightdm?
[14:13] <smoser> pitti, it was a bad joke.
[14:13] <pitti> (that's only a partial log, complete "journalctl" would be more helpful)
[14:13] <pitti> smoser: (I figured, hence the smiley)
[14:13] <attente> pitti: http://paste.ubuntu.com/11521648/
[14:14] <pitti> attente: ah, you manually started it now?
[14:14] <attente> pitti: yep
[14:14] <pitti> attente: so, would like to see that before you do that
[14:14] <attente> sure
[14:15] <pitti> attente: can you "sudo systemctl disable powerd" for now to get that pesky 90s timeout out of the way, and reboot and check lightdm's status?
[14:15] <pitti> we should probably modify the unit to not start on a desktop
[14:27] <attente> pitti: http://paste.ubuntu.com/11521786/ journalctl
[14:28] <attente> pitti: http://paste.ubuntu.com/11521794/
[14:28] <pitti> attente: looks fine?
[14:28] <pitti> systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
[14:28] <pitti> oh, indeed -- I didn't read far enough
[14:29] <pitti> attente: anyway, that's a SEP from my point of view :) I suppose the greeter session crashes?
[14:29] <attente> SEP?
[14:29] <attente> i'm not sure
[14:29] <pitti> 10:15:50 attente systemd[1294]: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0)
[14:29] <pitti> 10:15:50 attente lightdm[1290]: pam_unix(lightdm-greeter:session): session closed for user lightdm
[14:29] <pitti> so yes, that session didn't last very long
[14:30] <attente> oh
[14:30] <pitti> attente: anything in /var/log/lightdm?
[14:30] <pitti> attente: "somebody else's problem"
[14:30] <attente> lol
[14:32] <attente> pitti: is it a bit strange that the greeter works when i manually start it though?
[14:35] <pitti> attente: yes, for sure; maybe lightdm starts too early, and it's depending on something else to be up first? hard to say without knowing why the session crashed
[14:35] <attente> pitti: ok, thanks for the pointers :)
[14:41] <jamespage> tinoco, all in the proposed queue for SRU team review - thanks!
[14:41] <jamespage> @pilot out
[14:48] <tinoco> jamespage: nah, tku!!
[15:53] <pitti> cjwatson, wgrant: how can we change the import source of https://code.launchpad.net/~registry/systemd/master ? It's https://github.com/systemd/systemd.git now
[15:54] <cjwatson> pitti: Is that just a straightforward repository move?
[15:54] <pitti> cjwatson: yes, it was imported to github for using pull requests mostly
[15:54] <pitti> cjwatson: but the same branch in spirit (just a bunch of newer commits since yesterday)
[15:55] <cjwatson> pitti: Changed
[15:55] <pitti> cjwatson: danke
[16:00] <pitti> cjwatson: import finished, looks good
[16:00] <cjwatson> cool
[16:09] <pitti> slangasek, jodh: do you plan to merge Debian's systemd with Ubuntu? in particular, the split-out upstart-sysv package, so that this becomes usable as an "alternative" init system?
[16:09] <seb128> pitti, systemd?
[16:09] <seb128> you mean upstart?
[16:10] <pitti> seb128: erk, of course I do
[16:10] <pitti> slangasek, jodh: s/systemd/upstart/ of course -- gah :)
[16:10] <seb128> ;-)
[16:12] <pitti> ogra_: dude, you are all over G+ and you are making me dizzy!
[16:12] <pitti> ogra_: https://plus.google.com/u/1/+AlanPope/posts/UN9HYBM6B4c :)
[16:12]  * pitti hugs ogra_, fantastic loading image!
[16:12] <pitti> popey: ^ ++
[16:12] <ogra_> pitti, lol, yeah
[16:13] <popey> haha
[16:34] <slangasek> pitti: no plans for any work on the upstart packages.  Do you mean enabling upstart as an alternative in Ubuntu?
[17:06] <barry> doko: are you looking at the promotion blocks for python3.4 and 3.5?  if not, i will spend some time on the test failures, but i don't want to duplicate effort
[17:17] <LocutusOfBorg1> how is going libjsoncpp MIR?
[17:17] <LocutusOfBorg1> I see this bug https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1218220
[17:17] <LocutusOfBorg1> should I open another one?
[17:18] <LocutusOfBorg1> (needed for cmake 3.2.*)
[17:23] <slangasek> LocutusOfBorg1: does the library now have sane soname versioning?
[17:23] <slangasek> that was the reason for the reject before.  If that hasn't been addressed...
[17:33] <LocutusOfBorg1> slangasek, sorry I don't get the question, it has a soname https://packages.debian.org/sid/amd64/libjsoncpp0/filelist
[17:33] <LocutusOfBorg1> 0.6.0
[17:34] <LocutusOfBorg1> I don't know if it is enough
[17:34] <LocutusOfBorg1> (moreover there is a new package in debian NEW queue)
[17:39] <LocutusOfBorg1> maybe you mean https://github.com/open-source-parsers/jsoncpp/issues/147
[17:41] <LocutusOfBorg1> seems that they are fixed if I read correctly
[17:45] <rbasak> Is someone handling the nettle transition? I want to upload a squid3 merge soon that'll get stuck in it, but it looks like it'd be needed for the transition anyway