[01:11] alex-abreu: https://code.launchpad.net/~abreu-alexandre/unity-webapps-qml/improve-embedded-ui-params-passing/+merge/250329 need this top-approved [05:24] Mirv: https://code.launchpad.net/~rsalveti/kubuntu-packaging/qgstreamercapturesession_avoid_race_eos/+merge/256881 [05:24] rsalveti: thanks! [05:32] robru: ohh, what a begginer mistake :) thanks... now the MRs are approved [05:32] Mirv: ^ [05:41] bzoltan_: nice! [05:42] Mirv: I am sorry ... I simple forget about approving the MRs .. [05:43] bah, now we'd need packaging ack [05:44] robru: the diffs fixing is still underway, right? [05:44] Mirv: should be fixed... [05:44] robru: it's saying the source is a new package https://ci-train.ubuntu.com/job/ubuntu-landing-004-2-publish/lastSuccessfulBuild/artifact/ubuntu-ui-toolkit_packaging_changes.diff [05:45] bzoltan is probably pretty sure he has landed ui toolkit before [05:45] few times [05:45] Buh [05:46] Mirv: go back to the old build job for now. Will investigate that tomorrow [05:47] robru: thanks! [05:47] Mirv: https://ci-train.ubuntu.com/job/ubuntu-landing-004-1-build/129/ this one I think [05:47] You're welcome [05:48] robru: yes, found it [05:48] Great [05:52] asking for packaging ack on #ubuntu-devel === ara is now known as Guest22932 [06:37] got ack [07:40] sil2100: cwayne bug 1446499 after updating today from store - it's gone. [07:40] bug 1446499 in unity8 (Ubuntu) "Updating today scope from store kills scope, doesn't restart" [Undecided,New] https://launchpad.net/bugs/1446499 [07:45] popey, does it come back after reboot ? [07:46] not rebooted yet [07:46] * ogra_ stays away from updating [07:54] I can confirm [07:55] and does not come back after reboot [08:02] gah! [08:03] victorp: ^ [08:03] huh [08:07] bzoltan_: we'll have to poke the release team about this one [08:08] bzoltan_: i.e. about qtcreator-plugin-ubuntu - it's critical, so should be good to get approved [08:09] sil2100: thanks. it is silly to catch a critical bug at that late phase and even sillier to shoot twice on the same bug. [08:12] popey, can we pull it from the store worst case ? [08:13] not sure, last time I did that, I kinda got chided by beuno [08:13] cihelp, the provision script's been aborting for me with this error http://pastebin.ubuntu.com/10860323/ for a few days now, that expected? [08:13] ah no, I can "unpublish" okayt [08:13] popey, well, or block it ... we should make sure not more people upgrade to it [08:14] (it was revert to previous version he didn't like) [08:14] ah, yeah [08:14] ~380 people have updated so far [08:14] damn [08:14] shall I unpublish do you think? [08:14] yeah [08:14] done [08:15] if it is reproducable we should prevent more damage [08:15] and i see you pinged victorp already ... i guess we need a quick fix to unscrew the users [08:15] * popey adds a comment to the bug to say I unpublished [08:15] well, they can reboot and then re-fave the scope [08:16] but that's not very pleasant, and no discoverable [08:16] i thought it is gone ? [08:16] popey: cwayne should be around in a few hours to help out if anything [08:16] * Saviq thinks it was renamed to "dashboard" wasn't it? [08:16] In the meantime let's unpublish [08:16] already happened :) [08:16] likely why it disappeared from the favorite list [08:16] ouch [08:17] * popey wonders how this was tested :( [08:17] yeah, we have no support for that [08:17] I wonder if it was signed off by QA at all [08:17] yup [08:17] weird [08:17] ok, well we have a bug and they can look when they wake [08:17] This might be another hole in our process [08:18] Normally testing of the today scope happens on new custom tarballs [08:18] thanks popey [08:18] np [08:19] popey, just to confirm, can you see in "gsettings get com.canonical.Unity.Dash favorite-scopes" [08:19] Saviq: i have already rebooted and re-added.. [08:19] popey, sure, that's fine, still interesting to know what the scope id is [08:19] ['scope://com.canonical.scopes.dashboard_dashboard', 'scope://unity-scope-nearby', 'scope://clickscope', 'scope://com.canonical.scopes.news_unity-scope-news', 'scope://musicaggregator', 'scope://videoaggregator', 'scope://com.canonical.scopes.photos_photos'] [08:19] popey, if you don't care for your favourites list, could you `gsettings reset` it? [08:20] I'd rather not. [08:20] * Saviq wonders if they updated the default [08:20] oh, it can be readded. but how do I get it to be the first on again instead of last one? [08:20] oh go on then [08:20] * sil2100 will upgrade the package [08:20] Mirv: you can re-order [08:20] long press [08:20] sil2100: found [08:20] Mirv, long-press, drag by handle [08:20] Mirv: just long-press it on the manage screen [08:20] Yeah ;) [08:20] * popey mails the phone list to let people know how to undo this. [08:20] almost discoverable [08:21] Mirv, good news: manage dash is likely going away [08:21] Saviq: resetting has done this:- [08:21] phablet@ubuntu-phablet:~$ gsettings get com.canonical.Unity.Dash favorite-scopes [08:21] ['scope://clickscope', 'scope://musicaggregator', 'scope://videoaggregator'] [08:21] :( [08:21] popey, weird, that's mako/rtm? [08:22] no [08:22] retail bq [08:22] huh [08:22] yeah, I got my retail bq yesterday [08:22] popey, fwiw, you can `gsettings set com.canonical.Unity.Dash favorite-scopes "['scope://com.canonical.scopes.dashboard_dashboard', 'scope://unity-scope-nearby', 'scope://clickscope', 'scope://com.canonical.scopes.news_unity-scope-news', 'scope://musicaggregator', 'scope://videoaggregator', 'scope://com.canonical.scopes.photos_photos']"` to get back your list [08:23] thanks [08:23] but the reset is scary, /me flashes krillin to see in a moment [08:24] this would mean that the custom tarball doesn't override the default [08:24] but that'd be *really* weird [08:24] Saviq, why would it [08:24] Strange, I don't see the today scope update on my krillin, huh [08:25] the custom tarball installs what is in it as upgrade time, thats it ... if there is a newer version of something it ships in teh store this will always override [08:25] sil2100, because it was unpublished already :) [08:25] ogra_, I meant the gsettings key [08:26] ogra_, the default list of favourite scopes is just apps, music, video unless it's overridden by custom tarball [08:26] the default is likely schipped as system wide schema ... [08:26] Ah, it was already, ok ;) [08:26] so if the user has the key set, it will override the system one [08:26] ogra_, which is why going `gsettings reset ...` should get it back [08:26] yeah [08:27] it doesnt ? [08:27] ogra_, and popey did the reset, and was presented with just the 3 scopes [08:27] http://people.canonical.com/~alan/clicks/com.canonical.scopes.dashboard_1.7.15_armhf.click is the offending click if you really want it sil2100 :) [08:27] this is what makes me wonder [08:27] popey: thanks ;) [08:27] Mirv, confirmed silo 15 makes CPU settle [08:28] Saviq: thanks! I tested both that use case and the one I found. [08:33] jibel: ping [08:42] ogra_, oh, they're not using gsettings overrides but a dconf one... [08:45] lovely [08:51] ogra_, popey, sil2100, IMO a bug in unity-scopes-shell, letting pete-woods know [08:51] pete-woods, https://bugs.launchpad.net/today-scope/+bug/1446499/comments/12 [08:51] pstolowski, ↑ [08:51] Ubuntu bug 1446499 in unity-scopes-shell (Ubuntu) "Updating today scope from store kills scope, doesn't restart" [Undecided,Confirmed] [08:52] ogra ping [08:52] victorp, hey [08:52] just saw the pings from you and popey, whats up? [08:53] victorp, today scope in the store is broken [08:53] victorp, we unpublished it, but it went out to ~350 users [08:53] ok.. [08:53] what are you installing it on? arale or krillin? [08:53] krillin stable [08:53] victorp: on krillin [08:53] retail devices [08:53] ogra_, victorp, I wouldn't say "the scope is broken" any more [08:54] well, the user exüperience is broken once you install the update :) [08:54] it's the update process that's broken [08:54] ("the scope is broken is shorter :P ) [08:54] yeah ok, details on the bug [08:54] Saviq: ok, might indeed be the case here [08:54] Saviq, well, it also didnt get any QA it seems [08:54] Although I think that updating the scope without QA is a bad thing in overall [08:55] ogra_, sure, FWIW I'd say the problem is race-y, too [08:55] yeah [08:55] so not everyone will hit it [08:55] Some people said it was fine for them [08:56] sil2100: where? at least on the bug report the reply was "fine if you readd it" if I understood it correctly. [08:56] Mirv: on the mailing list [08:56] sil2100: oh, ok. good if it doesn't hit everyone. [08:57] ogra_, sil2100 first of all , dont make things up [08:57] :) [08:57] Mirv: one person said that he upgraded and today scope remained on the favorite list [08:57] sil2100: so it seems [08:57] Saviq, commented, it's as you described [08:57] if you have a scope favourited and you updated it to a new version it *always* removes it from the fav list [08:57] Saviq, ^^ [08:58] but should still appear in your bottom edge list [08:58] victorp, ugh [08:58] victorp: so that's by design? [08:58] i thought that had been reported, it happens to me with the child scopes we favourited [08:58] victorp, yeah, that's correct, but shouldn't be the case should it [08:58] well seems like bad desing :) [08:58] ;) [08:58] that sounds pretty broken ... like if an update would remove the icons i added from the launcher [08:58] right, I thought it was a bug that had been reported , my bad for not checking [08:59] ogra_, agreed [08:59] so the more concerning part would be why is not appearing in the bottom edge with respect today scope [08:59] victorp, good that we catched it then ... better if a QA test had catched it before it went to the store though :) [09:00] do we have phased store updates in plans similar to image updates? [09:00] ogra_, it wouldnt, because this only happens if you update from the scope, if you update custom is doesnt [09:00] victorp, so it's not appearing on the bottom edge list under 'Also installed' ? [09:00] victorp, well, a new music app doesnt go into the store without QA run ... this scope apparently did according to QA [09:01] also i thought it is in the manage scopes tool, but under new name ? [09:01] ogra_, what are you talking about? [09:01] This is one of the holes in the process, every new click that's by default on the image and gets upgraded needs QA sign-off [09:02] Even the today scope [09:02] victorp, with what exactly ? [09:02] victorp, that the scope didnt get QA before oing to the store ? [09:02] I am telling you the scope is not broken, is the "update a scope from the store" process that is doing this , you just have notice it now [09:02] *goin [09:02] ah ! [09:02] right, i didnt get that ... [09:02] pstolowski, so reading the bug from popey it appears after reboot [09:03] victorp: only if you re-add it. [09:03] popey, in the manage... list [09:03] yes [09:03] popey, what do you mean by re-add it? [09:03] victorp: from user point of view it's gone for good and doesn't come back. I didn't find it in the management either untils someone told it that it's in there. [09:03] sorry, re-favourite it [09:03] popey, ack [09:04] ok, first of all - this has nothing to do with the today scope [09:04] popey, well, this was about: is it in the manage scopes area only after a reboot or is it there right after upgrade [09:04] that is the behaviour of all scopes you update from the sore [09:04] store [09:04] ok. [09:04] so it's two problems actually; manage list didn't refresh until reboot, and the scope needed to be favorited again [09:04] if it wasnt in the bottom edge after update and then shows after a reboot, that still has nothing to do with the scope [09:04] But the fact that it's the default first scope, it uncovers a bug [09:04] sure [09:05] pstolowski, +! [09:05] +1 [09:05] popey, exactly [09:06] as far as I can tell the team is just publishing to the store scopes that where added to custom-proposed , which is tested ogra_ [09:06] I didnt get an update notice [09:06] because we unpublished it [09:06] i pulled it from the store around 40 mins ago [09:06] but if they had to change the version for whatever reason, it would have trigger it [09:06] and you dont get noticxes for apps/scopes [09:06] i.e. change on mantainer name in manifest [09:07] so I dont think qaing this more would have helped, what we need is the beta/alpha channel in the store so we can test upgrades [09:07] I believe beuno's team is already working on that [09:07] well if someone had installed the click on a retail bq device they would have noticed the scope disappear [09:07] so, can we open 2 bugs to track the issues that pstolowski has highlighted [09:07] and hopefully file the right bug? [09:08] right, we would at least have catched one of the issues here [09:08] but I suspect nobody QA'd it on a _retail_ bq image. [09:08] because that's the only one shipping it by default [09:08] popey, I understand that this issues are new to you, but we have know about them for a while, I just thought they were being addressed [09:08] or they did, and ignored the fact that the scope disappeared [09:08] popey, more probably that [09:08] victorp: new to me and thousands of bq retail handset owners [09:09] yeah [09:09] popey, ok and? I am not sure what you are asking me? [09:09] ok. where is the bug tracking the fact that scopes disappear, and need a reboot? [09:09] I think we need two bugs for that [09:09] the assumption that things are being fixed because "we read:I already know about them" is a broken process. [09:10] can you please open them popey? [09:10] i opened one, I don't know what the second one is. [09:10] popey, sure - if you expect me to find all the bugs that is also broken :) [09:11] I didn't say you. I implied QA [09:11] If someone is QAing something and they spot something is broken, I'd expect a bug. [09:11] my point being nobody filed a bug for these issues because "we know about it" [09:11] victorp, if you found that bug before (knew about it), someone must have seen it but not filed it ... thats the broken part [09:11] but yeah, I'll file the bugs for you. [09:11] exactly [09:12] anyway, this is going in circles, there are two bugs in unity8 Saviq.. favouriting does not survive an update from the store , and the bottom edge/manage dash does not seem to always register updates. [09:12] victorp, when interacting with the users it helps if we can point to a bug [09:12] let me know if you need anything else [09:12] ogra_, 100% agreed [09:12] i.e. popey could have pointed it out in the warning mail he sent [09:13] victorp, both are unity-scopes-shell bugs [09:15] Saviq, ack [09:17] Saviq, are you happy just tracking the issues on 1446499 [09:18] i added a second [09:18] bug 1446536 [09:18] bug 1446536 in unity-scopes-shell (Ubuntu) "Scope disappears from bottom edge on update" [Undecided,New] https://launchpad.net/bugs/1446536 [09:19] victorp, popey, thanks [09:19] ta! popey [09:20] pstolowski, one more related, not sure if that's -scopes-shell exactly or the scope backing Manage Dash ↑ [09:20] so do we re-publish today in the store? [09:20] because this is a "known" bug? [09:21] I think it's really bad from user pov [09:21] well [09:21] yeah, but then otherwise we'd block any core scope updates until we release the next OTA... [09:21] we dont have a system update planned [09:22] well right, true [09:22] so the fix wont land before next OTA [09:22] people will learn to use scopes at least.. [09:22] i wonder if there is a way to hack around it from the scopeside [09:22] ogra_, not likely [09:22] Saviq, ok, so this is the second problem from the 1st bug [09:22] yeah, i was fearing that [09:23] ogra_, it's basically a case of "oh, the scope went away, let's drop it from favourites" [09:23] so either we live with the bug (very bad imho) and re-publish ... or we hold back all scope changes til it is fixed [09:24] pstolowski, [09:24] https://bugs.launchpad.net/today-scope/+bug/1446499/comments/16 [09:24] Ubuntu bug 1446499 in unity-scopes-shell (Ubuntu) "Updating scope from store removes it from favorites" [Undecided,Confirmed] [09:25] victorp, any opinion ? [09:25] Saviq, yeah, that would be simple to do, but would mean we never get rid of uninstalled scopes. unless we purge at startup [09:26] pstolowski, hook on uninstall won't do, as it's based off of the .ini file already? [09:27] Saviq, sorry, i can't parse what you're saying ;). i'm just talking about the plugin which purges favorites whenever registry is updated (and scope disappears) [09:28] pstolowski, sure, I'm saying that a hook on uninstall could trigger the removal from favourites, unless this is basically what happens already? [09:29] * Saviq wonders how relevant this discussion is in light of "scopes as apps"... [09:29] Saviq, ah, no. it's handled completly by the shell [09:29] * shell plugin [09:29] Saviq, yeah, becomes irrelevant then ;) [09:29] well, kinda [09:30] it just moves from Manage Dash to $wherever_we_store_favourites (like in click scope or something, to display at the top) [09:47] jibel: o/ i'm trying to get an idea whether silo 6 is considered for testing, or if there is something blocking landings in the overlay ppa [09:48] i may have another silo next, with branches targeted for desktop (w updates and potential srus); let me know [09:56] dbarth, it is in the triaged queue, it should be verified soon-ish [09:57] ok, nw [09:57] trainguards, point of procedure: do I need to get an ACK from the Ubuntu release team first to land silo ubuntu/landing-020 (#1446256) or does it just land and go into the UNAPPROVED queue and get ACKed from there? [09:57] jibel: thanks [09:58] bregma: we could publish it without an ACK, but it's best to coordinate beforehand especially if the bug that's being fixed is not set to critical [09:59] bregma: without the ACK it would en up in UNAPPROVED, but might get rejected due to lack of infromation etc. [09:59] sil2100, thanks [10:01] sil2100: bregma: since it's seeded I think it's even required to go via release team https://wiki.ubuntu.com/FinalFreeze [10:01] for example qtcreator-plugin-ubuntu was unseeded universe package but unity is a different beast [10:02] anyway, it's still >1.5 days so it's ok to go to vivid normal instead of proposed [10:04] davmor2: Bq now passes my official seal of approval requirements when I'm now writing this from Bq after using a menu shortcut to login + screen -dr and I've added Ctrl-D, Ctrl-P and Ctrl-N to the ctrl menu [10:04] sil2100, Mirv bregma if it is ready publish it, we need it on the image [10:04] jibel: ok [10:05] Mirv: let me publish the unity silo then [10:05] sil2100: ok [10:05] The release team will deal with it ;) [10:06] that's right, pass the buck [10:07] Mirv: it did anyway, I told you you were just using it wrong ;) [10:07] davmor2: that too :) [10:08] Mirv: did you like the osm touch app by the way? [10:08] Mirv: and don't play uu or we'll lose you forever :D [10:10] davmor2: the osmtouch is a familiar one to me, I've used it mako quite a bit. even though I didn't use mako "really really" (so this Bq is what I really give my "normal use case" for), I did use it for browsing and location [10:11] davmor2: it's ok but I need something closer to Osmand~ - offline vector maps, voice navigation [10:11] and if I would have click chroot creation not broken on my vivid I'd give a Navit or Marble a try to get something built [10:11] but alas I've not found the reason why click is totally busted on my machine [10:11] Mirv: here does turn by turn it you switch down to walking rather than driving :) [10:12] davmor2: here is closed source, I want OSM maps too :) [10:12] I prefer OSM in general even without closed/open over google maps and here maps [10:12] Mirv: whine whine whine ;) [10:13] just so much more "love" into details in there, like stairs, tree locations or cow locations when people go crazy in details :) [10:13] well maybe not cow unless there's real time tracking objects feature in OSM [10:13] davmor2: no I just want to make it win win win for me :) [10:13] Mirv: it's not working because it hates you, hate it back it works for me ;) It might be all the dev stuff you have in place for other stuff is interfering maybe? [10:14] davmor2: :) I won't install any dev stuff on the Bq (except for stuff like customizating terminal settings etc). but no apt etc hacking. [10:15] Mirv: what you really need is a new dell laptop and a fresh install of vivid that will fix it and your broken screen too :D [10:15] oh right the chroot, yes [10:15] davmor2: I'd like to understand the actual bug in there, I've already gone through two difficult ones but it still now fails at the end of it (used to be: in the beginning) [10:16] but it's annoying since at the end of click chroot creation it wants to unmount my encrypted home after which my desktop is busted [10:16] Mirv: blame pitti or ogra that normally gets things fixed ;) [10:16] davmor2: I don't blame anyone, I file bugs! [10:17] Mirv: you do it all wrong don't you :D [10:17] but true, I'll get a fresh machine soon (~month?). but I hate it when there's some bug that might really affect other people too. [10:18] I'm sure other people are running into that previously filed bug #1436835 too [10:18] bug 1436835 in click (Ubuntu) "click chroot build fails on vivid" [Undecided,New] https://launchpad.net/bugs/1436835 [10:20] Mirv: you could try throwing a kvm install or an lxc install and try running it in there and then figure out the difference between the base install and the version on your desktop to figure out why it hates you [10:20] Mirv: I wonder if it is the QT versions you are building playing havoc with the system maybe? [10:20] davmor2: true, although I can also just run 14.04 LTS from my server and do stuff there [10:20] davmor2: no, I [10:21] davmor2: 'm not building Qt on this machine, but in a chroot on my server machine [10:22] davmor2: similar to that filed bug ^ I've messed around with schroot before and configuration files a lot, and ideally click would detect the most common misconfigurations instead of blowing up [10:22] Mirv: are you testing the QT packages on that machine though? Ie is it expecting to install qt 5.3.1 and getting qt5.3.4 that you've installed or something crazy like that? [10:22] davmor2: one problem is that I've already checked everything I can regarding click & schroot against a clean install and I fail to find anything relevant. that way I found that missing fstab in that previous report. [10:23] davmor2: no, and since Click creates a fresh chroot it does not care what's on the host system [10:23] oh well yes, I do occasionally have Qt PPA:s here and test them, but I also purge them afterwards === MacSlow is now known as MacSlow|lunch [10:53] popey, hey, any idea how can i test a potential fix for the problem of today scope update, without you actually publishing it? [10:56] (i need any scope update to test it) [10:57] pstolowski: good question [10:58] pstolowski: maybe someone on the team has a scope of some kind that we can push to the store under a new test name? [10:58] popey: pstolowski: surely you can just install it locally? [10:58] that could work too, but does the problem trigger with pkcon? [10:59] popey: I'm assuming pkcon is doing the installing from the update [11:00] worth testing in both ways [11:01] davmor2, popey that sounds like a good suggestion; isn't it 'click install --local...' that i need? [11:02] I tend to "pkcon install-local --allow-untrusted foo.click" [11:02] ok [11:03] pstolowski: ^ what he said [11:03] yeah, thanks [11:03] popey, the fix goes only into vivid i presume? [11:04] well as I understand it there will be no more rtm-1409 / utopic based OTAs so vivid makes sense, but check with sil2100 [11:04] Yeah [11:05] sil2100, popey ack [11:05] victorp, who can provide me with an updated version of today scope .click? [11:05] cwayne or kylen [11:06] ty [11:12] victorp, so whats our plan forward, do we hold back scope landings until after next OTA ? [11:12] ogra_, landings to? [11:12] since the fix can only come from a OTA [11:12] scope landings to the store [11:13] yes, at least for the agregators [11:13] that are currently favourites [11:13] ok [11:13] pstolowski, whats up? [11:13] we can still update them via OTA [11:13] that seems to work fine [11:13] yeah [11:14] in general that shows a problem though ... [11:14] being stuck with store landings because we need an OTA for the underlying fix [11:14] i wonder if there is a way around [11:16] ogra_: include the fix in a store package but then that would get messy [11:17] davmor2, well, in this case we couldnt [11:17] cwayne, sent you an email. bbiab === pstolowski is now known as pstolowski|lunch [11:17] davmor2, a click cant ship system bits ... and the rootfs would even have to be writable to replace the broken parts [11:18] in snappy, where the system bits will be framewworks, this will be fixable via the store [11:18] ogra_: unless it is in core [11:19] well, core is small enough that it shouldnt affect us [11:19] but yeah === MacSlow|lunch is now known as MacSlow === chrisccoulson_ is now known as chrisccoulson === greyback__ is now known as greyback === _salem is now known as salem_ [12:06] sil2100: moving back over here. i see pstolowski|lunch is going to talk to cwayne when he wakes. [12:06] sil2100: lets wait for that conversation to happen. [12:06] sil2100, i've been here :) got him a click [12:06] oops popey ^ [12:06] there we go :) [12:07] thanks cwayne (sorry for all the pings) [12:07] 7:30AM meetings ftw [12:07] :) [12:07] or ftl i guess :P [12:07] wake up and the whole worlds on fire [12:08] cwayne: ;p [12:08] Ok, let me wait for pstolowski|lunch to give some input and then we decide [12:08] I want to know how hard this will be to fix [12:09] Well, hm, actually, since this happens in stable there's no way to fix it proper I suppose [12:10] So I'm sure we'll just re-publish it in a few moments === pstolowski|lunch is now known as pstolowski [12:33] sil2100, i'm working on a fix for first part of the issue (https://bugs.launchpad.net/today-scope/+bug/1446499), should have a fix for vivid today [12:33] Ubuntu bug 1446499 in unity-scopes-shell (Ubuntu) "Updating scope from store removes it from favorites" [Undecided,In progress] [12:33] cwayne: I know giving you that petrol can for christmas was a bad idea [12:33] knew even [12:34] sil2100, and there is a slight chance https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1446536 is not affecting vivid, but i haven't checked yet [12:34] Ubuntu bug 1446536 in unity-scopes-shell (Ubuntu) "Scope disappears from bottom edge on update" [Undecided,Confirmed] [12:34] pstolowski: I suppose all of those issues require changes on the scopes infra, right? [12:35] In this case I guess we can re-publish the scope to the store, nothing we can do short term to fix this [12:35] sil2100, only unity shell plugin [13:01] pstolowski: then I think there's no use holding up the today scope [13:01] pmcgowan: ^ I'll ask popey to re-publish the today scope to the store [13:03] sil2100, I thought there is an issue replacing favorite scopes, or did I miss something [13:03] pmcgowan: there is an issue, but to fix it we would need to promote an image with a quick-fix which is still in progress, not sure if we want that [13:03] sil2100, we shouldn't put it back until that issue is fixed [13:04]