[05:50] <freislot> hello nerds :)
[07:27] <pitti> ogra_: oh, do we need to rebuild ubuntu-touch-meta?
[07:27] <pitti> ah yes, we do
[07:28]  * pitti turns the crank
[07:35] <pitti> ogra_: uploaded
[09:06] <ogra_> pitti, gah, there was a revision missin from vivid
[09:15] <JamesTait> Good morning all; happy Stress Awareness Day! :-D
[09:22]  * tbr becomes aware, jumps JamesTait and strangles him
[09:22] <tbr> I'm not stresssse!
[09:23] <tbr> looking for a job is not stressful at all, nope. Especially if some companies just don't respond at all, despite their promises.
[09:25] <JamesTait> tbr, you have my sympathies - been there, done that (while my wife was four months pregnant with our second child).
[09:26] <tbr> oh dear, that must have been much much more stressful
[09:27] <JamesTait> tbr, it wasn't a nice situation to end up in, but to be fair to the company who was making me redundant (they lost a big contract, restructured and my part of the company was surplus to requirements) they did take a lot of the stress out of it by paying me during my notice period, but not making me work.
[09:28] <tbr> something at least
[09:28] <JamesTait> Small things can make a big difference.
[09:52] <vesar> Does anybody know if mzanetti will be around today?
[10:30] <ogra_> pitti, we have a slight problem and i'm a little lost how to fix it ... i need the same seed change in rtm, since we dont have rtm seeds and vivid is out of sync i cant just binary sync the meta package now
[10:30] <ogra_> (which is what we used to do in utopic)
[10:32] <ogra_> re_building the meta package from rtm will make germinate use utopic, not rtm, so the dropped langpack wont be recognized (and we cant remove it from utopic now)
[10:32] <seb128> does anyone else get the gallery-app displaying spinners for like 10s every time it's started
[10:33]  * ogra_ isnt sure if cjwatson is around today to ask him about this ... 
[10:33] <seb128> it's slooow to load image previews
[10:33] <ogra_> seb128, check with top ... i bet there is something else going on
[10:33] <seb128> ogra_, no, I think it's https://bugs.launchpad.net/gallery-app/+bug/1381585
[10:33] <ogra_> (we have quite a lot issues with some processes using 100% CPU recently)
[10:33] <seb128> it's regenerating the previews every time
[10:33] <ogra_> ah, yeah, thats bad too
[10:33] <seb128> but arthur claimed on that bug that he doesn't see the issue anymore
[10:33] <seb128> but I still do
[10:34] <seb128> so I was wondering if I was alone in that case
[10:35] <didrocks> seb128: but even with no image, it's taking like 4-5s to load up (what I saw from a recent rtm video)
[10:35] <didrocks> with this spinner
[10:35] <seb128> didrocks, yeah, loading time is another issue
[10:35] <didrocks> so maybe there are 2 issues there
[10:35] <ogra_> sounds like it isnt properly using the precompilation
[10:35] <didrocks> the preview + something else making it spin for a long time even with no image
[10:35] <seb128> well, app being slow to start is a common issue on krillin
[10:35] <ogra_> huh ?
[10:35] <didrocks> seb128: I mean, the in-app spinner
[10:35] <seb128> the device is not that performant and qml is slow
[10:36] <ogra_> apps start in under 2sec for me
[10:36] <didrocks> so the app is already started
[10:36] <ogra_> since we have the qml precompilation stuff
[10:36] <seb128> ogra_, depending of the app, try starting setting and see how long you get the splash
[10:36] <seb128> didrocks, ok, I can't tell, I've a good stack of photos and no empty device to test
[10:36] <ogra_> well, settings was always slow
[10:37] <seb128> didrocks, in my case I see a spinner for each image and the grid filling slowly
[10:37] <ogra_> ~3 sec here
[10:37] <ogra_> (admittedly slower than others)
[10:37] <seb128> yeah, well they are okish
[10:37] <seb128> still it's not "click, it's there"
[10:37] <ogra_> heh, no
[10:37] <seb128> it takes some 2-3s for several of the apps
[10:39] <didrocks> seb128: https://www.youtube.com/watch?v=_DtNvz_WVu8#t=43
[10:41] <seb128> didrocks, the start of the video?
[10:42] <seb128> yeah, that's not the same bug/not a bug
[10:42] <seb128> they do lazy loading to start the app with less delay
[10:42] <seb128> so you get the main chrome then it's doing the loading of other objects
[10:42] <seb128> which is the time during which one you get the in app spinner
[10:45] <didrocks> seb128: oh ok, making sense
[10:58] <ogra_> oh what a mess :(
[11:23] <pitti> ogra_: well, utopic's touch-meta is fine, why do you need to rebuild it?
[11:24] <pitti> ogra_: AFAICS we need to rebuild rtm's -meta (and of course point it to the RTM archive, not utopic)
[11:24] <ogra_> pitti, to sync it to rtm
[11:24] <ogra_> there is no "rtm's meta" :)
[11:24] <ogra_> thats the issue
[11:24] <ogra_> (nor are there rtm seeds ... )
[11:25] <pitti> ogra_: the same seeds should work, it just needs to use RTM archive's archive
[11:25] <ogra_> colin just advised me to hack the meta package directly ... lets see
[11:25] <ogra_> pitti, right, that bit i was able to hack
[11:25] <ogra_> sadly germinate also uses debootstrap at some point
[11:25] <ogra_> which doesnt know about rtm or 14.09
[11:26] <pitti> ogra_: sure, hand-editing the -meta files works well, too
[11:26] <ogra_> we dont have a "utopic" in the rtm archive
[12:10] <oSoMoN> rpadovani, hey, I don’t know if you’ve seen it, I commented on https://code.launchpad.net/~rpadovani/webbrowser-app/1351165/+merge/238197
[12:11] <rpadovani> oSoMoN, oh, thanks, I missed it: I'll take care in next days
[12:11] <ogra_> oSoMoN, i had some sorrying webapp and browser crashes the last two days ... sadly what the crash file spits out is rather sparse https://errors.ubuntu.com/oops/1e65bb3a-6450-11e4-87c8-fa163e373683
[12:12] <ogra_> oSoMoN, the symptom is that the app or the browser hangs hard for a while and then simply vanishes
[12:12] <ogra_> afaik rsalveti has seen it too
[12:13] <oSoMoN> ogra_, where can I get to the crash file?
[12:14] <ogra_> well, the above is the crash file
[12:14] <ogra_> there is nothing in it
[12:14] <ogra_> (this is identical to what you get in /var/crash ... just uploaded to errors.u.c)
[12:15] <oSoMoN> ah, so no backtrace at all? :/
[12:15] <ogra_> right
[12:15] <ogra_> but there is something going on ... i'll tell you if it happens again
[12:16] <oSoMoN> ogra_, ok, thanks
[12:17] <ogra_> it obviously got a SIGSEGV
[13:11] <mpt> Trivia question: How many Ubuntu packages make up the Ubuntu Touch image?
[13:12] <ogra_> ogra@styx:~$ wget -O- -q http://cdimage.ubuntu.com/ubuntu-touch/ubuntu-rtm/14.09/daily-preinstalled/pending/14.09-preinstalled-touch-armhf.manifest|wc -l
[13:12] <ogra_> 1048
[13:12] <ogra_> ogra@styx:~$
[13:12] <ogra_> mpt, ^^ trivia answer :)
[13:12] <mpt> Thanks ogra_ :-)
[13:12] <ogra_> (thats not 100% accurate, there are some click packages listed too)
[13:12] <mpt> So 1048 out of the 48888 packages in the Ubuntu archives
[13:13] <tbr> is it really that many per release?
[13:13] <ogra_> ogra@styx:~$ wget -O- -q http://cdimage.ubuntu.com/ubuntu-touch/ubuntu-rtm/14.09/daily-preinstalled/pending/14.09-preinstalled-touch-armhf.manifest|grep -v ^click:|wc -l
[13:13] <ogra_> 1029
[13:13] <ogra_> ogra@styx:~$
[13:13] <ogra_> thats better :)
[13:14] <ogra_> these are indeed binary packages ... source is far less
[13:26] <pmcgowan> popey, I like the new music app, niiice
[13:27] <popey> Good! :D
[13:27] <daker> popey: do you have a .click somewhere ?
[13:28] <popey> daker: https://lists.launchpad.net/ubuntu-phone/msg10380.html
[13:28] <daker> popey: thanks!
[13:39] <seb128> didrocks, btw the gallery issues I had earlier were due to a buggy file, the code doesn't handle that well and wipe the cache and try to rebuild it when that happens it seems
[13:39] <seb128> works fine after deleting the file, not respinning, etc
[13:45] <gcollura> does anyone know about this? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389698
[13:51] <mterry> pmcgowan, did someone say you knew how to fake having two locked SIMs?
[13:53] <pmcgowan> mterry, fake? no dont think so
[13:53] <pmcgowan> I have two actual sims
[13:53] <pmcgowan> mterry,have you tried with phonesim?
[13:54] <mterry> pmcgowan, I know how to fake one locked sim by editing /usr/share/phonesim/default.xml
[13:54] <mterry> pmcgowan, but couldn't see settings for 2
[13:54] <pmcgowan> ah
[13:54] <pmcgowan> jgdxx, or Wellark  might know
[13:55] <mterry> and there are some sort of instructions for launching two emulators on your desktop while talking with the phone?  But I couldn't get them to work (they are old instructions): https://docs.google.com/a/canonical.com/document/d/1VTl0urE-caZSmv3sUqPQs2A2NKC4VHMf20XSq7n2pKU/edit
[13:55] <mterry> pmcgowan, where do you get locked SIMs in the states?
[13:55] <pmcgowan> mterry, you can lock any of them, I have locked tmobile and att
[13:56] <mterry> ah...
[13:56] <pmcgowan> mterry, they have default passwords, 1234 and 1111 as I recall
[13:56] <mterry> pmcgowan, can we lock via UI?  or is there a command line trick for that?
[13:56] <pmcgowan> yes via settings
[13:56] <mterry> ok, will stuff two sims in my guy then
[13:57] <pmcgowan> good luck
[14:11] <mpt> Cannot push /home/mpt/.cache/ubuntuimages/pool/ubuntu-fd170ac8424783a9e5db270f34f255b5a2087584e7a32582e1a79b009d652e31.tar.xz.asc to device: free space on /cache/recovery is 432M
[14:12] <mpt> How do I fix this?
[14:18] <mpt> Ah, trying it without --wipe seems to be working
[14:22] <mterry> boiko, so we can call unlockAllModems() but we can't cancel that, right?  Like, if one unlock comes through, we can't cancel the second before it shows, can we?
[14:23] <Wellark> mterry: you can edit the default.conf if you want to do it locally
[14:24] <Chipaca> larsu: the push client just requested to remove an entry, and the messaging indicator failed to do so (log has “g_menu_remove: assertion '0 <= position && position < menu->items->len' failed”). Is this us doing something wrong, or you?
[14:24] <mterry> Wellark, I've figured out my locked SIM situation -- discovered how to lock normal SIMs and found two SIMs.  So I'm going authentic.  But do you know about the above question ^ ?
[14:24] <Wellark> mterry: https://wiki.ubuntu.com/Process/Merges/TestPlan/indicator-network#Dual-Sim_testing
[14:24] <Wellark> mterry: about emulator?
[14:24] <Wellark> no idea..
[14:25] <mterry> Wellark, no about unlockAllModems
[14:25] <mterry> Wellark, right before you messaged me a moment ago
[14:25] <mterry> Wellark, I should have asked you instead of boiko, you're probably more likely to know  :)
[14:30] <larsu> Chipaca: that's not your fault, it should never happen. Do you have a backtrace?
[14:30] <Chipaca> larsu: it happened to seb128
[14:30] <larsu> or better, some way to reproduce :)
[14:31] <seb128> no and no
[14:31] <larsu> uh oh
[14:31] <larsu> seb128: is this related to the | crasher?
[14:31] <seb128> no
[14:31] <larsu> (which, btw, is almost fixed)
[14:31] <seb128> that happened on the phone
[14:31] <seb128> my messaging menu has 2 "system update available" entries
[14:32] <seb128> Chipaca, said it should have cleared the first one
[14:32] <seb128> Chipaca, larsu, btw seems you started that discussion somewhere else? so I'm unsure if you discuss the duplicate item or the warning
[14:32] <larsu> I just started discussing this
[14:33] <seb128> the indicator log had that warning, dunno if it has to do with the duplicate
[14:33] <larsu> only about the warning
[14:33] <larsu> but seems related: if it fails to remove an item, you might get two...
[14:33] <seb128> right
[14:34] <Wellark> mterry: correct. you don't have any control after you call UnlockAllModems()
[14:36] <larsu> seb128: I can review if remove_message() does the right thing, but it would be great if I weren't doing so blindly
[14:36] <seb128> larsu, don't bother, it's a one time thing
[14:37] <larsu> seb128: ok
[14:37] <seb128> larsu, but I do get "g_object_unref: assertion 'G_IS_OBJECT (object)' failed" in my log after a reboot, going to get you a bt for those and maybe you can have a look?
[14:37] <larsu> seb128: uh oh. yes please
[14:41] <mterry> Wellark, ok the more I look at this, the more I think unity8 needs a way to tell connectivity service that it shouldn't show the queued sim unlocks
[14:42] <mterry> Wellark, either by responding a certain way to the current unlock or by making a separate dbus call.
[14:42] <mterry> Wellark, thoughts?
[14:43] <seb128> larsu, https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1389725
[14:44] <larsu> seb128: ah, appinfo2 == NULL in #2. Probably a check missing. Thanks
[14:44] <seb128> larsu, yw!
[14:44] <seb128> larsu, sign of a buggy client as well maybe?
[14:44] <larsu> seb128: likely, but we should deal with this gracefully
[14:44] <larsu> seb128: at least we should print a more meaningful error
[14:44] <seb128> larsu, right, just saying that we should maybe fix the client as well
[14:45] <larsu> right
[14:47] <Wellark> mterry: umm.. what's the use case?
[14:47] <Wellark> I need to understand that first
[14:48] <mterry> Wellark, I suppose my suggestion isn't 100% necessary -- we can cover this in unity8 alone.  But still might be useful.  Here's the use case:
[14:48] <mterry> Wellark, user boots with 2 locked sims
[14:48] <mterry> Wellark, on first unlock sim dialog, they click the 'emergency call' button
[14:48] <mterry> Wellark, user expectation is likely that the next thing they see is the emergency dialer, rather than the second unlock dialog
[14:49] <Wellark> mterry: sure.
[14:49] <mterry> Wellark, we can fake it in unity8 by not showing sim unlock dialogs when in emergency mode
[14:49] <seb128> larsu, I posted a second bt, likely the same issue, the first warning is a "g_app_info_equal: assertion 'G_IS_APP_INFO (appinfo2)' failed" the other one ag_object_unref one
[14:49] <Wellark> mterry: but IMO that is indeed the responsibility of unity8 to make sure once we are in emergency dialer mode that no dialogs or snap decisions or anything can occupy the screen
[14:49] <mterry> Wellark, but if we ever show the panel in emergency mode, then we would have a hard time telling between user-initiated unlocks and the startup unlocks (and we'd want to show one but not the other)
[14:50] <mterry> Wellark, we can fake it now because we happen to not show the panel
[14:50] <Wellark> mterry: I would say that the emergency mode is a corner case and if the user hits it, then after the call is done he can go to the indicator and unlock the sims manually
[14:50] <mterry> Wellark, but I don't think we can forever simply say "show no snap decisions"
[14:50] <Wellark> mterry: no snap decisions while in emergency call mode
[14:51] <Wellark> emergency call mode must be handled separately by unity8 anyway
[14:51] <mterry> Wellark, oh come on, if we show the panel and a button that says unlock sim, it's not acceptable to have that button do nothing
[14:51] <larsu> seb128: thanks!
[14:51] <seb128> larsu, thank you for looking!
[14:51] <mterry> Wellark, again, not an urgent problem.  But I think it makes sense to be able to stop that initial unlockAllModems call somehow in this case
[14:51] <Wellark> mterry: sure. it's not acceptable for the button to do nothing
[14:52] <Wellark> mterry: but also
[14:52] <Wellark> if we are in emergency call mode
[14:52] <Wellark> the user should not be able to do anything else than make the emergency call
[14:52] <Wellark> so no access to indicators or anything that might distract the emergency call
[14:52] <mterry> Wellark, but unlock sim also allows incoming calls
[14:52] <mterry> Wellark, right...  as I said, today we don't show the panel/indicators
[14:52] <Wellark> I hope unity8 has a special emergcy call mode..
[14:52] <mterry> Wellark, I'm not arguing we should change that right this second
[14:53] <mterry> Wellark, just arguing for why there is a possible need for canceling the unlockAllModems sequence
[14:53] <Wellark> as the shell has to react differently when emergency call is being placed. not saying that it must happen today, but something we need to think about during the next iterations
[14:53] <Wellark> mterry: ack.
[14:53] <mterry> Wellark, we do have a special emergency call mode already!  And we don't show indicators
[14:54] <Wellark> mterry: good. so what's the problem? sorry, I think I'm lost
[14:54] <Wellark> as if the indicators are not shown
[14:54] <Wellark> then there is no way to access the "unlock sim" button
[14:54] <mterry> Wellark, imagine that the Design team comes to me tomorrow and says "we'd like to show the indicators in emergency mode too"
[14:54] <Wellark> that would trigger the snap decisions
[14:55] <Wellark> well, then we advice them that it's not a good thing to do
[14:55] <mterry> Wellark, in that case, merely saying "no snap decisions in emergency mode" no longer cuts it
[14:55] <Wellark> emergency mode is special, and everything that is not absolutely necessary for the call to succeed must be dropped
[14:56] <Wellark> app switches, indicators, notifications, background processes...
[14:56] <mterry> Wellark, that is a Design/legal decision, not an engineering one
[14:56] <Wellark> in emergency phone the device must have just single function and that is to place the call
[14:56] <Wellark> mterry: sure.
[14:56] <mterry> Wellark, so...>
[14:57] <mterry> Wellark, are you still arguing against the idea that unity8 should be able to cancel the sequence of modem unlocks?
[14:57] <Wellark> so, right now unless there is a design decision that states that the indicators must be accessible and that would allow the user to access the unlock sim buttons then we figure out what to do
[14:58] <mterry> Wellark, again, in no situation here am I arguing that you need to do any work right now
[14:58] <Wellark> mterry: that's not feasible, unless we provide more accurate API for the whole unlocking experience
[14:58] <Wellark> and I'm all open to discuss new API's
[14:58] <mterry> Wellark, I'm just trying to get you to agree that it is sensible for the connectivity service to give a modicum of control to unity8 over the unlock sequence
[14:59] <Wellark> but as with any API design we need to evaluate the features carefully
[14:59] <Wellark> mterry: agreed.
[14:59] <Wellark> mterry: the whole unlocking must be reworked anyway
[14:59] <Wellark> as snap decision will not cut it
[14:59] <Wellark> once we have the dialogs for unity8 I'm sure we can tag them with some reasonable way
[15:00] <Wellark> so that unity8 also can reason about the dialogs it's being asked to show
[15:00] <Wellark> and prioritize them
[15:01] <Wellark> mterry: we are all good? :)
[15:02] <mterry> Wellark, sure...  in so far as I don't actually need anything yet.  But I don't think if I did, we would need to redesign the whole thing.  Just let unity8 respond to the notification in a way that specify "user is cancelling this sequence of unlock dialogs" instead of the only option right now: "user is cancelling *this* unlock dialog"  but yeah, we don't have to argue about it
[15:02] <Wellark> I think we agree here
[15:03] <Wellark> mterry: I totally agree with that above
[15:03] <Wellark> we can and will adress that in the unity8 dialog api
[15:03] <mterry> cool
[15:04] <Wellark> mterry: we anyway need to redesign the notifications and snap decisions, so it's on it's way
[15:04] <Wellark> (on technical level that is)
[15:04] <mterry> yeah
[15:15] <Carom> Hello !
[15:16] <Carom> PLEASE, I just have a one question...    It's possible record calls ??? (both the sides)  Thanks a lot !
[15:16] <popey> not yet
[15:16] <Carom> I can't live without this fuction :(
[15:18] <Carom> For last...  please ->  It's possible use others apps from "google play" ?  If one app from google play works to record calls...    ?   Thanks a lot
[15:19] <Carom> popey: For last...  please ->  It's possible use others apps from "google play" ?  If one app from google play works to record calls...    ?   Thanks a lot
[15:20] <t1mp> popey: can I move the planning sessions for the different apps to any time slot in next week's summit?
[15:20] <popey> t1mp: no because I'm waiting on the individual devs getting back to me with their available slots
[15:21] <popey> Carom: no, Ubuntu is not Android.
[15:21] <Carom> THX
[15:26] <t1mp> popey: okay, np
[15:28] <t1mp> popey: I had some problems with the scheduling system and I moved some sessions around. I'm not sure if I moved the planning sessions that are there already back to where they originally were...
[15:28] <popey> ugh
[15:28] <popey> I'll look
[15:28] <t1mp> popey: they are still in the same day, but may be moved 1h
[15:28] <t1mp> thanks
[15:28] <t1mp> sorry for messing it up
[15:28] <popey> np
[15:32] <Carom> popey: PLEASE...  where can I check  ALL the apps available for ubuntu phone ? ( I just found little apps for now...) THANKS a lot !
[15:33] <dobey> Carom: they're all in the store
[15:33] <Carom> Thx, but I dont have ubuntu phone yet...
[15:33] <dobey> you can use the emulator
[15:34] <Carom> I'm thinking yet...
[15:34] <Carom> I remember... the emulator in the phone ?
[15:35] <dobey> the phone emulator, yes
[15:35] <dobey> or you can run unity8 on your computer or in a vm or whatever
[15:36] <dobey> with the click scope installed (which i think unity8 requires anyway)
[15:36] <Carom> THX
[15:38] <ogra_> dobey, that wont list much ... we are lacking i386 click packages
[15:39] <dobey> ogra_: you can fake the arch though; it will also probably list less on 14.04 than 14.10, due to framework versions
[15:39] <dobey> or you can just run the armhf emulator
[15:39] <ogra_> yep, that too
[15:39] <ogra_> if you have that patience :P
[15:40] <dobey> U1_SEARCH_ARCH=armhf in the scope-regitry's environment should show you all the armhf packages even on x86 though :)
[15:41] <dobey> ogra_: well, i guess the armhf emulator might run faster on an arm system perhaps. or just run ubuntu-desktop-next iso on a chromebook :)
[15:41] <beuno> or
[15:41] <beuno> you can just use the API, right?
[15:41] <beuno> if you're trying to get a list
[15:41] <beuno> you won't be able to easily get the country-specific ones
[15:41] <beuno> but can get the majority of them
[15:41] <beuno> if it's just a list
[15:41] <dobey> well, you can't get a list of everything in a single search, any more
[15:42] <beuno> you have to page through it, sure
[15:42] <dobey> and you have to read the json
[15:42] <beuno> sure
[15:42] <dobey> so sure, if you're a fan of masochism, it's an option too :)
[15:42] <ogra_> definitely trivial for someone who wants to find out if he wants to run ubuntu-touch ... based on the available apps
[15:42] <ogra_> :P
[15:43] <ogra_> beuno, i thought there was a web UI in the works
[15:43] <dobey> well, if you're trying to decide if you want to use the system based on available apps, you're probably doing it wrong :)
[15:44] <ogra_> many people here do though
[15:44] <ogra_> this isnt a rare question
[15:44] <dobey> i didn't say it was. i just said it's probably the wrong path to a good decision.
[15:44] <ogra_> sure, for you and me :)
[15:44] <dobey> facebook for example is a very different app than what you get by installing the facebook app on iphone :)
[15:44] <beuno> ogra_, there is, getting it through juju and deployments
[15:45] <dobey> and delta
[15:46]  * ogra_ meant something like http://apps.ubuntu.com/all
[15:46] <dobey> lots of things that shouldn't even be apps on other phones, and which have crappy mobile web experience
[15:46] <ogra_> or some such :)
[15:47] <beuno> ogra_, yes, there will be something like that soon
[15:47] <ogra_> great
[15:47] <beuno> it's been a bit delayed
[15:47] <beuno> but it'll get here
[15:47] <ogra_> cool
[15:47] <ogra_> thats enough
[16:26] <tiheum> kenvandine: hi, didrocks told me that you could help me concerning two MP for the mobile icon theme. One of them is 'ready to land' since more than one month but has not landed yet...
[16:28] <kenvandine> tiheum, sure, links please?
[16:30] <tiheum> kenvandine: https://code.launchpad.net/~tiheum/ubuntu-themes/suru-icons/+merge/231533
[16:30] <tiheum> kenvandine: https://code.launchpad.net/~tiheum/ubuntu-themes/white-indicators/+merge/240146
[16:33] <kenvandine> tiheum, so you need to land these in vivid right?
[16:35] <tiheum> kenvandine: I would like
[16:36] <tiheum> kenvandine: the first is ready since ages and contains updated app icons and new action mono icons
[16:36] <tiheum> kenvandine: the second one is for the mono (white) indicators
[16:36] <kenvandine> tiheum, can you give me a list of things to test?
[16:37] <kenvandine> including something to test to make sure moving some of those icons outside of the path didn't cause problems?
[16:37] <tiheum> kenvandine: nothing was remove only new/updated stuff so it shouldn't break anything
[16:38] <tiheum> kenvandine: you can check if the app icons (they shouldn't appear pixelated anymore) and the indicators which should be white instead of green/red (except the battery one)
[16:39] <tiheum> kenvandine: and you can have a look at the system settings menu to check if everythin is ok (the second MP inclues a few updates for its icons)
[16:41] <seb128> mterry, is bug #1389771 something you know about?
[16:41] <tiheum> kenvandine: does it make sense?
[16:41] <kenvandine> tiheum, yup!
[16:41] <kenvandine> tiheum, when it's built in the silo, can you test it on a device?
[16:41] <tiheum> kenvandine: sure
[16:42] <tiheum> kenvandine: I can this week but not the next
[16:42] <mterry> seb128, no haven't seen that yet
[16:42] <mterry> seb128, but I don't run through the wizard on many image installs
[16:42] <kenvandine> tiheum, it's building in silo 21
[16:42] <seb128> mterry, yeah, same here
[16:43] <kenvandine> tiheum, should be ready to test soon
[16:43] <mterry> seb128, I have to run for lunch, but will look and test after
[16:43] <kenvandine> tiheum, scratch that... merge failure
[16:44] <kenvandine> tiheum, merge conflict in the white-indicators branch
[16:44] <kenvandine> tiheum, can you fix that?
[16:44] <kenvandine> Conflict adding file suru-icons/status/scalable/alarm-missed.svg.  Moved existing file to suru-icons/status/scalable/alarm-missed.svg.moved.
[16:46] <tiheum> kenvandine: what does that mean? I am not an expert of launchpad :s
[16:47] <tiheum> kenvandine: the icon is included in the two mp (only its colour differs)
[16:47] <kenvandine> tiheum, the bzr branch can't be merged into trunk
[16:47] <kenvandine> just the white-indicators branch
[16:47] <kenvandine> looks like that alarm-missed.svg file changed in trunk since you last merged your branch from trunk
[16:48] <tiheum> kenvandine: I created the white-indicators branch last week from trunk
[16:49] <kenvandine> tiheum, oh... maybe it's really conflicting with your other branch
[16:52] <kenvandine> tiheum, ah... it's because the suru-icons branch moves those icons to a different directory
[16:53] <tiheum> kenvandine: weird, alarm-missed.svg is at the same place in both branches
[16:54] <tiheum> kenvandine: in suru-icons/status/scalable
[16:54] <kenvandine> it's probably just because of the path change
[16:54] <kenvandine> no...
[16:54] <kenvandine> oh... it is
[16:56] <kenvandine> tiheum, but the file itself changed in both branches
[16:56] <kenvandine> they are different
[16:56] <kenvandine> so bzr doesn't know what to do
[16:57] <kenvandine> tiheum, you should probably merge suru-icons into the white-indicators branch then resubmit the white-indicators merge proposal adding a prereq on the suru-icons branch
[17:00] <tiheum> kenvandine: is there a bzr command to merge two branches?
[17:00] <tiheum> or do I have to do everything manually?
[17:00] <kenvandine> tiheum, in your checkout of white-indicators
[17:00] <kenvandine> bzr merge lp:~tiheum/ubuntu-themes/suru-icons
[17:00] <tiheum> kenvandine: great
[17:00] <kenvandine> then fix the conflict, and make sure the right icon is included
[17:01] <kenvandine> and make sure you do a bzr resolve on the file you fixed
[17:01] <kenvandine> commit it and push
[17:01] <kenvandine> then in LP, go to the white-indicators MP and do a resubmit
[17:01] <kenvandine> adding a prereq on the other branch
[17:02] <tiheum> kenvandine: that's clear
[17:02] <tiheum> I'll ping you when it's done
[17:03] <kenvandine> thx
[17:03] <tiheum> thanks for your time and explanations
[17:03] <kenvandine> np
[17:25] <tiheum> kenvandine: hi, everything was fine till the bzr push command. It created a new branch in launchpad: https://code.launchpad.net/~tiheum/+junk/white-indicators
[17:26] <tiheum> and I have an error when I try to set the branch target (ubuntu-themes)
[17:26] <tiheum> do I have to remove the previous white-indicators branch before?
[17:27] <kenvandine> not a +junk branch
[17:27] <kenvandine> tiheum, push it to the previous white-indicators branch
[17:29] <tiheum> kenvandine: ok, sorry
[17:31] <chrisccoulson> Mirv, any idea what's going on in bug 1389721?
[17:31] <tiheum> kenvandine: I re-submitted the merge proposal
[17:34] <kenvandine> tiheum, thanks, building in silo 21 again
[18:09] <r4do> hi guys, i'm trying to install rvm from root user
[18:10] <r4do> it says to me Archives path '/usr/local/rvm/src/rvm/archives' not writable, aborting.
[18:10] <r4do> what's wrong with it?
[18:10] <r4do> there is no file or folder '/usr/local/rvm/src/rvm/archives'
[18:19] <mterry> seb128, haven't been able to reproduce the passcode bug, left a comment
[18:19] <seb128> mterry, thanks
[18:19] <mterry> seb128, did you try to reproduce by any chance?  any luck if so?
[18:23] <seb128> mterry, no I didn't, but I only have a krillin which is on rtm
[18:23] <mterry> seb128, I didn't get the sense that this was mako specific...  I tried on krillin/rtm.  let me try my mako.
[18:25] <seb128> mterry, well, it's more that I'm unsure in the code difference between those rtm images, are they supposed to include the same content?
[18:25] <mterry> seb128, pulling from the rtm channel, yes
[18:25] <mterry> seb128, except they use a different device tarball
[18:25] <mterry> seb128, so different scopes and customization
[18:25] <seb128> maybe Mirv did something weird
[18:26] <seb128> or picked passphrase and misrembered and though he picked passcode?
[18:26] <mterry> Mirv, did you do something weird?  ;)  (trying to reproduce bug 1389771)
[18:31] <dobey> r4do: i think maybe you want to ask that in #ruby or whatever irc channel is appropriate for rvm
[18:31] <dobey> r4do: this channel is about porting ubuntu to touch interface based devices
[18:34] <seb128> mterry, Mirv: I can't confirm either (rtm 143 on krillin)
[18:34] <ogra_> did you perhaps use --password for UDF ?
[18:35] <mterry> ogra_, ooh good point, that would invalidate whatever the wizard tried
[18:35] <ogra_> i think that only calls passwd but doesnt set anything account related
[18:35] <mterry> ogra_, seb128: I should have the wizard show a label that says "you've already got a password set, skipping that bit" instead of fooling the user into entering a passcode anyway
[18:35] <mterry> Just never been a priority
[18:36] <ogra_> well, technically users shouldnt use the --password option for UDF
[18:36] <ogra_> (practically everyone does sinde it is there :P )
[18:36] <ogra_> *since
[18:36] <ogra_> it clearly says it is for CI and automated testing
[18:36] <ogra_> we should remove it from the help
[18:37] <mterry> ogra_, fair but the confusion happens even if just using phablet-config welcome-wizard --enable
[18:39] <ogra_> which s also not an actual enduser tool indeed :)
[19:23] <rickspencer3> does anyone know the passphrase for a newly created emulator?
[19:26] <ogra_> rickspencer3, 0000
[19:27] <rickspencer3> ogra_, well, it asked for a passphrase, not a pin, and then, oddly it just skipped the lockscreen after a while
[19:27] <rickspencer3> I suspect it's due to slowness
[19:28] <rickspencer3> and it is 0000 ;)
[19:28] <ogra_> :)
[19:28] <rickspencer3> ogra_, any idea how to edge swipe on it?
[19:29] <ogra_> use the mouse
[19:29] <ogra_> it is a bit fiddly but works
[19:29] <rickspencer3> hmmmm
[19:29]  * rickspencer3 tries some more fidgeting
[19:29] <rickspencer3> ah, there is exactly one pixel you need to hit :)
[19:29] <ogra_> ;)
[19:30] <rickspencer3> ogra_, is it possible for me to configure it to come up a bit smaller?
[19:30] <ogra_> there is a -scale commandline option
[19:31] <rickspencer3> ogra_, hmmm, can I make that work from QtCreator?
[19:31] <ogra_> hmm, no idea
[19:32] <rickspencer3> ok, thanks anyway
[19:32] <rickspencer3> at least I'm running now :)
[19:32] <ogra_> bzoltan might be able to tell you
[19:32] <rickspencer3> turns out you can't do scopes development directly on trusty
[19:34] <bzoltan> rickspencer3: the Scale selector in the Devices page gives you options between 0.1-1.0 with 0.1 steps
[19:34]  * rickspencer3 looks
[19:35] <rickspencer3> bzoltan, I don't see the Scale selector, where should I look?
[19:35] <bzoltan> rickspencer3:  just about the Memory selector. The default scale is 1 and if you choose 0.7 it will be default next time
[19:35] <rickspencer3> where is the Memory selector?
[19:37] <bzoltan> rickspencer3:  this is how it looks for me http://picpaste.com/Screenshot_from_2014-11-05_21_35_59-F2QQGkoq.png
[19:39] <ogra_> bzoltan, you shoudl re-post ;)
[19:39] <bzoltan>  rickspencer3:  this is how it looks for me http://picpaste.com/Screenshot_from_2014-11-05_21_35_59-F2QQGkoq.png
[19:40] <rickspencer3> bzoltan, I bet the problem is that my emulator is actually running
[19:40] <rickspencer3> found it!
[19:40] <rickspencer3> thanks bzoltan
[19:41] <bzoltan> rickspencer3:  cheers :)
[21:21] <Z3> Hi, can you import google bookmarks to ubuntu touch web browser?
[21:22] <rpadovani> Z3, not at the moment. There is a bug about this, let me find it
[21:22] <rpadovani> Z3, bug 1236926
[21:23] <Z3> rpadovani ok, thank you ! :)
[21:23] <rpadovani> yw :-)
[21:37] <dobey> which thing should i file a bug against, about twitter notifications
[21:37] <dobey> ?
[21:41] <daker> dobey: account-polld
[21:42] <dobey> hmm, i'm not sure this belongs in there, but ok
[21:43] <daker> https://bazaar.launchpad.net/~phablet-team/account-polld/trunk/view/head:/plugins/twitter/twitter.go
[21:43] <dobey> sure
[21:45] <dobey> https://bugs.launchpad.net/ubuntu/+source/account-polld/+bug/1389875
[21:47] <nik90> rsalveti: ping