/srv/irclogs.ubuntu.com/2016/09/14/#ubuntu-devel.txt

spotteris pepper flash plugin not working in yakkety correctly?  chromium lists it in about://plugins but eveyr site that tries to do flash shows an error of "couldn't load plugin"01:56
Unit193spotter: That's a support question thus should be asked in a support channel such as #ubuntu.  Chromium may have click-to-play, but visit http://www.adobe.com/software/flash/about/ and see if it tells you what version you have.02:01
spotterasked here as its a yakkety issue, but can ask there too, but that page shows same error, "Couldn't load plugin"02:02
Unit193Oooh, sorry yeah. #ubuntu+1.  My bad.02:02
=== pavlushka is now known as Guest78383
=== Guest78383 is now known as pavlushka
mwhudsonxnox: re https://launchpad.net/ubuntu/+source/software-properties/0.96.24.6, gnupg1 is in universe, what's the plan there?04:57
pittiGood morning05:40
cpaelzerGood morning05:48
pittixnox: http://autopkgtest.ubuntu.com/packages/m/mercurial/yakkety/amd64 is another (test-only) regression from gnupg2; do you track these somewhere with bug tags or so?06:42
pittiMirv must have gotten up, autopkgtest infra is getting Qt'ed again :-P07:40
andrewshpitti: could you please have a look at #835648?08:08
ginggsandrewsh: LP or BTS ?08:13
Unit193That number is BTS.08:13
Unit193Debian #83564808:13
ubottuDebian bug 835648 in wpasupplicant "wpasupplicant: suspend takes very long due to problematic system-sleep hook" [Normal,Open] http://bugs.debian.org/83564808:14
ginggsUnit193: thanks08:14
Unit193Sure.08:14
Mirvpitti: mornings! :)08:26
Mirvor lunch time actually08:26
=== enrico_ is now known as enrico
andrewshginggs, pitti: yes, I meant BTS, sorry for the confusion08:37
Unit193andrewsh: Well pretty sure you weren't talking about a bug in tomboy about 'Ubuntu One'08:38
andrewsh:)08:39
pittiandrewsh: so calling wpa_cli suspend takes 10s??08:41
andrewshaccording to the reporter08:41
pittiandrewsh: it's been a while, but we've had the pre/post suspend hooks basically forever (in upstart/pm-utils time it was through /usr/lib/pm-utils/sleep.d/60_wpa_supplicant)08:41
andrewshI see this in my journal too:08:42
andrewshSep 13 18:27:07 nuevo systemd-sleep[29472]: Suspending system...08:42
andrewshSep 13 21:21:55 nuevo systemd-sleep[29472]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory08:42
andrewshSep 13 21:21:55 nuevo systemd-sleep[29472]: System resumed.08:42
pittiso obviously this is a workaround, but so far it seemed it helps more people than it hurts08:42
andrewsh(that's on Ubuntu)08:42
andrewshSep 13 21:21:55 nuevo systemd-sleep[29642]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255.08:42
andrewshadding & to background it sort of helped:08:43
andrewshSep 14 10:18:43 nuevo systemd-sleep[30309]: Suspending system...08:43
andrewshSep 14 10:18:43 nuevo systemd-sleep[30309]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory08:43
andrewshSep 14 10:18:48 nuevo systemd-sleep[30309]: Failed to connect to non-global ctrl_ifname: (nil)  error: No such file or directory08:43
andrewshSep 14 10:18:48 nuevo systemd-sleep[30309]: System resumed.08:43
andrewsh(no error message)08:43
andrewsh(so probably no waiting)08:43
pittiright, but with & it might not actually finish before the suspend happens, so that's a bit pointless08:43
pittiand even detrimental -- you DON'T want wpa_cli suspend to run after resuming08:44
andrewshyep08:44
andrewshthough if followed by resume it shouldn't hurt08:44
andrewshthis makes me think it somehow connects to a wrong socket08:44
andrewshas it says No such file or directory08:45
andrewshpitti: for some strange reason, at the moment systemd-sleep runs, /run/wpa_supplicant is already gone08:59
pittiandrewsh: so maybe a simple check would just be to guard this call with if [ -d /run/wpa_supplicant ] ?08:59
andrewshpitti: maybe09:00
andrewshI don't understand the reason though09:00
andrewshwpa_supplicant is still running09:00
Odd_BlokeIf there's a core dev with a few minutes, a review and merge of this livecd-rootfs change would be much appreciated: https://code.launchpad.net/~daniel-thewatkins/livecd-rootfs/label-function/+merge/30476709:22
doko_kenvandine: please could you prepare your MIR's on yakkety? it's not that we wouldn't have work enough already09:51
xnoxmwhudson, good point.10:01
xnoxpitti, no not tracking things yet. But i guess i should be.10:07
xnoxhttps://bugs.launchpad.net/ubuntu/+source/mercurial/+bug/162342310:07
ubottuLaunchpad bug 1623423 in mercurial (Ubuntu) "gnupg2 autopkgtest regression" [Undecided,New]10:07
xnoxhttps://bugs.launchpad.net/ubuntu/+source/lxc/+bug/162342410:08
ubottuLaunchpad bug 1623424 in lxc (Ubuntu) "lxc autopkgtest regression" [Undecided,New]10:08
pittihttps://bugs.launchpad.net/ubuntu/+bugs?field.tag=gnupg210:08
pittithanks10:08
doko_pitti: about #1622893, I don't think downgrading the gnutls is an option10:09
pittidoko_: right, I wasn't suggesting that; I have a workaround for our test VMs, but it still affects real installs10:11
pittinot a blocker though, I mostly pinged you for the lols10:11
pittithe new version moved from reading /dev/urandom to calling getrandom() which is a good thing from gnutls' POV I suppose; maybe NM just calls something too early and it can be fixed in NM10:12
=== oSoMoN_ is now known as oSoMoN
cpaelzerwas there a reasonable local workaround to bug 1621269 until xenial gets an SRU for it?10:27
ubottubug 1621269 in sbuild (Ubuntu Xenial) "not possible to build yakkety packages because of gpg changes" [High,Triaged] https://launchpad.net/bugs/162126910:27
cpaelzerI remember there was quite some discussion about it, but searching the logfile of the chan wasn't as successful as i'd have hoped10:27
cpaelzertrying to move the sbuild apt keys away as suggsted in the debian linked debian bug10:30
cpaelzerpassing the initial sign of the dummy repo, although I'm not sure this won't cause other pain later on - we will see10:30
Unit193xnox: Also on that note, LP should upgrade them and use the new-ish Signed-By field! :P10:35
=== G_ is now known as G
xnoxUnit193, is there an LP bug open about that?10:36
Unit193xnox: I presume other than 1331914?10:37
directhexwho's in charge of the ppc64le port, nominally? presumably there's someone at IBM spearheading that?11:01
doko_cyphermox, mwhudson, slangasek: accepted subquity. are the hardcoded python2 dependencies in subiquity-tools really intended?11:11
mwhudsondoko_: seems unlikely to me11:14
doko_mwhudson: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/162344811:19
ubottuLaunchpad bug 1623448 in subiquity (Ubuntu) "subiquity-tools has a lot of hard-coded Python2 dependencies" [Undecided,New]11:19
mwhudsondoko_: thanks11:21
doko_xnox: gnupg1 is in component-mismatches now. promote it?12:03
xnoxdoko_, for now yes, ideally i want to drop it from software-properties.12:04
xnoxbut i'm not sure how yet.12:04
doko_xnox: subscribed foundations and promoted12:09
=== _salem is now known as salem_
pittiarges: there was a previously existing isc-dhcp in x-proposed (verified, just reached 7 days today, but causes test regressions); was accepting another one on top of that intended?12:24
pitti(AFAICS this fixes something unrelated)12:24
argespitti: hmm... usually sru-review warns me when that's the case12:30
argespitti: the SRU I accepted was for the same bug12:31
pittiah, so follow-up fix then?12:31
pittithanks12:31
argespitti: checking on this now12:31
argespitti: also I think the network-manager autopkgtest regression is a false negative.12:34
argespitti: and last, i accepted the isc-dhcp into p/t-proposed, not x-proposed.12:36
pittiarges: ah, ok12:36
arges: )12:36
argespitti: oh are you going through the queue too?12:41
pittiarges: no, I just did some releases some 30 mins ago12:41
argespitti: ok12:42
Odd_Blokesmoser: pitti: Are "Transaction order is cyclic" messages from systemd in cloud-init package installation a sign that I don't have a recent enough cloud-init?13:00
Odd_Bloke(This is in yakkety.)13:00
=== xclaesse` is now known as xclaesse
smoserOdd_Bloke, hm..13:09
smoserwhat package installation ?13:10
Odd_Blokesmoser: This is happening when we take an old cloud image and upgrade on boot; I'm freshening the image we use to see if the problem goes away.13:10
smoserOdd_Bloke, ok. let me look some.13:12
pittiOdd_Bloke: oh, could be that init-system-helpers gets upgraded too early/too late or so; I haven't seen dependency loops in fresh installs, but I haven't tried a lot of upgrade scenarios13:15
pittiOdd_Bloke: do you mind posting the logs to bug 1576692?13:16
ubottubug 1576692 in init-system-helpers (Ubuntu Xenial) "fully support package installation in systemd" [High,Fix committed] https://launchpad.net/bugs/157669213:16
pittiOdd_Bloke: (assuming that this also happens on upgrading xenial to xenial-proposed, the changes are pretty well identical)13:16
smoserpitti: http://paste.ubuntu.com/23177905/13:22
pittismoser: ah, that reproduces it?13:22
smoseryeah13:22
smoserhaving old images easily available is nice.13:22
brendandis launchpad in a bad mood or something?13:23
pittiI tried an upgrade with both .services having After=multi-user.target and didn't get into trouble, but different unpack orders can also make this hard to repro13:23
pittibrendand: at least on my end it seems to have a fit pretty well every day for some minutes (feels like an expensive cron job or so)13:24
smoserfull log http://paste.ubuntu.com/23177914/13:24
pittijournal would be good to see too13:28
smoserpitti, well, you can ask me , or you can try it :)13:33
smoseri can get it to you.13:33
smoseri was just checking..13:34
smoserthe latest xenial daily + proposed + package_upgrade=true does not shwo the issue.13:34
smosertrying now with release imae13:34
smoserimage13:34
smoserreleased image seems fine too13:35
smoseractually, pitti...13:37
smoseri think its just that package upgrade with the version of cloud-init that is in the image doens't work.13:37
smoseras is known by that bug.13:37
smoserand we've (i think) fixed the bug.13:37
smoserbut that doesnt fix the image13:37
smoserOdd_Bloke, does that make sense ?13:38
smoseryou're hitting a bug that we've fixed.13:38
Odd_Blokesmoser: Yep, that definitely makes sense; newer image as the base works fine. :)13:40
smoseryeah, but its more than just "its fixed because there are no upgrades to do"13:41
smoserpackage_upgrade and package install was broken, this update to cloud-init fixes it, but you can't have the old cloud-init apply this update due to that bug :)13:42
Odd_Blokesmoser: Yep, understood; we're still installing a bunch of packages and we've stopped seeing failures.14:08
pittismoser: oooh! yes, that makes perfect sense14:10
pitti(sorry, was OTP for a long time)14:10
=== Daviey_ is now known as Daviey
pittismoser, Odd_Bloke: so that means people upgrading from xenial after that SRU lands should *not* run into this15:08
pittiand people upgrading from intra-yakkety, well, yeah, tough luck :)15:09
semiosisOdd_Bloke: are you aware of a reason why the livecd-rootfs hasn't been updated to 2.408.4 in xenial-updates yet?  I marked the bug verification-done about two days ago15:28
semiosisbug 162139315:29
ubottubug 1621393 in cloud-images "xenial64 image (20160907.1.0) has a broken (empty) /etc/resolv.conf" [Undecided,New] https://launchpad.net/bugs/162139315:29
naccsemiosis: iirc, 7 days for srus15:29
nacctypically15:29
naccnot hard and fast15:29
bipulYes, but that's how we can resize our lvm15:29
semiosisnacc: ah ok, thanks15:29
Odd_BlokeThough also: "Not touching package due to block request by freeze (contact #ubuntu-release if update is needed)" from https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html15:29
bipulsorry Shrinking the logical volume.15:30
bipulTo reduce the size of a logical volume, first unmount the file system. You can then use the lvreduce command to shrink the volume. After shrinking the volume, remount the file system.15:30
naccOdd_Bloke: iirc, i saw that too and once it's release that page is not necessary accurate15:30
bipulThat's what i did15:30
Odd_Blokenacc: Ahh, OK.15:30
naccbipul: wrong channel?15:31
bipuloh yes, sorry15:31
semiosisnacc: Odd_Bloke: so we wait a few more days?15:31
naccsemiosis: that would be my recommendation :)15:32
naccsemiosis: it should trickle in just fine15:32
rbasaksemiosis: it gives other users a chance to flag regressions.15:32
semiosisok, then in that case, Odd_Bloke, I would like to post the link to your test build image in the bug.  that sound good to you?15:32
semiosiswill the download link expire?15:34
Odd_Blokesemiosis: I'm not sure what the expiry is; I'd just check if it's working still.15:34
Odd_Blokesemiosis: If it is, it'll probably be good for a while.15:34
semiosisit is working right now15:34
Odd_BlokeThen go for it. :)15:35
semiosisdone.  thanks!15:36
naccrbasak: i'm starting to think that using git-python may have been a mistake. In that, really, I think we can leverage just normal subprocess/`git commands` for most everything and it will be quite a bit faster. Especially for eventual cron usage15:48
naccrbasak: i'll play with that on the side, might just need a little wrapper class for the various commands we need15:48
rbasaknacc: OK. I think we needed the hindsight to have known. I'd be happy with such a switch.15:49
rbasaknacc: I wonder if it's worth seeing if pypy or similar can speed things up, if that's easy and works? Might save you the effort in switching over.15:49
naccrbasak: yep, absolutely -- not an error on our part, we're just not really needing the convenience of git-internals that python-git affords, really15:49
naccrbasak: i'll take a look!15:49
rbasakIs speed the only issue?15:49
argesmwhudson: hey can you give bug 1602243 an SRU template? thanks15:50
ubottubug 1602243 in Ubuntu on IBM z Systems "[16.10 FEAT] Upgrade Docker to newest version 1.12" [Medium,In progress] https://launchpad.net/bugs/160224315:50
naccrbasak: pretty much, as the initial load of an existing repository can take hours15:51
rbasakWow15:51
naccrbasak: as it verifies every object in the git database15:51
naccrbasak: as it's creating an internal reference, i think15:51
naccrbasak: not sure, exactly, but it's very slow15:51
naccand will only get worse as the repos grow15:51
rbasakSounds like we should either fix the library or move away from it.15:53
naccrbasak: yeah, i think the 'fix' is really just a usage thing. I'm not sure if it could be parallelized more15:53
naccrbasak: in that it has does that `git cat-file --batch-check` and `git cat-file --batch` on the repository15:54
naccrbasak: i'll dig into it later15:54
rbasakack15:54
cjwatsonnacc: did you consider python-pygit2?15:57
cjwatsonnacc: that's what the git.launchpad.net backend uses15:57
nacccjwatson: interesting, i'll take a look -- i was trying to use python3 :)15:58
cjwatsonnacc: python3-pygit2, then :)15:58
nacccjwatson: ah yes, thanks!15:59
nacccjwatson: i'll take a look!15:59
cjwatson(we're still on python2 for this because of some details of Twisted, but the library in question supports either)15:59
naccgreat, i'll see if that's any different performance wise for our case15:59
cjwatsonthere are ways to make it hit pathological behaviour, but we certainly haven't noticed anything like what you suggest in general16:00
cjwatsonand we would16:00
nacccjwatson: yep, absolutely16:00
nacccjwatson: thanks again!16:00
cjwatsonnpo16:00
cjwatsoner, np16:00
naccno problem, ole!16:01
rbasakA perfect example of why using public channels is good. Thanks cjwatson :)16:01
naccrbasak: i think i have the patch bits implemented too, fyi -- testing it now16:02
cjwatson:)16:02
cjwatsonhttps://git.launchpad.net/turnip if you need usage examples16:02
smoserpitti, i assume you are gone16:23
smoserbut .. https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/162357016:23
smoserfun.16:23
ubottuLaunchpad bug 1623570 in cloud-init (Ubuntu Xenial) "Azure: cannot start walinux agent (Transaction order is cyclic.)" [High,Confirmed]16:23
smoseri think i have it in hand.16:23
andrewshpitti: and now I see the following: I did suspend, wpa_cli suspend did *not* run; I resume — it does *not* run, and no wifi connection either16:26
andrewshI manually run wpa_cli resume — wpa_supplicant wakes up and reconnects16:26
andrewshI see this in the logs before I ran wpa_cli resume:16:29
andrewshSep 14 18:21:18 nuevo NetworkManager[2944]: <info>  [1473870078.9817] device (wlan0): supplicant interface state: starting -> ready16:29
andrewshSep 14 18:21:18 nuevo NetworkManager[2944]: <info>  [1473870078.9818] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]16:29
=== elbrus_ is now known as elbrus
=== marga_ is now known as marga
naccPharaoh_Atem: ping18:59
Pharaoh_Atemnacc: pong19:00
naccPharaoh_Atem: hey, looking at LP: #162354019:00
ubottuLaunchpad bug 1623540 in php7.0 (Ubuntu Xenial) "If php.ini is incorrect, php-frm starts without warning with default values" [Medium,Triaged] https://launchpad.net/bugs/162354019:00
naccPharaoh_Atem: seems like debian dropped the hlper script, so it affects 16.10 too19:00
naccPharaoh_Atem: do you have any suggestions?19:00
Pharaoh_Atemisn't fpm supposed to just fail anyway?19:01
Pharaoh_AtemI'm not sure how to fix it if it's not working19:02
naccPharaoh_Atem: well, i would have expected fpm to fail, but it doesn't :)19:04
Pharaoh_Atem:S19:05
* Pharaoh_Atem grumbles about php19:05
naccPharaoh_Atem: -t definitely says a line like '# abcd (' is a 'syntax error', but the service still runs19:06
naccPharaoh_Atem: if you have any ideas, i'd appreciate it, i guess the helper script (which can make this work in 16.04, where it's still present) was dropped because "php-fpm often ends with zend_mm_heap corrupted that prevents th service to be (re)started" with no reference to bugs, etc so not sure how common that is19:08
Pharaoh_Atemnacc: I could have sworn that php-fpm has it's own method for checking these things19:11
naccPharaoh_Atem: yeah, i mean '-t' does it19:33
naccPharaoh_Atem: but it's not used currently, perhaps?19:33
Pharaoh_AtemI think that's it19:33
Pharaoh_Atemit's not used by default, I think19:33
Pharaoh_Atemthough, that's completely brain-dead19:33
naccPharaoh_Atem: so i wonder if the systemd script should be using that as a pre-exec19:34
naccor whatever19:34
Pharaoh_Atemit probably should19:34
naccbut i mean, that's what the wrapper script basically did (incorrectly, though)19:34
Pharaoh_Atemwell, the wrapper script is basically unnecessary, right?19:34
naccPharaoh_Atem: unclear :)19:34
naccPharaoh_Atem: i guess so19:34
nacclet me see what else it does19:34
naccPharaoh_Atem: it also did something with tmpfiles?19:39
nacc /usr/lib/tmpfiles.d/php7.0-fpm.conf19:39
* Pharaoh_Atem shrugged19:39
Pharaoh_Atemwhy not define tmpfiles in the service file?19:39
Pharaoh_Atemit supports that19:39
nacci have no idea19:39
naccok, i'll play with adding a call to php7.0-fpm -t in the ExecStartPre19:39
Pharaoh_Atemdoes invocation with -t lead to a running interpreter?19:40
Pharaoh_Atemor does it exit after the check?19:40
naccit always exits, afaict19:40
naccsigh, but it exits successfully even if the syntax error occurs :)19:41
Pharaoh_AtemI repeat: php is brain-dead19:41
Pharaoh_Atem:)19:41
tumbleweedwin 3320:17
pittismoser: sorry, was just gone for dinner and basketball, looking20:22
smoserpitti, you are allowed to walk away from the computer20:23
smoserjust not for more than 6 minutes20:23
smoserplease take a look at http://pad.lv/1623570 . i've uploaded to both yakkety and xenial20:24
ubottuLaunchpad bug 1623570 in walinuxagent (Ubuntu) "Azure: cannot start walinux agent (Transaction order is cyclic.)" [High,In progress]20:24
smoserbut would like your thoughts, and can nack it and replace it if needed.20:24
pittismoser: 6 minutes? *now* I know what "fast food" means!20:27
=== salem_ is now known as _salem
mwhudsonarges: done23:28
naccPharaoh_Atem: well, i figured out *why* php7.0-fpm starts successfully even with the -t check. the -t check only applies to parsing of php-fpm.conf, not php.ini23:31
naccPharaoh_Atem: as the php.ini parsing happens at a top-php-level across all sapis23:31

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!