=== ribru is now known as robru [01:32] hurr durr i'm a shurr [04:48] morning again [04:52] Mirv: oh hello! I *just* merged some experimental stuff into production, so watch out for weird failures. I'll stay up for a bit to revert it if anything goes wrong, just ping me [04:53] Mirv: builds were tested in preprod but publishing and cleaning is totally untested and may explode [04:54] indeed I've broken cleaning. excellent! [04:55] tedg: false alarm, I'm breaking stuff [04:55] robru: ok :) [05:01] heh, check-publication-migration is working ;-) [05:01] robru: publishing seems to be working, too [05:01] Mirv: oh sweet [05:02] Mirv: ok I'm gonna try to fix cleaning instead of reverting everything... [05:02] Mirv: but if I can't fix it in an hour then I'll revert and try again tomorrow [05:02] sounds good [05:03] eh, that's not true though ^ [05:04] it's not yet anywhere, the keyboard [05:04] the rsync line looks correct so I'd expect it to appear soon though [05:06] yes, now it appeared [05:06] robru: but the check-publication-migration failed there ^. it's still pending https://launchpad.net/ubuntu-rtm/+source/ubuntu-keyboard/0.99.trunk.phablet2+14.10.20141104~rtm-0ubuntu1 [05:07] shit [05:09] damnit [05:09] I didn't really touch check-publication-migration though. [05:11] oh, I did tinker with a function that check_publication_migration calls. damn. ok I'm loading with debugging statements! [05:19] hm [05:20] ok well i've fixed merge & clean [05:20] Mirv: ok I think I fixed check_publication_migration as well, but silo rtm 6 now really is published so it's tough to say. let's keep an eye on that... [05:22] hmmm [05:24] wut [05:25] cihelp did citrain jenkins just get rebooted or something? strange anonymous job termination plus I got logged out just seconds after submitting a job [05:25] oh well that's good at least ;-) [05:26] Mirv: ok check_publication_migration is fixed ^ [05:26] I like how check_publication_migration's default thing is to claim all packages are migrated in the event of an error. "oh something broke? all packages are migrated!!" [05:27] ugh [05:27] robru: ok, great! [05:28] nice defaults [05:28] a bit like these "Error! Success!" of the past [05:29] Mirv: yeah it's the same old architectural deficiency shining through various cracks [05:30] tedg: ok sorry for the highlight spamming there, your silo was successfully merged & cleaned despite that strange signal 15 message there. I confirmed your trunk branch has the right stuff in it ;-) [05:54] sweet this is looking really good. [05:54] Mirv: ok I'm gonna land this [05:56] robru: sure, all seems good now so far [06:44] Mirv: ok I'll be around for a little bit, but if anything explodes, just run the deploy job with DEPLOY_PROD_REVISION set to -3 to get it back to a known working state. -2 will put it into a state where syncs don't work [07:31] robru: everything seems still fine, although I'm only playing with the qt silo atm [07:32] probably there will be no reason to deploy the older version [07:33] Mirv: yeah dunno, my last branch also seemed fine but then some corner car came up that was broken. The train is a fickle mistress [07:34] *case [07:36] that she is [07:51] Mirv: when you get a moment could you please upload http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.calendar_0.4.534_all.click - I think balloons may have tried last night, but I don't see it in the store. [07:56] good morning [09:01] popey: calendar uploaded [09:05] thanks Mirv [09:06] Damn, I feel like a zombie [09:09] hmm, unity8 is still freaking out in topbefore/after everywhere [09:10] * Mirv has loads of crashes in /var/crash from playing around for the morning [09:10] or had, rather, just reflashing [09:10] we have only 3 in smoke-testing [09:12] my volume overlay comes up at the very top of the screen again (covering the panel) [09:12] this happens every other image to me ... totally random [09:14] ogra_: on krillin? not seen that here [09:16] popey, yeah, on krillin, i showed it to john-mcaleely at the sprint ... it was gone for a while but now i have it randomly back after every other OTA [09:17] havent seen it for at least three images though [09:23] hah, fun [09:23] now it is gone [09:24] (i disconnected my BT speaker) [09:25] We still didn't get the CPU-load-fixes in, right? [09:26] sil2100, nope, one part of them is on the way in rtm 9 [09:27] brendand, davmor2: for QA, how many people do we have now in the EU timezone? Just 2 people? [09:27] tvoss: thanks :) [09:27] * Mirv bootstrap flashed latest vivid, stares at spinning Ubuntu logo [09:28] sil2100, 4 [09:28] * Mirv waits for the step 1 from the new QA plan to be implemented (only release images to -proposed that boot & run unity8) [09:28] robru: it ran out of space [09:28] Mirv, ? [09:28] See #is-outage [09:29] And https://bugs.launchpad.net/ci-train/+bug/1389968 [09:29] Error: ubuntu bug 1389968 not found [09:29] Mirv, oh vivid. pfff [09:29] brendand: it was discussed during the sprint that there should be a gatekeeper that non-booting images wouldn't be released. I assume that would make sense (when it's available) on vivid too. [09:29] brendand: ;) [09:29] Mirv, it would indeed [09:30] brendand: how much before you wanted this "rtm-022 ping"? there's something to test there now, I just find it a bit hard to test with the unity8 crashes and scope unreliability in general. [09:31] Mirv, whenever you're ready to test it [09:31] ev: hey! I'll comment on that in a minute [09:31] Thanks sil2100 [09:33] brendand: I'm ready to test it in the sense that lorn could use feedback on the bug whether there's an improvement or not. I did get music scope image downloads over 3G, but I also had problems that I don't know if they are related to the qtbase or the unity8 problems. [09:34] ogra_, did we decide it was a difference with OTA vs clean flashes? [09:35] john-mcaleely, iirc we firstly did but then discovered someone else who had OTAed and didnt see it [09:35] and set the bug to incomplete [09:35] davmor2: ping! Meetong [09:38] cjwatson, I need to ask for updates to system-image.u.c, so it takes different tarballs for rtm & vivid [09:38] cjwatson, I've tried to find that file you sent me at the sprint in my logs [09:38] cjwatson, but have failed to find it :-( [09:49] Saviq, i was testing silo 4 yesterday [09:49] brendand, yes, I know you did not like the indicator syncing [09:50] brendand, we're looking into it now, all else fails I'll pull the relevant changes from silo 4 [09:54] Saviq, thanks. i also felt like it was crashing more often, but they were the same crashes as usual, not new ones [09:54] brendand, I think the qtubuntu-media fix only landed later than when you were testing [09:56] Saviq, well i don't think i had landed yet [09:56] or even.. [09:57] cihelp in the transition to vivid mir-ci seems to have lost some builds: specifically mir-mediumtests-utopic-touch has no vivid equivalent. Before: https://jenkins.qa.ubuntu.com/job/mir-ci/2008/console, after: https://jenkins.qa.ubuntu.com/job/mir-ci/2022/console. What's going on? [09:58] stupid webcam [09:58] * Mirv flashes vivid 9 [09:59] popey: you should have a warning "May contain flashing images" as your lower 1/3 ;) [09:59] heh [09:59] yes! [10:04] === trainguards: IMAGE 11 building (started: 20141106 10:05) === [10:06] john-mcaleely: http://paste.ubuntu.com/8849582/ [10:06] (that's nusakan:/srv/system-image.ubuntu.com/etc/config) [10:07] cjwatson, thanks [10:17] alan_g: looks like the mir-mediumtests-vivid-touch doesn't exist, will ping fginther [10:18] vila: thanks [10:24] robru, sil2100, Ursinha-afk: public service announcement: if you move files around in lp:cupstream2distro's citrain directly, do be sure to update the jenkins charm and/or lp:ci-train [10:24] as this has broken the production deployment [10:27] brendand, hello, fyi the topblocker bug from #50 has been tested by us and is ready for qa sign off [10:27] cjwatson, here's how I think it should look http://paste.ubuntu.com/8849746/ [10:28] cjwatson, there are now 3 tarballs available for system-image.u.c: utopic, ubuntu-rtm-14.09, master (vivid) [10:28] cjwatson, right now, all three are identical, and contain what is in the single lookup now [10:28] cjwatson, I believe I need to publish separate updates today for vivid & ubuntu-rtm [10:28] cjwatson, does the update make sense to you? [10:35] robru, sil2100, Ursinha-afk: this is also why while having a remote branch that production pulls from gives you flexibility, it's a fundamentally broken approach as it's all too easy to get out of sync when things aren't carefully coordinated. Tar'ing up the code and making that part of the deployment fixes this. [10:36] obviously not blaming you guys for any of this - it's a creation you've inherited - but I want to make sure we take the right lessons from it [10:39] fix cowboy'ed onto production. jacekn is working on doing an upgrade-charm to pick up the real fix in the jenkins charm [10:41] john-mcaleely: I'm at a conference right now. Could you please mail me a diff (*not* the whole new file)? [10:41] cjwatson, sure [10:43] ogra_: vivid 10 on mako known broken? [10:43] popey, ask Mirv and davmor2 :P [10:43] they showed it in the meeting [10:44] popey: yeap ogra_ is meant to be fixing it though [10:44] popey, i triggered 11 (see above) to make sure we are not missing anything from the android update, 11 might or might not work [10:44] ogra_: fix it faster [10:45] :P [10:45] kk [10:45] ogra_: no faster not more sarcastically :P [10:45] haha [10:45] ev: ACK [11:11] heh [11:11] the bootchart for vivid 10 looks interesting [11:11] http://people.canonical.com/~ogra/ubuntu-phablet-vivid-10.png [11:11] looks like media-hub is in a crashing loop .... tearing down unity8 with it [11:12] popey: I went back to 9 to test qt [11:12] ta [11:12] will revert [11:18] ogra_, do you have the new device tarball? [11:18] tvoss, where ? krillin ? yes, since yesterday [11:19] ev: understood, but not sure if files were moved around, robru was working on changing relative/absolute paths in the code, I wonder if that broke things? [11:22] ogra_, the one that is required for https://launchpad.net/ubuntu/+source/media-hub/2.0.0+15.04.20141105.1-0ubuntu1 [11:22] ogra_, also: got crash file for media-hub? [11:23] tvoss, note the above is vivid on mako ... that should have the changes in the new android package [11:23] and yes, i have crashes [11:23] ev: if you are talking about bug 1389968, then the problem seems to be that the charms weren't updated to reflect how setup_citrain gets parameters (not that files were moved around), but your point still stands -- thanks for pointing that out [11:23] Error: Launchpad bug 1389968 could not be found [11:23] ogra_, did you upload them, yet? oops idea would be helfpul [11:23] s/idea/id [11:23] tvoss, https://errors.ubuntu.com/oops/5bdbf2a4-65a4-11e4-80e5-fa163e525ba7 [11:25] ogra_, ouch, somehwere in android [11:26] yes [11:27] ricmm, ^^^ [11:27] (oh, i think he is flying today) [11:27] we might have to wait for rsalveti [11:29] === trainguards: IMAGE 11 DONE (finished: 20141106 11:30) === [11:29] === changelog: http://people.canonical.com/~ogra/touch-image-stats/11.changes === [11:29] tvoss, ^^ looks like hybris simply had not migrated for image 10 [11:29] 11 should boot [11:31] Mirv, popey ^^^^ [11:31] dammit, 9 just finished ☻ [11:32] huh, no volume overlay when changing up/down [11:32] popey: but now you can ota to 11 [11:32] ya [11:33] ogra_: thanks. [11:36] * popey updates [11:42] 111 is good [11:42] er, 11 [11:42] got a bit excited there [11:45] haha [11:45] +100 [11:50] popey, nope that never landed in vivid [11:50] popey, as i found out yesterday [11:53] Ursinha: already fixed :) [11:53] Ursinha: what broke it was renaming files, yeah [11:53] but what's more fundamentally broken is that this production environment references a remote bzr branch that can change underneath it [11:54] it really should've been that the code got bundled with the deployment [11:54] and requests were made to webops for further updates [11:54] ev: got it [12:13] brendand, sil2100, ogra_: Mako vivid 11 has buttons not swipe http://people.canonical.com/~davmor2/buttons.png [12:14] sil2100, isn't stuff meant to land in vivid first? [12:14] Saviq, ^ [12:14] brendand, davmor2, it's the telephony service that needs adapting [12:15] and yeah, they did not land it in vivid yet [12:15] we did our part [12:15] Saviq, brendand: it hasn't landed in RTM either this is buttons too [12:16] davmor2, well no - i'm testing that now [12:16] davmor2: yeah, it's silo 4 that has that actually [12:16] ogra_: so no breakage? :) [12:16] slow migration bots ;) [12:16] ricmm, yeah, just out-of-sync [12:17] davmor2, it's in silo [12:18] so yeah, the telephony bit landed in rtm, not in vivid, unity8 bits the other way round [12:19] * davmor2 blames ogra_ obviously for vivid 10 being broken ;) [12:19] yeah, my hybris fiddling broke everything [12:20] Saviq, so what about silo 4 then? [12:20] brendand, dednick pung you somewhere, will come here shortly [12:20] Saviq, i didn't get anything [12:21] brendand: hi [12:21] dednick, hello [12:21] fight! [12:21] ;) [12:21] /food [12:21] food fight ? [12:21] ogra_, you kinky you [12:21] :D [12:21] brendand: pinged you on touch awhile ago. nevermind :) [12:21] brendand: i've tried out silo 16 but can't get the sound out of sync? what are your steps? [12:22] dednick, sound? [12:22] brendand: kgunn said the flight mode and sound settings in system settings were stll getting out of sync with indicators [12:23] dednick, the problem i have is that flight mode toggles back and forth when you switch it on [12:23] brendand, ah, that's an indicator-network issue [12:23] brendand: i think it's because of the backend [12:24] Saviq, is there a fix pending for it? [12:24] brendand, we tell it "go to flight mode", a second or so later we check the value, but it's still "no flight mode", then another second after that it comes back with "yeah, I turned flight mode on" [12:25] Saviq, it looks crappy though [12:25] brendand, it does, I agree, and no I don't think there's a fix, but then that's required for the switches to remain in sync [12:26] Wellark, so, indicator-network taking a long time (like multiple seconds) to acknowledge flight mode setting, what can be done? [12:26] Saviq: dednick ....but with silo 16, i can toggle flight mode quickly and get it to "stick" seemingly [12:27] kgunn, I think it depends on your setup, basically the network indicator is waiting for urfkill (?) to say "yeah, you're in flight mode" [12:27] and it's switching hardware about that might take some time I think [12:27] kgunn: the indicators and settings use a differnt method to working the flight mode. i think something is getting screwy somewhere in the backend [12:27] so, does 'rtm silo 9' have a pair for (I'm guessing) vivid? [12:27] and how would I find out? [12:28] rsalveti, ^ ? [12:28] john-mcaleely: grep the sheet for landing-009 [12:28] oh, are the numbers the same on both distros? [12:29] no [12:29] dednick: also, for sound, if i select silent mode...the little speaker+sound wave icons stays... [12:29] kgunn, no luck :-( [12:30] tvoss, is there a vivid silo for what rtm 9 is? [12:30] john-mcaleely, but also, that silo looks like a sync, meaning that is already *in* vivid [12:30] dednick, i can get the sound toggles to be out of sync here too [12:30] aha. interesting. [12:30] Saviq, thanks [12:30] john-mcaleely, if you look at http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=009 [12:30] dednick, without the silo [12:30] john-mcaleely, it says "spreadsheet row 62" [12:30] it does indeed [12:30] brendand: yeah.. that's what the silo fixes [12:31] john-mcaleely, you can then go to https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&pli=1#gid=0 [12:31] dednick, ok [12:31] kgunn: do you mean the icon? [12:31] john-mcaleely, and see how the silo is set up, it says "sync:ubuntu,vivid" there, meaning it simply picked all the packages up from vivid [12:31] dednick: yep gimme a sec...will video [12:32] /reallyfood [12:32] Saviq, aha, thanks. makes some sense. [12:32] unping rsalveti :-) [12:33] kgunn: i dont think silent mode is connceted to an icon. it doesnt change if i change in indicators either. [12:34] unless you mean the really annoying icon which pops up in the system settings page. [12:35] dednick: then how the heck is a user supposed to glance at phone and see he's on silent mode ? :P [12:35] sholdn't the icon change to a speaker+'X' instead of sound waves [12:35] kgunn: hehe. yeah, well it should. bug in indicator-sound i guess [12:37] kgunn, so i really don't want to land this unless i hear that either a fix is imminent (like in a silo almost ready for sign-off), or that this is the desired behaviour for RTM [12:44] brendand: it might be that we're not the ones to fix it [12:44] kgunn: hm. so apparently "mute" and "silent mode" are not the same things... [12:44] brendand, kgunn, dednick, we could pull the sync branch from the silo and come up with a proper fix afterwards, but that will mean breakage, as opposed to visual awkwardness [12:45] dednick, yeah, but we don't do <|× for either ;) [12:45] so def. a bug in indicator-sound [12:45] Saviq: pull the u8 sync branch you mean? [12:45] dednick, yes [12:45] Saviq: breakage how ? [12:45] Saviq: no breakage. will be same as before [12:46] kgunn, same breakage we have now I mean [12:46] :) [12:46] so we're getting out of sync, with dednick's branch we're in sync, but visually awkward [12:46] right. so the indicator will just be wrong. === alan_g is now known as alan_g|lunch [12:46] dednick: but it's eventually right [12:46] ya [12:46] i mean it does correct eventually [12:46] kgunn, with dednick's branch, not without it [12:46] (but awkward indeed) [12:47] Saviq: got it.... [12:47] so yeah, IMO it's better to be correct but awkward vs. wrong [12:47] brendand, ↑? [12:47] man Saviq said it better....that's what i tried to say to brendand y'day [12:47] worth noting that i dont think the settings corrects itself :/ [12:49] dednick, not before your branch in silo 16 that is? [12:49] Saviq: silo16 doesnt add autocorrecting. [12:49] Saviq: the USS branch i mean [12:50] with the timer thingy [12:50] dednick, should it? [12:50] Saviq: well, for the same reason we have done in u8. [12:51] dednick: so i'm on silo 16....and system-settings seems to follow [12:51] even eventually [12:53] hmmm dednick this seems way better than last night (flight mode toggling) [12:54] ah...cause i installed ofono sim stuff [12:54] faster than a real radio [12:55] kgunn: https://bugs.launchpad.net/indicator-sound/+bug/1390067 [12:55] Ubuntu bug 1390067 in The Sound Menu "Silent mode does not change the icon to the mute icon (or like)" [Undecided,New] [12:55] kgunn: yeah, that would do it. probably works every time as well... [13:01] boiko: bfiller: https://code.launchpad.net/~boiko/history-service/save_timestamps_utc/+merge/240337 not approved, ready for publishing otherwise [13:01] brendand, so, just to restate: with silo 4 we're correct, but awkward, without it we're wrong (in what the indicator shows), so if you ask me it's still better [13:01] Mirv: oups, I think I will wait for bfiller to approve it [13:01] and that's the only two choices we have right now [13:07] * sil2100 lunch o/ [13:09] brendand_, looks like your connection's flaky today [13:09] brendand_, brendand, so, just to restate: with silo 4 we're correct, but awkward, without it we're wrong (in what the indicator shows), so if you ask me it's still better [13:09] brendand_, and that's the only two choices we have right now [13:10] why do I have ~80 systemd-logind process on my mako... vivid I guess [13:10] ogra_, bzoltan, cjwatson: https://codereview.qt-project.org/#/c/99054/ [13:11] ogra_, bzoltan, cjwatson: please also fix this issue: https://bugreports.qt-project.org/browse/QTCREATORBUG-13339 [13:12] and why does the mirscreencast stall all the time [13:12] Saviq, yup, the changes landed to vivid last night [13:12] * Mirv wants an oracle to answer all his questions [13:15] cjwatson: do things break if I CI Train would try to sync 5.3.2-2 of qtimageformats _with binaries_ from landing PPA, while 5.3.2-2 is in proposed already without binaries (because build dependencies not matched)? with 5.3.0, I removed the synced packages from PPA right before publishing and let them build in the archive, which was a bit slow. === boiko_ is now known as boiko [13:20] rsalveti, around? [13:20] core-dev question also here, if anyone up for acking a single liner for vivid: https://ci-train.ubuntu.com/job/ubuntu-landing-010-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-ui-toolkit_1.1.1311+15.04.20141102-0ubuntu1.diff [13:22] Saviq, it needs to be passed by product management/design then. if that's the final behaviour they prefer to have then so be it [13:23] Mirv: ogra_ can you take a look at Mirv's question reg. packaging ^ ? [13:24] kgunn, ↑ [13:26] trainguards pretty please a silo for row #70? [13:26] tvoss: yes [13:26] oops, trainguards meant row #56 [13:27] ralsina: rtm-006 [13:27] thx Mirv! === mandel is now known as mandel|lunch === chihchun_afk is now known as chihchun [13:35] can somebody translate https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-006-1-build/86/console to human? what do we need to do? [13:36] Chipaca: your rtm bzr branch https://code.launchpad.net/~ubuntu-push-hackers/ubuntu-push-qml/rtm does not match what's actually in rtm at the moment https://launchpad.net/ubuntu-rtm/+source/ubuntu-push-qml [13:36] kgunn, did you say yesterday that when you used dednick's silo that the flight mode toggle worked normally? [13:37] Mirv: is this checking versions, or actual branches? [13:37] Mirv: That's because this is my first time landing this to rtm after vivid opened [13:37] Chipaca: versions [13:37] ralsina: ^ [13:37] Mirv: thanks [13:37] so I need to dch and change the version? [13:38] ralsina: preferably you should dget the rtm archive version and make sure the rtm branch matches that content exactly, and parse the meaningfulness of any delta. most probably it's just the last changelog entry not being rtm mangled in the bzr. [13:38] ack, thx Mirv! [13:38] brendand_: define normal... :) i was trying to say what saviq said [13:39] that is, it is correct behavior however "visually awkward" b/c the ui is checking to be in sync with what the backend acgtually does [13:39] whereas...before these silos, the ui would reflect incorrectly what the state of the backend is [13:40] brendand_: think of it as bad visual design with silos, we're using toggle & icons to be both for theuser to input desire & reflect the current state [13:40] * Mirv is sad not being able to publish UITK [13:40] kgunn, so one problem is that if you toggle the switch on > off > on [13:41] kgunn, then it ends up in off [13:41] kgunn, the ui shouldn't do what the backend says, the backend should do what the ui says [13:42] kgunn, anyway i'm not going to make the call on this, somebody from product management/design should [13:42] brendand_: i don't think you understand...the ui has to reflect what the backend state is, e.g. you turn off flight mode, but it takes 10 seconds to get out of flight mode [13:43] and what it failed to get out of flight mode completely [13:43] how would the use know that ? [13:43] can't just redraw the ui and hope for the best...b/c that is exactly the original bug [13:43] so if i follow your argument, you should mark the top blocker invalid [13:45] Can't we have an intermediate state? [13:45] kgunn, so the TOPBLOCKER refers to switches getting out of sync in general [13:45] Like, after switching the flight mode, disabling the button until we get confirmation from the backend or wait some timeout (in case that fails)? [13:46] * olli waives [13:46] kgunn, not specifically flight mode [13:46] olli, hey [13:47] how can I help [13:47] olli, there's an attempted fix for a TOPBLOCKER which makes the flight mode switch behaviour very obviously broken looking from a user point of view [13:47] olli: hello! btw. can I send out a draft e-mail for proof-reading in a moment? :) [13:48] olli, kgunn and Saviq's argument is that it's necessary to ensure correct behaviour [13:48] note i said broken *looking* [13:48] brendand_, iwas reading the backscroll [13:49] sil2100: yes, we need an intermediate state really...but with 1 day to go that's rough [13:49] kgunn: true... [13:49] not to mention it's more than ui...it'd be a whole new meta state to perpetuate throughout [13:49] olli, basically, what happens: user taps flight mode, the indicator starts doing things; the UI then asks "is flight mode on?", and gets "no", so it switches back; then backend says "dude, flight mode is on now", and it settles on On [13:49] brendand_, I haven't seen it myself... but doesn't it improve the state where the button state was pointless as it was out of sync? [13:49] olli, yes, it does, it's actually correct, but visually awkward [13:50] * kgunn takes video to avoid explaining like 10 times today :) [13:50] john-mcaleely: yeah, the changes for vivid already landed :-) [13:51] john-mcaleely: so feel free to just push the vivid tarball [13:51] ogra_: thanks for building 11, 10 was indeed out of sync [13:51] olli, out of sync with what? the system state, or out of sync between the indicator and system-settings? [13:51] it got the new android tarball, but not latest hybris [13:51] brendand_, the situation on #140 [13:52] where iirc the indicator is out of sync with pretty much everything easily [13:53] olli, depending on exactly what issue you're taking about, i believe there were some ofono fixes to eliminate the chance of that happening [13:53] ...i'm totally pushing for an actual indicator alert with "dude, flight mode is on now" [13:53] olli, if you mean when it gets permenantly out of sync, rather than temporarily [13:54] kgunn, if you look at the way android does it then it almost instantly turns off wifi and bluetooth, but takes a little for cellular [13:54] kgunn, when turning off at least [13:54] brendand_, don't get me wrong, the indicator service should just go "yes, flight mode is on" straight away, and, if failed (?), come back with "oh dude, I failed" [13:55] yeah [13:55] should have, would have, could have... I think the question is... [13:55] brendand_: we're not arguing we're done and dusted....we're saying what we're wanting to land is "better" than broken [13:55] brendand_, which needs fixing in the network indicator service or urfkill at least [13:55] olli, do you have an exact bug number for the issue you're thinking of? is it this one? https://bugs.launchpad.net/indicator-network/+bug/1336715 [13:55] Ubuntu bug 1336715 in unity8 (Ubuntu RTM) "[TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings" [Critical,In progress] [13:55] what's worse... the previous state of the system or the current [13:55] right [13:55] but we need time to add design into the mix for a meta-state/transistion for radios and sucj [13:55] such [13:56] olli, well not current - it hasn't landed yet [13:56] Saviq: crap, how do i get this ofono meego sim off my phone now :P [13:56] kgunn, uninstall it [13:56] i removed ofono-phonesim-autostart but that no help [13:56] kgunn, uninstall ofono-phonesim [13:56] kgunn, and reboot [13:56] did [13:56] brendand_, intended current [13:57] -phonesim, too, or just -autostart? [13:57] my bad... [13:57] doing phonesim (no autostart now) [13:57] olli, personally i think the previous was better but there appears to be a specific bug i wasn't aware of [13:58] brendand_, that's where we disagree, you could end up with flight mode permanently saying "yes" when it was, in fact, not enabled [13:58] exactly...rude surprise for user [13:58] and then if you toggled, it would say "no", but was actually getting enabled Oo [13:59] Saviq, i know that was possible in the past, but i do believe a fix was landed to ofono to make that extremely unlikely [13:59] Saviq, i'll do some testing on the base image [14:00] brendand_, to me the improvement was a combination of both bugs [14:00] tvoss, btw lets get your silo landed, it works beautifully here [14:02] olli, i think the new behaviour will be extremely confusing for the user because there can be a significant period where the toggle state is not what it's going to be soon in the future [14:03] olli, so they look at it and go "didn't i just switch that on?" [14:03] Mirv: that won't be allowed. you could upload 5.3.2-2build1 to the relevant silo though [14:04] brendand_, it is set to testing done, awaiting qa [14:04] trainguards: hello, can i have a new silo for line 68 ? [14:06] kgunn, olli, Saviq - it just feels like we are swapping a big issue that happens rarely with a minor issue that is obvious and always there [14:06]