[00:42]  * cyphermox -> back
[02:10] <imgbot> [02:25] <cyphermox> err
[02:53] <jhodapp> cyphermox, can I get a silo for line 78 please?
[03:10] <imgbot> [03:17] <charles> ah bfiller, thanks for picking up silo 12
[03:25] <imgbot> [03:25] <imgbot> [04:03] <cyphermox> jhodapp: certainly
[04:15] <imgbot> [04:15] <imgbot> [08:09] <vila> trainguards: It seems that devel-poposed #74 mako and #81 krillin fail to install on phones in the lab, is this known ?
[08:18] <sil2100> vila: hey, what do you mean 'fail to install'?
[08:18] <sil2100> vila: yeah, I heard some info from other people about that
[08:18] <jibel> vila, yes someone said that too on the ML
[08:19] <vila> sil2100: yeah, what jibel said + I'm seeing makos and krillins stuck at:
[08:19] <vila> 2015/01/23 05:25:19 Rebooting into recovery to flash
[08:19] <vila> + adb -s 04ed727c929709ba wait-for-device
[08:19] <sil2100> Let me see what landed
[08:20] <vila> sil2100: thanks
[08:22] <sil2100> vila, jibel: damn, this image had a lot - a new lxc, new udev, new lightdm, new gcc/glibc
[08:23] <vila> meh, and tha's #82 for krillins soryy
[08:42] <sil2100> Damn, my current device is busy so to say, as I'm testing Qt5.4 on it
[08:42] <sil2100> But let me re-flash and try seeing what's up
[09:01] <mzanetti> sil2100: good morning. sorry have to ask for a reconfig of 14. seems we have systemsettings-components dep in there
[09:09] <sil2100> mzanetti: done o/
[09:11] <mzanetti> sil2100: thank man
[09:30] <popey> aaaargh
[09:32] <popey> I give up.
[09:33] <sil2100> popey: awww!
[09:33] <sil2100> Google hangout problems?
[09:43] <pstolowski> trainguards hello, can you check the changes in landing-15 and land it?
[09:50] <sil2100> pstolowski: hey! Been in a meeting, dealing with this in a moment :)
[09:50] <ogra_> silly browser
[09:50] <pstolowski> sil2100, thanks
[09:56] <vila> sil2100: any news on the devel-proposed images ?
[09:57] <sil2100> vila: not yet, only recently I got my phone bricked, will investigate a bit in a moment
[09:57] <vila> sil2100: ack
[09:57] <sil2100> (had trainguard stuff to do)
[09:58] <dbarth> hi trainguards; silo 017 (vivid) can be deleted, we landed the branch from another silo already
[09:59] <sil2100> dbarth: ACK
[10:01] <sil2100> pstolowski: looking good, publishing - took a while since someone sorted debian/control dependencies ;)
[10:03] <pstolowski> sil2100, np.. oh, let me take a look what's unapproved
[10:04] <pstolowski> sil2100, one branch got updated in the meantime.. approved now
[10:11] <sil2100> Updated?
[10:11] <sil2100> pstolowski: if a branch got updated we'd need the packages rebuilt
[10:12] <sil2100> pstolowski: otherwise not only will we be landing outdated stuff, but also the merge will fail
[10:13] <pstolowski> sil2100, uh, you're right, thanks!
[10:30] <mzanetti> sil2100: hey, yesterday kgunn added u-s-c to my silo, but then we pulled it out again because it wasn't ready. Now I have the package in the silo and it fails to build: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-014/+packages
[10:30] <mzanetti> is that a problem?
[10:30] <mzanetti> the others seem to build fine
[10:33] <sil2100> mzanetti: u-s-c seems to build fine there - but let me remove it from the PPA for you, if you want
[10:33] <sil2100> In the past it was done by CI Train, but after some modification the train stopped doing that
[10:35] <mzanetti> ah, ok
[10:35] <sil2100> mzanetti: you want me to delete it?
[10:36] <mzanetti> sil2100: to be clear, u-s-c stands for unity-system-compositor
[10:36] <sil2100> Aaaa
[10:36] <mzanetti> not the ubuntu-settings-components package in there
[10:36] <mzanetti>  :D
[10:36] <sil2100> ... ;)
[10:36] <mzanetti> only saw it now that it matches for both :D
[10:36] <sil2100> Ok, should I remove the compositor then?
[10:36] <mzanetti> yes please
[10:37] <sil2100> mzanetti: it's normal it fails to build on those two arches btw.
[10:37] <sil2100> Missind mir deps IIRC
[10:37] <mzanetti> right. just caused the dashboard to report the silo as failed
[10:37] <mzanetti> so I wasn't quite sure about it
[10:40] <dbarth> ogra_: ping? sorry to bother you again; it's about the signon extension
[10:41] <ogra_> dbarth, yeah, sorry i'll try to get to it today, snappy is keeping me busy, havent worked on phone stuff this year yet
[10:43] <dbarth> ogra_: ok, nw and thanks for taling that on your plate; i just want to make sure it's on your radar
[10:43] <dbarth> let me know if you need me to do anything else
[10:44] <ogra_> you, bzoltan_ and silo11 are on my phone radar for today :)
[10:47] <rsalveti> ogra_: do you know if someone already investigated why we can't boot the latest image?
[10:47] <rsalveti> vivid
[10:48] <ogra_> rsalveti, see devel
[10:48] <pstolowski> sil2100, i have rebuilt and retested the affected package in silo 15, should be good now
[11:01] <bzoltan_> ogra_:  so no chance to push an update for the sdk seeds
[11:03] <ogra_> bzoltan_, oh, why ? what happened ?
[11:05] <bzoltan_> ogra_:  Sorry ... I though you write to me that "silo11 are on my phone radar for today" ... I missed the "and"
[11:27] <sil2100> jibel: hey, regarding the regression in gallery... does it only happen when the SD card is full of pictures, or is it also the same case when the internal storage is full?
[11:28] <jibel> sil2100, it works better with internal storage, but you cannot store as many photos than on a 16G SD Card. And maybe it's faster too.
[11:28] <sil2100> jibel: ah, ok, since I was wondering if actually backing up SD support will help
[11:29] <sil2100> (for me lack of SD support in gallery or camera would be basically a ship stopper)
[11:30] <jibel> sil2100, it's also a ship stopper if you have support but it doesn't work
[11:30] <sil2100> Yeah, just saying that reverting won't help, as we need this fixed anyway
[11:30] <jibel> sil2100, I think someone from bfiller's team should have a look, if there is no obvious fix revert and reland it in a later milestone
[11:31] <sil2100> It's up for management to decide, but for me that's a rather crucial feature from the POV of a customer
[11:31] <sil2100> Just saying
[11:31] <victorp> sil2100, hi
[11:31] <sil2100> victorp: hey!
[11:32] <victorp> so we cant ship as it is now
[11:32] <sil2100> victorp: what's the decision? Can we ship without no support for SD-cards in gallery?
[11:32] <victorp> I am not sure that is true about not having sd support for camera and gallery
[11:32] <sil2100> *without
[11:32] <jibel> sil2100, you'll have the case where users take the SD card from a previous phone, already loaded with photos and it'll just won't work
[11:33] <sil2100> jibel: I'm not saying we want to release it like it is now, I'm saying we don't want to release it with no support as well
[11:33] <victorp> sil2100, it is not great but we cant ship a broken phone
[11:33] <victorp> sil2100, right but if we back it out, that doesnt mean we should not keep working on it
[11:33] <sil2100> Sure
[11:34] <victorp> maybe wait til bfiller and pmcgowan are up, but I am for backing it out at the mo
[11:36] <sil2100> From what I see it's around since some time, so we'll have to wait for bfiller anyway since I probably can't revert it 'the packaging way'
[11:36] <sil2100> Too many changes inbetween
[11:36] <sil2100> We'll need bfiller to revert it himself
[11:38] <ogra_> victorp, sil2100, i once understood that we wanted to wait with implementing SD access in apps until the new planned SD card framework is there ... seems that didnt happen
[11:38] <ogra_> (so that not all apps have their own implementation of accessing the card)
[11:39] <victorp> sil2100, I think sd card support on the gallery and camera just landed though
[11:40] <victorp> but yeah, might more "commenting" code out..
[11:40] <victorp> what I dont understand is why the camera freezes at boot.. what is the camera doing with the sd card?
[11:41] <sil2100> victorp: right, but sadly it landed with a full vivid sync, so with many many changes - best if bfiller just removes the SD bits and leaves all other bugfixes
[11:43] <ogra_> victorp, on "boot" or on app startup ?
[11:43] <victorp> app startup
[11:43] <victorp> sil2100, ah yes, ofcourse
[11:43] <victorp> forgot that..
[11:43] <victorp> sil2100, maybe there is a quick fix
[11:44]  * victorp hope
[11:44] <victorp> s
[12:03] <bzoltan_> sil2100:  the sil10 is mature for publishing ... it brings cool feature
[12:04] <sil2100> ;)
[12:04] <sil2100> Oh, upgrade notification!
[12:04]  * sil2100 publishes
[12:05] <mzanetti> sil2100: something is still wrong on silo 14... the ppa and the spreadsheet hold unity8 and ubuntu-settings-components
[12:05] <mzanetti> while the dashboard shows unity8 and ubuntu-system-compositor
[12:05] <sil2100> huh
[12:05] <sil2100> mzanetti: did you reconfigure after removing ubuntu-system-compositor?
[12:05] <mzanetti> sil2100: no, you did today morning
[12:05] <mzanetti> haven't changed the spreadsheet since
[12:06] <mzanetti> then the dashboard actually was fine
[12:06] <sil2100> mzanetti: hm, maybe it didn't 'catch it'
[12:06] <mzanetti> but now after it finished building the dashboard is wrong again
[12:06] <sil2100> Let me retry
[12:07] <mzanetti> I tried to reconfig now in the hope it would just update the dashboard without actually changing the silo. but wouldn't allow me
[12:09] <mzanetti> now it looks better, thanks
[12:10] <sil2100> Not sure what happened before that
[12:10] <sil2100> yw!
[12:11] <sergiusens> victorp: sil2100 the camera doesn't need to land in vivid, just in the click store; the landing into the archive is a legacy part of a process
[12:11] <sil2100> sergiusens: yep, I know
[12:12] <sergiusens> and it an update to the app requires no image build
[12:12] <sergiusens> of course that doesn't solve first boot xp
[12:30] <sil2100> tvoss: hmm
[12:49]  * sil2100 goes off to lunch
[12:49] <sil2100> o/
[13:07] <brendand> sil2100, i need something on the spreadsheet to indicate a row concerns a click package landing
[13:08] <brendand> sil2100, will it contain the full name of the click package?
[13:09] <brendand> sil2100, i can always check it ends with .click
[13:11] <rsalveti> sil2100: ogra_: so what can we do with lxc?
[13:11] <rsalveti> should we revert that? wait stgraber to show up?
[13:12] <ogra_> i would do the latter
[13:12] <rsalveti> would be nice to fix that before the weekend starts
[13:13] <ogra_> yep
[13:18] <jibel> bfiller, I'm rejecting silo 009, the dialer crashed.
[13:36] <rsalveti> tvoss: lool: you need to update lxc-android-config at https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-017
[13:36] <rsalveti> there was another upload in RTM since that package got available in there
[13:36] <rsalveti> 11 days ago :-)
[13:36] <tvoss> rsalveti, ah, thanks for the hint
[13:39] <brendand> sil2100, can you confirm that lines for click packages will have a 'request ID'?
[13:48] <Ursinha> brendand: how are you using citrain for clicks if that sends packages to PPAs? how is that going to work? (honest question)
[13:49] <brendand> Ursinha, sil2100 is dealing with the citrain side of things. i'm just modifying the code to create trello cards
[13:51] <Ursinha> sil2100: are you modifying citrain to also build clicks?
[13:53] <Ursinha> sil2100: from the last time I've spoken with robru, he was intending to work on the last bits to migrate away from the spreadsheet, adding more functionality to citrain means more things will have to be put in place to support the migration. if he's already aware of this change then it's fine :)
[13:53] <om26er> Chipaca, Hi!
[13:54] <Chipaca> om26er: verily!
[13:54] <jibel> Ursinha, no, the goal is to just store the information in the spreadsheet so we can track landings of click packages, devices and custom tarballs.
[13:54] <om26er> Chipaca, can you help me with silo 7 testing ?
[13:54] <Chipaca> om26er: sure
[13:54] <jibel> Ursinha, nothing fancy
[13:54] <Ursinha> jibel: thanks for the information
[13:54] <Chipaca> om26er: what are you looking to test?
[13:55] <om26er> Chipaca, what exactly do I need to verify the fix ? Also do I not need to run the TestPlan for it ? (As its not linked in the spreadsheet)
[13:55] <om26er> well, more or less I need to verify the bug is fixed.
[13:55] <Chipaca> om26er: you can run the test plan if you want, but it doesn't cover the issue this fixes
[13:55] <Chipaca> right
[13:55] <Chipaca> om26er: well, in a deep sense the bug is _not_ fixed
[13:55] <Chipaca> om26er: but i can show you how to reproduce it, and show you that after this change you can no longer reproduce it
[13:56] <Chipaca> om26er: we do still have further work to do on this, but it's big enough that we decided to release with this change first, which makes it a lot less likely
[13:57] <om26er> Chipaca, from what I understand we are fixing the issue to some extend. So perhaps the steps should be added to the TestPlan as well ?
[13:58] <om26er> *extent rather.
[13:58] <Chipaca> om26er: maybe, but i'm not sure it's a good idea. let me help you do it this time, and if you think it's reasonable as part of a test plan i'll do it
[13:58] <sil2100> rsalveti, ogra_: so the package at fault was lxc in the end?
[13:59] <sil2100> rsalveti, ogra_: we could prepare everything for a revert and wait for stgraber to appear
[13:59] <ogra_> sil2100, yes, we're waiting for stgraber
[13:59] <sil2100> brendand: it won't have an UID I think, since it's just a hack - you need to have that?
[13:59] <lool> rsalveti, tvoss: Thanks
[13:59] <ogra_> might just be that we need to simply adjust something in our setup for the new version
[13:59] <lool> rsalveti: yeah I didn't notice because I was dpkg -i installating it
[14:00] <sil2100> Ursinha: no, the CI Train will not build clicks ;) No modifications in the train, it's just a convinience thing requested by QA
[14:01] <Ursinha> sil2100: understood, thanks :) though the spreadsheet will now be used to track these requests, so we will have to add same functionality to the spreadsheet replacement UI to allow that
[14:02] <sil2100> Ursinha: sure, but that's not critical to have right now, it's a new addition that doesn't have to be covered instantly
[14:02] <brendand> sil2100, it would make things easier for me but if it makes things much harder for you i can always work around it
[14:02] <Ursinha> brendand: sil2100, that's fine, really, I'm just trying to make sure that changes are well communicated so there are no surprises after
[14:04] <sil2100> brendand: hm, let me think about that, since the UID would have to be auto-generated here
[14:04] <sil2100> But it's doable
[14:05] <jibel> Ursinha, the goal is to use the same workflow for any type of landing independently of the format of the packages.
[14:05] <Ursinha> jibel: that's what we want to do :)
[14:05] <jibel> Ursinha, good :)
[14:06] <om26er> Chipaca, ok, I'll wait for the procedure to verify the fix.
[14:07] <Chipaca> om26er: it's short-form described in the spreadsheet
[14:08] <Chipaca> om26er: let me know if that's not enough
[14:11] <om26er> Chipaca, that is not clear enough. which 'push client' should be running ?
[14:12] <pstolowski> trainguards hello, can we get a silo for line #82?
[14:15] <sil2100> boiko: could you top-approve https://code.launchpad.net/~thomas-voss/location-service/allow-for-disabling-providers/+merge/241707 ?
[14:15] <sil2100> boiko: wait
[14:15] <sil2100> boiko: https://code.launchpad.net/~boiko/telephony-service/rtm-fix_1398427/+merge/246996 I meant
[14:15] <sil2100> (wrong paste in the pastebin)
[14:15] <boiko> sil2100: yep
[14:15] <sil2100> Thanks
[14:16]  * mzanetti disagrees
[14:17] <sil2100> pstolowski: should be assigned!
[14:17] <mzanetti> boiko: hmm strange... I'm quite sure I approved them already yesterday
[14:18] <Chipaca> om26er: stop ubuntu-push-client && /usr/lib/ubuntu-push-client -log_level debug
[14:20] <Chipaca> om26er: stop ubuntu-push-client && /usr/lib/ubuntu-push-client/ubuntu-push-client -log_level debug
[14:20] <Chipaca> om26er: sorry for the first one :)
[14:21] <om26er> Chipaca, I figure that. But how do I actually verify the bug/fix ? Is there a way to create dummy push notifications ?
[14:22] <Chipaca> om26er: ah! give me a moment please
[14:24] <Chipaca> om26er: on the phone, assuming you have telegram installed, do:
[14:24] <Chipaca> gdbus call -e -d com.ubuntu.PushNotifications -o /com/ubuntu/PushNotifications/com_2eubuntu_2etelegram --method com.ubuntu.PushNotifications.Register com.ubuntu.telegram_telegram
[14:24] <Chipaca> om26er: take the token that returns, and on a computer where you have network and push checked out, do:
[14:25] <Chipaca> ./scripts/unicast  -H push.ubuntu.com TokenTokenToken== com.ubuntu.telegram_telegram '"potato"'
[14:25] <Chipaca> om26er: you should see that arrive in the push client and be handed off to the helper
[14:26] <Chipaca> (the helper isn't going to like it, but you should see it get that far)
[14:36] <lool> rsalveti, tvoss: Uploaded lxc-android-config rtm9 rebased on rtm archive version
[14:36] <lool> tvoss: is this in the QA pipeline already?
[14:36] <tvoss> lool, let me check
[14:36] <tvoss> lool, should be
[14:39] <popey> jibel: davmor2 we need to postpone music app testing till monday for translation updates, but clock still needs doing :)
[14:40] <alf_> cihelp: Hi! All mir mako builders seem to either be offline or stuck. Any idea what's going on?
[14:41] <jibel> popey, OK, that reminds me that the card had not been created. Where can I grab the click package for the clock app?
[14:41] <davmor2> popey: I'll add aticket now and jump on it after I finish the sanity on 209 should be about 45 minutes or so
[14:41] <jibel> davmor2, I can take the clock
[14:41] <jibel> just finished adb
[14:42] <davmor2> jibel: ah okay I think popey has an etherpad with manual tests iirc
[14:42] <davmor2> or was that just music
[14:42] <popey> jibel: http://pad.ubuntu.com/kY99vztlmS is the clock details - changelog from nik90 and link to click package contained in there
[14:43] <jibel> popey, nice, thanks!
[14:43] <om26er> Chipaca, do these logs look good? I haven't received a notification with or without the silo. https://pastebin.canonical.com/124100/
[14:44] <Chipaca> om26er: you got the notification, right there in the logs
[14:44] <Chipaca> 2015/01/23 14:42:15.885873 DEBUG posted unicast notification BkgDh6MOEeSf9/oWPmWXaQ== for com.ubuntu.telegram_telegram.
[14:45] <om26er> Chipaca, aah, so Nothing in the UI was expected ? hmm.
[14:45] <Chipaca> om26er: the message itself was rubbish (literally the word "potato"), so it wasn't translated into something you would see in the UI
[14:45] <Chipaca> om26er: karni might be able to give you a better string that'd translate into something you can see
[14:45] <Chipaca> om26er: him being the telegram guy :)
[14:45] <Chipaca> om26er: but for this issue, just that is enough
[14:46] <Chipaca> om26er: now, those logs are from the fixed version
[14:46] <popey> davmor2: tests are in the source, linked from the pad
[14:46] <popey> thanks chaps!
[14:46] <Chipaca> om26er: give it a go with the non-fixed (you don't need to re-register)
[14:46] <Chipaca> om26er: i'm off to fetch my kids from school, but will be back in ~1h
[14:47] <vila> alf_: see topic, the current devel-proposed image is broken
[14:47] <vila> sil2100: any update ?
[14:48] <sil2100> vila: we're waiting for stgraber to appear, since it's the new lxc causing touble
[14:48] <vila> sil2100: ack
[14:48] <alf_> vila: ah, thanks
[14:48] <sil2100> The decision has been made to wait and not revert for now
[14:48] <om26er> Chipaca, ok, I think its not really working after doing the thing with wireless network
[14:49] <Chipaca> om26er: what does 'nmcli nm' say? are you connected to the network?
[14:49] <om26er> Chipaca, connected
[14:49] <Chipaca> om26er: can i see the logs?
[14:50] <om26er> Chipaca, https://pastebin.canonical.com/124101/
[14:51] <Chipaca> om26er: hm, give it a few, it should sort it out
[14:51] <Chipaca> i've got to run
[14:52] <om26er> sure
[15:01] <jhodapp> sil2100, I can't seem to find my spreadsheet entry anymore that I added last night for vivid silo 25...I think it got eaten
[15:02] <sil2100> huh
[15:02] <sil2100> jhodapp: we had some strangeness happening with the spreadsheet indeed
[15:02] <sil2100> hm
[15:03] <jhodapp> lol, I still have my silo :)
[15:03] <sil2100> jhodapp: will you be able to add it once again? Sorry about that, I'll connect it to the silo ;)
[15:03] <jhodapp> sure thing
[15:03] <sil2100> The spreadsheet only holds additional info (like description and comments) and is only used in the assignment phase
[15:05] <jhodapp> sil2100, line 88
[15:05] <sil2100> jhodapp: thanks!
[15:05] <sil2100> jhodapp: hooking it up
[15:05] <jhodapp> no thank you :)
[15:07] <sil2100> jhodapp: should be hooked up again ;)
[15:10] <ted> trainguards, Could I get silos for lines 85/86 please? rtm/vivid
[15:11] <sil2100> ted: sure! In the middle of that ;)
[15:11] <ted> Heh, cool, thanks!
[15:13] <sil2100> ted: yw! So, I assigned the vivid one but remember that you have url-dispatcher in silo 003 already
[15:13] <sil2100> RTM assigned without any conflicts
[15:13] <ted> sil2100, Yeah, silo3 is to that they can test the trusted session changes. I don't expect that to land for a while.
[15:27] <dbarth> o/ trainguard on line 69 please
[15:34] <u_glide> Hello guys! Does autopilot able to introspect QQuickWidget (http://doc.qt.io/qt-5/qquickwidget.html) ?
[15:55] <oSoMoN> trainguards: can silo 8 be published please?
[16:03] <sil2100> o/
[16:05] <jibel> popey, I still have AP tests to run but manual verification of the clock app looks good. I'll give you the final result later today.
[16:06] <nik90> jibel: Yay :)
[16:07] <popey> jibel: excellent. nice work nik90 :)
[16:11] <Chipaca> om26er: back. how's things?
[16:21] <ogra_> pmcgowan, could you categorize bug 1413622 i would like to do the seed change in the same package upload as for bug 1392380
[16:23] <sil2100> brendand: hey, just had a moment to take a look at the UID thing and sadly it would be a bit risky to add
[16:23] <sil2100> brendand: since even though the addition of that could be possible, but it would then require us to change a lot of the spreadsheet code - which carries potential risk of everything breaking badly
[16:24] <pmcgowan> ogra_, all set
[16:24] <ogra_> thx
[16:26] <brendand> sil2100, ok i'll have to think of a workaround then
[16:27] <brendand> sil2100, see i have a check in my code to see if the uid is there, surely for a good reason
[16:27] <brendand> sil2100, got to see if i can remove it somehow
[16:27] <sil2100> brendand: you could do it contitionally (as a hack) and check for UID and if no UID is there, then look for the [non-citrain] string somewhere
[16:27] <sil2100> brendand: I'm still trying to move it to a different column btw.
[16:35] <sil2100> ogra_: do you have a short moment for a packaging ACK?  https://ci-train.ubuntu.com/job/ubuntu-landing-013-2-publish/lastSuccessfulBuild/artifact/packaging_changes_dbus-test-runner_15.04.0+15.04.20150116-0ubuntu1.diff
[16:35] <Chipaca> om26er: I'm back. how's things?
[16:36] <ogra_> sil2100, do we have that version in rtm ?
[16:36] <ogra_> or is that for vivid only
[16:36] <om26er> Chipaca, I replied, internet failed me. https://pastebin.canonical.com/124120/
[16:36] <sil2100> ogra_: vivid only for now
[16:36] <om26er> Chipaca, it never detected network
[16:37] <Chipaca> om26er: from the log, it carried on trying to detect it though
[16:37] <om26er> Chipaca, but internet was there, working just fine. Is there an "expected" time that would happen ?
[16:37] <ogra_> sil2100, ACK then
[16:38] <sil2100> ogra_: thanks!
[16:39] <Chipaca> om26er: i don't know what's going on, then. What "that" do you mean wrt "time that would happen"?
[16:43] <om26er> Chipaca, hmm, now it seems to work sometimes, fails the other. Which I guess is expected as this is not a full fix ?
[16:43] <Chipaca> om26er: i would've expected you to see it fail only rarely
[16:43] <Chipaca> om26er: so it's interesting that you're able to make it fail, unless you're doing more than the "for i in `seq 5`; do frob the network" thing
[16:44] <om26er> Chipaca, in 5 attempts it failed twice.
[16:47] <Chipaca> om26er: and without the fix?
[16:48] <om26er> Chipaca, I think I was reading the logs wrong. This has been working, right.
[16:52] <om26er> Chipaca, I'll re-try without the silo and evaluate the different, will update you when I am done. Sorry for the confusion.
[16:54] <Chipaca> om26er: no worries, it's a relief. Thank you and looking forward to it.
[16:55] <om26er> Chipaca, what does this DEBUG message mean:
[16:55] <om26er> connectivity: connection check says: false
[16:56] <om26er> there is no internet or that it stopped looking for connection ?
[16:59] <oSoMoN> trainguards: can I have an RTM silo for line 91, please?
[17:06] <sil2100> tvoss: https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-1396985/+merge/243063 <- needs approval
[17:06] <popey> dpm: will you be around to do a clock upload (assuming jibel has finished testing soon)
[17:11] <Chipaca> om26er: 'connection check says: false' means it tried to download a file from the internet and failed, meaning that although network manager thinks it's connected, it's not
[17:11] <Chipaca> om26er: sorry for the delay responding, didn't see the popup
[17:11] <om26er> no problem, I was in a call.
[17:20] <popey> dpm: actually, don't worry, it won't be ready till a bit later or even over the weekend
[17:45] <om26er> Chipaca, I have done some thorough testing now. The overall situation does not seem to change with or without the silo. On some reconnects it just does not detect the network connection even after a few minutes.
[17:46] <Chipaca> om26er: can i have debug logs for when it didn't work, please?
[17:47] <om26er> Chipaca, https://pastebin.canonical.com/124130/
[17:48] <cyphermox> robru: don't hesitate to ping me if you need help with landings.
[17:48] <Chipaca> om26er: how many times were you reconnecting the network during that test run?
[17:48] <Chipaca> om26er: looks like 62 times, from the logs
[17:48] <om26er> Chipaca, yes, with a loop, with sequence of 5
[17:49] <om26er> Chipaca, my point is, it was pretty much the same without the silo as well.
[17:49] <robru> cyphermox: thanks
[17:50] <Chipaca> om26er: are you sure you actually had network at the end, there? my AP needed restarting after I'd done this a few times (not sure i reached 60+ reconnections)
[17:51] <Chipaca> om26er: could you also pastebin the one _without_ the ppa?
[17:52] <Chipaca> om26er: (fwiw, i see no evidence of a deadlocked client in those logs, although it's probably academic if it's decided not to connect)
[17:54] <om26er> Chipaca, the problem is it does not detect the internet, not talking any deadlocks.
[17:54] <om26er> Chipaca, I have had that cleared, would need to get fresh logs without silo.
[17:54] <Chipaca> om26er: ok. are you sure you had internet though? because it tried to download that page and failed with a network error
[17:55] <Chipaca> it'll retry after a number of seconds, as long as network manager still thinks it's connected
[17:55] <Chipaca> or it should :)
[17:55] <om26er> Chipaca, I think it retries after exact 1min so if it didn't find internet when the connection was established, it never does even after a minute.
[17:56] <om26er> Chipaca, also internet should be working, its the same wifi as my laptop and IRC never disconnected.
[17:57] <Chipaca> om26er: 10 minutes
[17:58] <Chipaca> om26er: 10 minutes between web checks
[17:58] <om26er> "not connected after 1m0s; giving up"
[17:58] <Chipaca> om26er: you can configure that, specifying e.g. -recheck_timeout=1m
[17:58] <Chipaca> om26er: that's about account-polld, not the webcheck
[17:59] <Chipaca> push client asks for a hardware wakeup, waits a bit for the network, goes back to sleep
[17:59] <Chipaca> not related to this
[17:59] <om26er> Chipaca, The code change doesn't seem to regress anything, so perhaps it could have something to do with my internet
[18:00] <Chipaca> om26er: i really want to know why you got stuck now :)
[18:00] <Chipaca> om26er: can we do another run, changing some config values?
[18:01] <om26er> Chipaca, "yes we can"
[18:01] <Chipaca> om26er: probably easiest if you edit the config file, in /etc/xdg/ubuntu-push-client
[18:01] <Chipaca> om26er: double everything that looks like a time, except for recheck_timeout :)
[18:01] <Chipaca> or maybe i pastebin a config file
[18:02] <Chipaca> gimme a sec
[18:02] <tvoss> sil2100, done
[18:03] <Chipaca> om26er: https://pastebin.canonical.com/124135/
[18:03] <Chipaca> ooh, look, it's nearly beer o'clock
[18:04] <om26er> Chipaca, just restart the client ?
[18:04] <Chipaca> om26er: yup
[18:07] <sil2100> o/
[18:07] <robru> sil2100: goodnight
[18:08] <sil2100> robru: I'll still be around to finish up some discussions and e-mails, but I published the 2 silos above and leaving everything else in your hands
[18:08] <sil2100> robru: remember, in case you don't feel too well, ping cyphermox
[18:08] <sil2100> :)
[18:09] <robru> sil2100: ok thanks
[18:10] <om26er> Chipaca, it might have something to do with my network, in another tab if I login to the phone, even the ping to google.com sometimes just timesout.
[18:11] <Chipaca> om26er: or the phone getting confused because of all the network frobbing
[18:11] <Chipaca> om26er: you might need to reboot it (or the router)
[18:11] <Chipaca> om26er: sorry :)
[18:11] <Chipaca> my router just refused to give it an ip after i'd tested this a number of times
[18:16] <Chipaca> om26er: i'm afraid i've got to go start the evening routine here at home. I'll check back in a while, but won't be able to sit down for a few hours.
[18:17] <om26er> Chipaca, alright, I think this is not something that needs to land immediately ? so perhaps if not today, we can land early next week.
[18:17] <Chipaca> om26er: the sooner the better, as this is breaking telegram for some people, but if we can't make it today we can't
[18:21] <robru> cyphermox: when are you taking your lunch?
[18:23] <cyphermox> robru: thirty minutes or so from now, I have a coquille saint-jacques in the oven :)
[18:24] <robru> cyphermox: ah ok. let me know when you get back and then I'll go
[18:24] <cyphermox> don't hesitate, I'll eat in front of my computer
[18:28] <tvoss> brendand, you still around?
[18:57] <om26er> Chipaca, for, when you get back https://pastebin.canonical.com/124147/
[18:58] <om26er> Chipaca, that is after the changes you suggested to the config. So I am pretty confident, my network aint the only problem.
[19:05] <imgbot> [19:14] <om26er> cyphermox, Hi!
[19:14] <cyphermox> om26er: howdy sir
[19:15] <om26er> cyphermox, if i connect bluetooth to my car and play a song that works fine the first time but if I disconnect it and reconnect the bluetooth the sound stutters and lags.
[19:15] <om26er> cyphermox, but I don't see that issue with my bluetooth headsets. which is bluetooth 3.0
[19:16] <om26er> cyphermox, is there a way to check the bluetooth version of my car through terminal or something ? also what logs should I try to gather ?
[19:17] <cyphermox> maybe bluez-test-device <address> info tells you? I don't remember if that's an actual command
[19:19] <cyphermox> om26er: that or hciconfig -a, but in reality it's not a straightforward "you have this version", but usually rather a case of what features are provided
[19:19] <cyphermox> oh wait, since you're asking about the car, that would be more hcitool inq <address>
[19:19] <kenvandine> rsalveti, i passed by silo 18 again... i'll rebuild it again once this is merged
[19:20] <rsalveti> kenvandine: thanks, no worries, sorry not yet done with it
[19:20] <kenvandine> no worries
[19:32] <om26er> cyphermox, what does that translate to:
[19:32] <om26er> clock offset: 0x0d01	class: 0x240408
[19:32] <cyphermox> "wrong command", that just says what kind of device it is
[19:35] <cyphermox> om26er: I'm sorry, clearly I can't do this from memory
[19:35] <cyphermox> I think you want hcitool info instead... otherwise I wouldn't know how to get the information
[19:36] <cyphermox> om26er: thing is, even that might not really help, because the stuttering could be due to something completely different
[19:36] <om26er> cyphermox, ok. But can you please look through this syslog: http://paste.ubuntu.com/9839085/
[19:36] <cyphermox> you're streaming audio from the phone to the car?
[19:36] <cyphermox> oh
[19:36] <om26er> cyphermox, yes, local mp3 in the phone through bluetooth.
[19:37] <om26er> yes it started Skipping when I reconnected the bluetooth and played the song.
[19:37] <cyphermox> insufficient signal maybe?
[19:37] <cyphermox> does it ever pick it back up or does it keep skipping for a long while>
[19:37] <cyphermox> ?
[19:38] <om26er> cyphermox, I am inside the car, so very close to the system.
[19:38] <om26er> cyphermox, it keeps on skipping
[19:38] <cyphermox> om26er: have you filed a bug about it?
[19:39] <om26er> cyphermox, never had the change to sit in the car with a laptop previously :)
[19:39] <cyphermox> I'd have to dig in pulseaudio code to figure out why it would skip
[19:39] <om26er> cyphermox, it happens with both mako and krillin FWIW.
[19:41] <cyphermox> ok
[19:41] <om26er> cyphermox, can you tell me which package to report the bug against ?
[19:41] <cyphermox> om26er: please open the bug against bluez
[19:42] <cyphermox> since you said your test was working with a bluetooth headset, it's likely not pulse... and probably not bluez either
[19:44] <cyphermox> om26er: if you're up to doing more testing, it would be nice to compare the output of hcitool lq <address> before and after suspend for the car, and for the headset
[19:45] <om26er> yeah, I am testing (and collecting more logs)
[20:19] <om26er> cyphermox, Ok. I reported the bug. Attached hcidump,  syslog and link quality. bug 1414142
[20:20] <om26er> brb
[20:25] <imgbot> [20:25] <imgbot> [21:12] <ogra_> cyphermox, if you find some time ... ^^
[21:12] <cyphermox> of course
[21:12] <cyphermox> ogra_: are you adding a proper fr_CA keyboard layout? :D
[21:13] <ogra_> dunno, did canda switch to bosinan or croatian recently ?
[21:13] <ogra_> or emoji ?
[21:13] <ogra_> :)
[21:14] <cyphermox> ouh, shiny.
[21:14] <cyphermox> unfortunately, all silos are taken
[21:14] <ogra_> dang
[21:14] <ogra_> ok
[21:14] <cyphermox> kenvandine: rsalveti: can we drop the bluetooth agent rework thing for now?
[21:14] <cyphermox> (or better yet, can we just land it? :)
[21:15] <ogra_> cyphermox, err, wait, i need rtm
[21:15] <cyphermox> ah
[21:15] <kenvandine> it would need a rebuild first
[21:15] <kenvandine> or drop it
[21:15] <cyphermox> well it's for RTM so nevermind
[21:15] <kenvandine> i should have another settings landing tonight still, so i was holding off rebuilding 18
[21:15] <cyphermox> kenvandine: ack
[21:15] <ogra_> yeah, there are a few free ones
[21:15] <cyphermox> ogra_: how come you didn't set the spreadsheet accordingly?
[21:16] <ogra_> did i not ?
[21:16]  * ogra_ checks
[21:16] <cyphermox> has it already landed in vivid?
[21:16] <ogra_> sorry
[21:16] <ogra_> no
[21:16] <ogra_> its a seed change
[21:16] <cyphermox> no worries, but it explains the issue
[21:16] <cyphermox> ok
[21:16] <ogra_> i'll line up the vivid seeds on the weekend
[21:18] <cyphermox> ok
[21:20] <ogra_> merci !
[21:25] <cyphermox> ogra_: np!
[22:15] <pmcgowan> om26er, woot!
[22:16] <om26er> ;)
[22:29] <charles> trainguards, the MP for ubuntu-rtm/landing-012 is top-approved now, so publishing now shouldn't block on "some merges are unapproved"
[22:30] <cyphermox> bfiller: Kaleo: you know camera-app is already in another silo? just want to make sure before I override that warning.
[22:31] <cyphermox> charles: ok
[22:32] <bfiller> cyphermox: yup that's fine
[22:32] <cyphermox> charles: it will take a bit even if I refresh it's not top-approved for me...
[22:32] <charles> ...? /me re-looks
[22:32] <bfiller> cyphermox: you can ignore warning
[22:33] <cyphermox> ok
[22:33] <charles> cyphermox, you're correct, looks like the URL I passed to wellark to top-approve was the vivid MP rather than the rtm MP
[22:41] <robru> cyphermox: charles: btw if this happens again, the publish log will say specifically which MPs need to be approved: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-012-2-publish/31/console
[22:42] <charles> robru, ty :)
[22:42] <robru> charles: you're welcome
[22:42] <robru> charles: and that's linked from the dashboard, since the train-guard may not think to send you the link
[22:44] <Kaleo> cyphermox, ??
[22:46] <cyphermox> robru: you're back
[22:46] <robru> cyphermox: oh yeah sorry, i have a pounding headache
[22:48] <cyphermox> no worries
[22:48]  * cyphermox gets back to his soup
[23:03] <robru> ogra_: no qa for rtm 15?
[23:20] <robru> cyphermox: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-004-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-download-manager_0.9+15.04.20150123~rtm-0ubuntu1.diff need a core dev ack when you get a sec
[23:20] <cyphermox> sure
[23:24] <cyphermox> robru: go
[23:24] <robru> th
[23:24] <robru> thx