[06:38] <dholbach> good morning
[07:44] <jaywink> o.O
[07:45] <Mirv> jaywink: O.o
[08:00] <b0bben> hey all
[08:01] <b0bben> i had a device view all of the sudden on my phone while having a call, and now I can't find that view anywhere
[08:01] <b0bben> didn't even know it existed...
[08:01] <b0bben> how do I get to it again?
[08:09] <wowow> welcome
[08:23] <jaywink> hmmmm tried phablet-tools -b to flash all data (maguro) .. it died when trying to transfer autodeploy.zip to device (permission error). Started adb-server as root (first google hint) but now I can only get to recovery mode and phablet-tools does not see the device ... any hints? :)
[08:34] <jaywink> ok I think I managed to fix it, deployed autodeploy.zip to device in recovery mode with adb push manually
[08:37] <Mirv> jaywink: cool if you found a way. one thing is that if you get permission problems and adb devices gives you "??????", there might be an USB id change and you need to update udev rules
[08:37] <Mirv> or at least I encountered a such thing, even though I don't have maguro
[08:38] <Mirv> so in /lib/udev/rules.d/69-libmtp.rules I added a line SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0666"
[08:38] <Mirv> sudo service udev restart and adb devices (etc) worked again
[08:38] <Mirv> but adb root obviously is the first thing to do
[09:11] <om26er> nik90, hey
[09:14] <didrocks> sil2100: the app stack is still failing utah tests, it seems that the dep that oSoMoN added yesterday was not enough, mind checking?
[09:17] <sil2100> didrocks: ACK, ok, in the morning the check job was still waiting for a free slot on the generic job queue, I'll take a look and poke oSoMoN
[09:18] <seb128> sergiusens, hey, I reviewed phablet-tools in NEW, small comment
[09:19] <seb128> "License: GPL-3
[09:19] <seb128>  ...
[09:19] <seb128>  See the applicable version of the GNU Lesser General Public
[09:19] <seb128>   License for more details."
[09:19] <seb128> sergiusens, seems like somebody took the snippet of the LGPL and dropped the L but forgot to drop the Lesser in the text
[09:19] <seb128> sergiusens, that's not a blocker to accept it but would be nice to fix (in debian/copyright and some of the sources)
[09:26] <dpm> hey Saviq, looks like i18n works well for Unity on the phone, which is pretty cool. I can see translated messages for Applications, Music, etc. Do you know where the strings for "Frequent Apps", "Favourite People" and such come from?
[09:28] <oSoMoN> didrocks: the missing dep is still missing, the autolanding job for my MR failed (and is still failing), it looks like the job itself is broken :/
[09:30] <didrocks> oSoMoN: argh, ok :/
[09:30] <didrocks> sil2100: ^
[09:31] <oSoMoN> didrocks: I’m considering merging it manually, given that it’s really trivial, I’m tired of fighting windmills, I’ve wasted so much time this week waiting on jenkins
[09:32] <oSoMoN> om26er: would you object to me merging manually https://code.launchpad.net/~osomon/gallery-app/missing-uoa-dep/+merge/166552, to bypass the busted jenkins job?
[09:34] <didrocks> oSoMoN: that's fine with me FYI ;)
[09:34] <Saviq> dpm, those come from the applications lens
[09:34] <didrocks> oSoMoN: tell us, we'll rebuild the daily apps stack then
[09:35] <didrocks> so that you can be published
[09:35] <oSoMoN> didrocks: ok, waiting for om26er’s green light
[09:35] <didrocks> sure!
[09:35] <Saviq> dpm, AFAIK they need to come translated from there already (i.e. we won't ever know all the category names used by all the scopes)
[09:36] <nik90|Mobile> om26er: hey sry I am at the university, cant talk now
[09:36] <nik90|Mobile> om26er: but leave any messages to nik90, and I will look at it when I get home
[09:38] <dpm> Saviq, yeah, so we just need to internationalize the apps lens, right? Is this the right branch? -> https://launchpad.net/unity-lens-applications/phablet
[09:39] <Saviq> dpm, yes, and it should already be internationalized, no?
[09:40] <Saviq> dpm, btw, the Video and Music lens are static, driven by http://bazaar.launchpad.net/~phablet-team/demo-assets/trunk/files/head:/lenses/
[09:40] <sil2100> oSoMoN: fine with me as well
[09:40] <dpm> Saviq, it looks like the apps lens here is i18n'd on that branch above, but it looks like vala code?
[09:41] <Saviq> dpm, yup, it is
[09:41] <om26er> oSoMoN, yeah, please merge it manually
[09:41] <om26er> (and my internet sucks for the day)
[09:41] <oSoMoN> ok, thanks, merging
[09:41] <sil2100> oSoMoN: could you give me a sign once it's done?
[09:41] <Saviq> dpm, here's unity-lens-mock that's driven by the .json files https://code.launchpad.net/~phablet-team/phablet-extras/unity-lens-mock
[09:41] <dpm> Saviq, ack on Video and Music lens, so I guess we cannot do much until they are not static
[09:42] <Saviq> dpm, yeah, probably not worth the effort
[09:42] <om26er> nik90, the clock app have a problem starting
[09:42] <sil2100> oSoMoN: I'll re-trigger the stack once it's in
[09:42] <om26er> nik90, file:///usr/share/ubuntu-clock-app/ubuntu-clock-app.qml:136 Type TimerPage unavailable
[09:42] <om26er> nik90, tried both trunk and the package from the ppa..
[09:42] <dpm> Saviq, yeah, I agree, not for now
[09:42] <nik90|Mobile> om26er: ok, that's weird. Which version r u running it on?
[09:43] <dpm> Saviq, does it make sense to enable translations in LP for the apps lens (as far as I can see it's just a matter of creating and committing the .pot file) or do you expect big changes there?
[09:43] <oSoMoN> sil2100, didrocks, om26er|lunch: merged and pushed
[09:44] <didrocks> sil2100: relaunching it?
[09:44] <didrocks> oSoMoN: thanks!
[09:44] <Saviq> dpm, the apps lens is just a modified lp:unity-lens-applications - it *should* just use the translations that are already there
[09:44] <Saviq> dpm, and well, it goes away when we switch to saucy (100 scopes), so...
[09:44] <didrocks> (just rebuilding the webbrowser package I guess)
[09:45] <Saviq> dpm, we're not going to touch it at all anymore
[09:45] <sil2100> didrocks: yep!
[09:45] <sil2100> didrocks: should I specify just gallery-app in the run command, or do a whole stack rebuild?
[09:46] <didrocks> sil2100: just what needs to be rebuild please, launchpad will be happy :)
[09:47] <sil2100> didrocks: I'll abort the current apps check job then
[09:47] <dpm> Saviq, yeah, but it only has one translation, Danish, so it's not very useful for non-Danish speakers :) http://bazaar.launchpad.net/~unity-team/unity-lens-applications/phablet/files/head:/po/ so it might be worth opening translations in LP to get some more languages in
[09:48] <didrocks> sil2100: hum
[09:48] <didrocks> sil2100: remember that UTAH doesn't like that?
[09:49] <Saviq> dpm, that's weird - it's the same for http://bazaar.launchpad.net/~unity-team/unity-lens-applications/trunk/files/head:/po/
[09:49] <Saviq> dpm, it's shipped by the lang pack
[09:49] <Saviq> dpm, how does that work?
[09:50] <sil2100> didrocks: I did not remember that, although aborting the upstream check job is a problem for UTAH?
[09:50] <sil2100> didrocks: did it cause some problems in the past?
[09:50] <didrocks> sil2100: if you relaunch one using UTAH, yeah
[09:50] <didrocks> sil2100: UTAH won't deprovision the machine and will continue running the tests
[09:50] <didrocks> so next -check job -> try UTAH -> FAIL
[09:51] <sil2100> Shit
[09:51] <Saviq> dpm, btw, I'm off until Monday, so don't expect me to be responsive
[09:51] <sil2100> didrocks: I think we should have a document with all the common problems and quirks related to daily-release
[09:52] <dpm> Saviq, yeah, for Ubuntu packages it doesn't matter if the .po files are not in the code, as they are fetched from Launchpad directly by the language packs. But as the language packs are not installed on the phone, and they are not shipped in the package itself, then they can't be loaded from either location. So what needs to be done is enable translations in the upstream project so that they are committed to the branch and then shipped in the package
[09:52] <Saviq> dpm, ok, works for me
[09:52] <dpm> Saviq, ack, you've actually been very responsive. Now go and enjoy your time off, thanks!
[09:52] <sil2100> didrocks: so that it's more probable that we're all on the same page and at least have no excuse for repeating a mistake like I just did
[09:53] <sil2100> didrocks: so, basically now the check job will fail if re-run, yes?
[09:54] <didrocks> sil2100: please feel free to document :)
[09:54] <didrocks> sil2100: yeah, it will fail
[09:54] <didrocks> until UTAH finishes
[09:54] <didrocks> so please, check with the QA guys
[09:56] <nik90|Mobile> dpm: can you confirm if the clock app is starting for you? om26er|lunch has a problem starting the app.
[09:56] <sil2100> didrocks: will do, but just so I have a good understanding of it - what happens if the generic testing job finishes before the -check job is re-ran?
[09:56] <sil2100> didrocks: should it be fine then?
[09:56] <dpm> nik90|Mobile, om26er|lunch, it starts from the 144 image. Or do you mean from trunk?
[09:56] <davmor2> ogra_: good news ish  I decided to run a debug build process for crespo.  I did breakfast crespo  brunch crespo then hashed out 1 line at a time till I got it to build.  Looks like I removed the nfc security lines originally.  So now I'm going to see if this build completes then add the Ubuntu specific lines one at a time and see if any of those broke the build :)  But I am making headway it seems woohoo :)
[09:57] <nik90|Mobile> dpm: could you try trunk?
[09:57] <nik90|Mobile> dpm: he couldn't get it to work from trunk and ppa
[09:57] <didrocks> sil2100: is the generic job is still running, that's fine
[09:57] <didrocks> that will protect the lock
[09:58] <sil2100> didrocks: the generic job is still runinng but it should finish pretty soon
[10:00] <dpm> nik90|Mobile, on the mobile r89 works for me (r92 is latest, but after r89 all changes are just translation commits). On the desktop trunk (r92) works for me too
[10:00] <didrocks> sil2100: ok, so once it's finished, it means that UTAH finished
[10:00] <didrocks> which is what we want
[10:07] <user82> check out the cover of this german pc manazine: http://www.pcwelt.de/tipps/LinuxWelt_3_2013_-_jetzt_am_Kiosk-Neues_Sonderheft-7926353.html?view=zoom&zoom=aufmacher
[10:07] <popey> nice
[10:10] <ogra_> heh, i wonder if they actually ship the images on CD
[10:10] <ogra_> err, DVD
[10:10] <ogra_> it kind of indicates they do
[10:11] <sil2100> didrocks: I think the ati run of the generic job is broken, is it possible to abort that while keeping UTAH happy?
[10:12] <user82> will get it later and see what's in there
[10:21] <didrocks> sil2100: not that I know of, did you ask on #qa?
[10:32] <om26er> nik90|Mobile, dpm it starts fine for me. mmrazik is the one seeing the issue
[10:33] <mmrazik> nik90|Mobile: I'm getting this (line 10-14): http://pastebin.ubuntu.com/5719267/
[10:34] <mmrazik> there is a bit of autopilot stuff around but 10-14 is what I get if I try to run the app without autopilot
[10:34] <mmrazik> this seems to be the issue:
[10:34] <mmrazik> file:///usr/share/ubuntu-clock-app/common/AnimationContainer.qml:62 UbuntuNumberAnimation is not a type
[10:37] <timp> mmrazik: which version of the UITK do you have installed?
[10:39] <timp> apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin ubuntu-ui-toolkit-theme
[10:39] <timp> we have r526 now
[10:40] <mmrazik> timp: the one from raring archives
[10:40] <mmrazik> looks the canonistack instance is down. will need to check later what exactly is that
[10:41] <mmrazik> but I did check I have the latest
[10:41] <mmrazik> 0.1.43 for both of them
[10:43] <timp> mmrazik: ok. that's the problem, 0.1.43 is old and doesn't have the UbuntuNumberAnimation, so to run the clock app you'll need the UITK from the ppa
[10:44] <mmrazik> timp: thanks
[10:45] <timp> mmrazik: ppa is listed here http://developer.ubuntu.com/get-started/
[10:52] <davmor2> guys the adb push out/target/product/crespo/*.zip /sdcard/autodeploy.zip line is giving me an error for adb should it be one or the other of the zip file that are in out/target/product/crespo/  I have cm-10.1......crespo.zip and cm_crespo_ota...zip in the directory
[11:02] <ogra_> davmor2, you dont want the ota file
[11:02] <davmor2> ogra_: thanks
[11:24] <nik90|Mobile> mmrazik|afk, om26er: the reason for that error is because his Ubuntu SDK is not updated. Ensure that both the ppa listed in developer.ubuntu.com are included
[11:24] <mmrazik> nik90|Mobile: ack
[11:25] <nik90|Mobile> mmrazik: ack?
[11:26] <mmrazik> nik90|Mobile: acknowledged/all clear :)
[11:26] <mmrazik> thanks
[11:26] <nik90|Mobile> mmrazik: wonderful :)
[11:48] <tara> Hi
[11:49] <tara> I am trying to install ubuntu touch in my nexus 7 tablet
[11:57] <paulliu> renato_: hi. Do you know where is the source code for ChewieUI?
[12:03] <renato_> paulliu, indicators-client
[12:04] <paulliu> renato_: ok.. thanks.
[12:06] <paulliu> renato_: ok. There's a bug cause the datetime mojibake. I guess it is because the fromLation1 function in chewie_datetimeplugin.cpp. I'll see if I can change it to UTF-8 and solves the problem.
[12:25] <paulliu> renato_: https://code.launchpad.net/~paulliu/indicators-client/fix-mojibake/+merge/166772
[12:26] <paulliu> renato_: please help review.
[12:42] <renato_> paulliu, approved
[12:49] <hopkinskong_w8> ~seen dank101
[12:49] <paulliu> renato_: thanks.
[12:51] <evilt0ne> tani: /j #fooo*
[13:29] <davmor2> ogra_: so close yet so far :(  recovery fails to do anything with the image :(
[13:30] <ogra_> you can forcefully install it by selecting it in the recovery menu
[13:32] <davmor2> ogra_: Install /sdcard Finding update package... Opening update package... Verifying update package... Installation aborted.
[13:32] <ogra_> ouch
[13:34] <davmor2> ogra_: I even tried via adb sideload din't like it from there either
[13:34] <seb128> ricmm, rsalveti, ogra_: I'm reviewing android-audiosystem in NEW, the debian/copyright has some small things are inexact
[13:35] <seb128> * it says
[13:35] <seb128> Files: include/machine/*
[13:35] <seb128> License: BSD
[13:35] <seb128> but there a few other files under BSD in there
[13:35] <seb128> include/cutils/atomics.h: BSD (2 clause)
[13:35] <seb128> include/media/stagefright/WAVEWriter.h: BSD (3 clause)
[13:35] <seb128> include/media/stagefright/QCOMXCodec.h: BSD (3 clause)
[13:35] <seb128> for example
[13:36] <seb128> the files in etc/pulse/ come from pulseaudio and are LGPL2+, that should probably be reflected in the copyright as well
[13:38] <seb128> include/unicude is also Copyright "International Business Machines" which is not listed in debian/copyright
[13:38] <seb128> those files have also no license infos
[13:40] <seb128> but the unicode license afaik stipulate that the files can be used/redistributed/modified but that the copyright notice needs to be kept in the copy
[13:40] <seb128> didrocks, ^
[13:41] <seb128> didrocks, since you asked to review, I'm fine with the first issues but the unicode one seems like a potential NEW blocker, the redistribution details and license infos should be included with the copy from what I understand
[13:44] <didrocks> seb128: thanks for the info, rsalveti: ricmm: can you fix this today? so that next daily have it right
[13:45] <om26er> mzanetti, hey! are the autopilot tests working for the qml-phone-shell on devices now ?
[13:45] <mzanetti> om26er: I think so... thomi does not want to fix the display thingie in autopilot tho...
[13:45] <mzanetti> om26er: so I guess we need a workaround for that in the AP tests
[13:48] <om26er> mzanetti, right, do you need help on that ?
[13:48] <om26er> mzanetti, i could try if its not going to be messy
[13:59] <kgunn> om26er: i think a few folks are getting hung up on it....if you could take a run at it
[14:02] <om26er> kgunn, sure, I will look into that. I might need guidance from some
[14:04] <jounih> anyone remember what the clock app bzr url is?
[14:05] <om26er> jounih, lp:ubuntu-clock-app
[14:06] <Oranger> om26er: Thank you for your merge proposal :)
[14:06] <jounih> om26er: thanks
[14:07] <om26er> Oranger, np, if you need any help with autopilot tests there I'll surely help
[14:08] <Oranger> om26er: autopilot tests is something new for me, so I think that I will need your help some times
[14:09] <om26er> Oranger, sure
[14:16] <didrocks> oSoMoN: do you have anything depending on sphinx?
[14:16]  * didrocks sees that sphinx-voxforge-hmm-en sphinx-voxforge-lm-en wants to be installed
[14:16] <didrocks> I guess it's the hud…
[14:17] <oSoMoN> didrocks: sounds like the hud, indeed
[14:17] <didrocks> tedg: any recent transition to libhud2?
[14:17] <tedg> didrocks, ?
[14:18] <didrocks> tedg: I see the hud is depending on          sphinx-voxforge-hmm-en,
[14:18] <didrocks>          sphinx-voxforge-lm-en
[14:18] <didrocks> which are in universe
[14:18] <tedg> Yup
[14:18] <didrocks> we can't have that in ubuntu
[14:18] <didrocks> multiverse*
[14:18] <tedg> Why are they in multiverse?
[14:19] <didrocks> tedg: sorry, my bad, I need to drink coffee
[14:19] <tedg> The source is GPL
[14:19] <sil2100> uh
[14:19] <didrocks> tedg: is that really recent, like today?
[14:19] <didrocks> or a long time ago?
[14:19] <tedg> No, it's been a while.
[14:19] <didrocks> ok, so someone broke the package detection in UTAH
[14:19] <didrocks> a long time ago
[14:20] <didrocks> and now that otto is checking
[14:20] <didrocks> it's working again
[14:20]  * tedg didn't do it, he promises
[14:20] <didrocks> tedg: I believe you on that one :)
[14:20] <didrocks> tedg: thanks!
[14:20] <tedg> NP
[14:20] <sil2100> didrocks: hm, was there some switch from generic autopilot to autopilot-raring-daily_release ?
[14:20] <sil2100> didrocks: for the check jobs?
[14:20] <didrocks> sil2100: right, don't touch the apps stack please
[14:21] <didrocks> we are pluggin in otto in it
[14:21] <sil2100> !
[14:21] <sil2100> \o/
[14:21] <didrocks> sil2100: that's why we see that the package dependencies are not correct :)
[14:21] <didrocks> sil2100: so probably some troubles
[14:21] <didrocks> in the first run
[14:21] <didrocks> to have the list correct
[14:23] <sil2100> ACK
[14:23] <didrocks> sil2100: so, we are adding the hud for now
[14:23] <didrocks> sil2100: as it's transitionning
[14:23] <didrocks> to not fail the job everyday
[14:23] <didrocks> as long as we are in this transition period
[14:24] <sil2100> Since the last correct generic AP job returned just 1 failure, so I've been wondering if maybe we should force publishing?
[14:24] <sil2100> Ok, noted
[14:24] <didrocks> sil2100: no, don't touch it, we need it for now :)
[14:24] <sil2100> didrocks: affirmative ;)
[14:24] <sil2100> But excellent to finally see the new test environment in action
[14:25] <stgraber> ogra_: so how's that container flip going?
[14:26] <didrocks> sil2100: the logs and artefacts looks good for you?
[14:27] <ogra_> stgraber, well, waiting for lxc-android-config to show up in the archive, then seeding and the biggest part should be done ... one bit for later this evening for me is to implement the fstab creation somehow
[14:28] <ogra_> stgraber, and i found a way to repack the zips in a working way for the flipped model, so on monday we should have the standard dual zip setup available for brave people that want to try it
[14:29] <ogra_> stgraber, oh, and the system image ships the initramfs for us in /boot/ on the ubuntu side now
[14:29] <stgraber> ogra_: cool. Once we have that, I'll look into what's needed to convert those into the .tar.xz format I need for the new upgrader
[14:29] <_salem> ricmm, ping
[14:29] <ricmm> pong
[14:29] <ogra_> stgraber, unzip .... tar it ... should be trivial
[14:30] <ogra_> ricmm, did you see seb128's ping above about the audio stuff ?
[14:30] <stgraber> ogra_: unzip => convert all of the weird file metadata to actual file permissions => tar it
[14:30] <stgraber> ogra_: the middle part is the not so trivial one ;)
[14:30] <ogra_> stgraber, the META-INF stuff ?
[14:31] <ogra_> well, it has a binary interpreter that we will need to package anyway
[14:31] <ogra_> the rest is text files
[14:31] <stgraber> ogra_: yep. That part will be different as we use tar and so can and will ship the files with all the attributes
[14:32] <ricmm> ogra_: no
[14:32] <stgraber> ogra_: so with the tar.xz format, our metadata file will be completely different and basically limited to removing files and formatiting partitions
[14:32]  * ricmm scrolls
[14:32] <ogra_> ricmm, seems there are copyright issues
[14:32] <ogra_> stgraber, we need copying and adding files too
[14:33] <ogra_> else things like userdata preservation wont work
[14:34] <ricmm> ogra_: iirc rsalveti did that packaging
[14:34] <ricmm> lets wait for him
[14:34] <ogra_> ah, k
[14:34] <ogra_> stgraber, http://bazaar.launchpad.net/~phablet-team/touch-preview-images/phablet-build-scripts/view/head:/ubuntu_data is what we use today
[14:35] <ogra_> and indeed http://bazaar.launchpad.net/~phablet-team/touch-preview-images/phablet-build-scripts/files/head:/META-INF/com/google/android/
[14:35] <_salem> ricmm, hey, I just flashed build 145, and it seems the screen doesn't turn off during a call. the proximity sensor should be already working, right?
[14:35] <ogra_> for the update-binary we'll have to wait for the toolchain though
[14:35] <_salem> ricmm, is there a way to debug what's going wrong?
[14:37] <stgraber> ogra_: right, I expect that stuff to be quite different for the tar.xz images but I'll wait for the .zip ones to be ready and then will prepare a clear plan on what'll be the difference for the .tar.xz. Then we can discuss whether it's easier to have the livefs buildd spit out both format or simply have a tool converting them.
[14:38] <ricmm> _salem: what device?
[14:38] <ogra_> stgraber, well, i think the binary interpreter is needed for installing
[14:38] <_salem> ricmm, galaxy nexus
[14:38] <ogra_> stgraber, the android recovery mode kind of expects it
[14:39] <ogra_> once the device is installled and our own recovery is in place thats indeed different, but for the initial install you will need what androids recovery wants
[14:39] <ricmm> _salem: its working fine for me on galaxy nexus, have you flashed everything correctly?
[14:40] <stgraber> ogra_: yeah, I'm not against keeping both formats for the time being for those who're not using our recovery image, but for the devices we care about, we'll have our own recovery image that'll understand the .tar.xz format (and possibly only that one)
[14:40] <ricmm> _salem: have you tried many times? or just once
[14:40] <_salem> ricmm, well, I did a phablet-flash, should I wipe the entire phone?
[14:40] <stgraber> ogra_: so we may end up generating a .zip that only contains the recovery image, have that one applied, then push the files and have the new recovery unpack the .tar.xz
[14:40] <_salem> ricmm, I tried 3 times
[14:40] <ogra_> stgraber, i'm not tallking about "those who're not using our recovery image", i'm talking about everyone ...
[14:40] <ogra_> stgraber, the initial install needs something thats compatible with androids recovery mode
[14:41] <ogra_> what comes after the initial installl is all in our hands ... but for replacing whats there we will need to use what android wants
[14:41] <stgraber> ogra_: sure, but for the devices we care about currently, we can just push the new recovery with fastboot, reboot in recovery, adb push the files, reboot and we're done
[14:41] <ogra_> you need to get "our own recovery image" in place first ;)
[14:42] <stgraber> ogra_: but yeah, I expect we'll want to build a .zip that does that for the devices that don't have fastboot
[14:42] <ogra_> fastboot access is a matter of luck
[14:42] <didrocks> sil2100: seb128: http://10.97.0.1:8080/job/cu2d-apps-head-2.2check/44/console \o/
[14:42] <ogra_> we shouldnt rely on it
[14:42] <ricmm> _salem: can you pastebin /system/ubuntu_stamp please
[14:43] <didrocks> otto: 11 min, utah: 30 min for the same tests :)
[14:44] <seb128> didrocks, \o/
[14:44] <didrocks> but with archives!
[14:44] <didrocks> (which takes 1min30) :)
[14:45] <sil2100> Ohshit!
[14:45] <didrocks> sil2100: want to publish the apps stack now? (I forced the manual publishing on purpose before ;))
[14:46] <sil2100> didrocks: sure thing, I'm just browsing through the artifacts looking how things are now ;)
[14:46] <sil2100> Let me fire publish
[14:46] <_salem> ricmm, https://pastebin.canonical.com/91935/
[14:47] <mhall119> are there plans to get camera and audio working on the Nexus 7?
[14:47] <jcastro> is there an individual bug for data via GSM in addition to the wifi?
[14:48] <sil2100> didrocks: publishing forced, but otto testing looks awesome - will we switch all test machines to this platform?
[14:48] <sil2100> (once we test it out more of course)
[14:49] <ricmm> _salem: all that looks right, how are you trying it?
[14:49] <ricmm> when in an active call, put your hand over the prox sensor (top right)
[14:49] <_salem> ricmm, yep, exactly that. the screen keeps on.
[14:49] <didrocks> sil2100: yeah, we are deploying little by little :)
[14:49] <ricmm> ok
[14:50] <didrocks> sil2100: we need to have a saucy install as well
[14:50] <sergiusens> ogra_: stgraber even today, officially for first install we flash our recovery image (it's compatible for other devices), I don't see a need for building the zips
[14:50] <ricmm> _salem: gonna need you to install libplatform-api1-hybris-tests and run test_android_sensors_api or something like that, from that package
[14:50] <ogra_> sergiusens, so you would go with fastboot for everything ?
[14:50] <_salem> ricmm, ok, let me try
[14:51] <ricmm> test_android_sensors_api | grep proximity might be easier to parse
[14:51]  * ogra_ was in the same camp until rsalveti convinced me we should go with adb rather 
[14:51] <sergiusens> ogra_: for the first flash, yes
[14:51] <ogra_> ah
[14:51] <ricmm> but first run it without the catch to see if you are getting any sensor events at all
[14:51] <sil2100> fginther: ping, are you around right now, or in the middle of AFKing?
[14:51] <fginther> sil2100, I'm here
[14:51] <sergiusens> ogra_: then we would need some instructions to allow people to flash/build these recovery images for other devices
[14:52] <ricmm> _salem: I need 5 min, ping me with the result or post it on pastebin
[14:52] <ogra_> sergiusens, yeah
[14:52] <sergiusens> ogra_: and last... we just need to make sure the recovery image is backwards compatible
[14:52] <ogra_> i wouldnt want to flash my SGS2 with heimdall all the time
[14:52] <sergiusens> ogra_: at least for community, for shipping (and nexus line) it wouldn't matter that much
[14:52] <ogra_> since that actually can brick it
[14:52] <ogra_> yeah
[14:52] <sergiusens> ogra_: yeah, exactly...
[14:53] <sergiusens> ogra_: I have to see why my Note is bricked since last week :-P
[14:53] <_salem> ricmm, ok, I see the events there
[14:53] <ogra_> ugh, isnt that yoour main phone ?
[14:53] <_salem> ricmm, void on_new_proximity_event(UASProximityEvent*, void*)
[14:54] <fginther> sil2100, I'll be offline soon though
[14:54] <stgraber> right, that was my thought, use fastboot to push a new recovery image, then push the rest through that. I wouldn't use fastboot to push everything (as we know that tends to fail), but using it for the first flash of the recovery partition should be reasonable.
[14:55] <sil2100> fginther: \o/ hm, do you remember that strange PPA building problem we encountered on the spring last year when packages for some arch's failed building because the -dev package was somehow available earlier and the lib version was not available during build?
[14:55] <stgraber> and for devices that don't support fastboot, they should be able to easily roll a .zip that replaces the recovery partition
[14:55] <sergiusens> ogra_: my main phone now is an Ubuntu Touch install on maguro ;-)
[14:55] <sil2100> (long description)
[14:55] <ogra_> sergiusens, doesnt work, i have that here too
[14:55] <ogra_> :P
[14:56] <fginther> sil2100, It sounds vaguely familiar
[14:56] <sil2100> fginther: let me illustrate it with two pastebined logs
[14:57] <sergiusens> stgraber: ogra_ I would rather not do it in a zip to update recovery... deploying through zips have chances of breaking too
[14:57] <sergiusens> just use the tool for the device explicitly, people should know when they do a dangerous operation
[14:57] <sil2100> fginther: for instance http://paste.ubuntu.com/5720094/ and http://paste.ubuntu.com/5720095/
[14:57] <stgraber> I'm fine with that
[14:58] <sil2100> fginther: getting things like "libunity-dev : Depends: libunity9 (= 7.0.0daily13.05.30ubuntu.unity.next-0ubuntu1)"
[14:58] <ogra_> sergiusens, i'll just go with what stgraber implements, i trust him :)
[14:59] <sil2100> fginther: it started happening again, this time it seems to attack powerpc - do you remember if we had any ideas on the root cause of that? Since I can't remember anything solid
[14:59] <fginther> sil2100, ah, is this because the -dev packages are built by i386 and are therefore availalble sooner
[15:00] <ricmm> _salem: back, can you check your version of powerd?
[15:00] <_salem> ricmm, 0.11
[15:00] <fginther> sil2100, we disabled powerpc builds for unity when pusing to the ppa
[15:01] <ricmm> well all seems to be fine then, something might be wrong with your testing. try doing adb logcat and then ringing your phone from another
[15:01] <sil2100> fginther: I remember we had a conclusion like this, but the problem is... -dev packages have 'any', so they're being built for every arch seperately
[15:01] <sil2100> fginther: so it can't be the case
[15:02] <ricmm> _salem: and pastebin the logcat out
[15:02] <sil2100> fginther: for instance, libunity-dev is built for i386, amd64, armhf and powerpc
[15:02] <didrocks> sil2100: it can be a dependency of this -dev package which is arch:all and not available everywhere
[15:03] <fginther> sil2100, hmmm, sorry, I thought it was just built once...
[15:04] <sil2100> didrocks: would make sense, but strange thing only powerpc would be affected, as theoretically armhf is much slower
[15:05] <fginther> sil2100, a very hackish solution would be to insert additional dependencies prior to uploading the source package
[15:05] <fginther> sil2100, for example replacing "libunity-dev," with "libunity-dev,libunity9,"
[15:06]  * rsalveti reads backlog
[15:07] <_salem> ricmm, http://pastebin.ubuntu.com/5720120/
[15:08] <rsalveti> seb128: didrocks: why did we push audio-audiosubsystem to the archive today?
[15:08] <ogra_> yesterday actually
[15:08] <rsalveti> right
[15:08] <ricmm> _salem: is your powerd even running?
[15:08] <ricmm> _salem: does the auto turn-off of the screen happen? on timeout, 5 seconds
[15:09] <rsalveti> I'd like to get a ping or such, as I was maintaining it and knew it needs a bit more love
[15:09] <didrocks> rsalveti: because it's part of the stack for phablet-tools, that sergio wanted into saucy
[15:09] <didrocks> rsalveti: when I asked about audio-audiosubsystem, he acked that's fine to push to the archive
[15:09] <fginther> sil2100, gotta go, I'll let you know if I think of anything else
[15:09] <_salem> ricmm, powerd is running. the screen is turning off correctly.
[15:10] <rsalveti> didrocks: right, didn't know that
[15:10] <rsalveti> didrocks: so I'll check, might not be able to check today
[15:10] <rsalveti> got some other stuff for today
[15:10] <ricmm> _salem: can you tell me the steps you are using to test this?
[15:10] <seb128> rsalveti, no worry, it's in the queue but it doesn't need to get in today, you can fix those few issues next week
[15:11] <didrocks> rsalveti: ok, thanks, Monday is fine :)
[15:11] <sil2100> didrocks: btw. did you see my ping in the morning about the evdev package in NEW?
[15:11] <rsalveti> seb128: didrocks: cool, ok then
[15:11] <rsalveti> seb128: thanks for the review anyway
[15:11] <seb128> yw
[15:11] <_salem> ricmm, the screen turns off, but it takes 30 seconds, not 5
[15:12] <didrocks> sil2100: hum, I probably misses that
[15:12] <didrocks> missed*
[15:12] <didrocks> sil2100: I pushed it yesterday evening IIRC
[15:12] <sil2100> didrocks: since evdev the old package I see is still in the NEW queue
[15:12] <didrocks> ah, interesting
[15:12] <_salem> ricmm, well, I make a call, when the call is answered I cover the proximity sensor with my hand, and the screen keeps on
[15:12] <sil2100> didrocks: while python-evdev should be if anything (if the packaging looks ok to you)
[15:13] <didrocks> sil2100: it's in already
[15:13] <sil2100> didrocks: by 'in' you mean 'in saucy'? ;p
[15:13] <didrocks> sil2100: evdev rejected
[15:13] <_salem> ricmm, when I do the same using the hybris testing program, I see the event is being emitted correctly though.
[15:13] <didrocks> sil2100: well, you should be able to check: (and you should be suscribed to saucy-changes :p)
[15:13] <ricmm> _salem: I've just run exactly the same test and it works for me, something seems to be wrong with your powerd<->ofono communication
[15:13] <didrocks> sil2100: https://launchpad.net/ubuntu/+source/python-evdev
[15:14] <sil2100> didrocks: I think I need to add myself to that one indeed ;)
[15:14] <sil2100> didrocks: thanks!
[15:14] <didrocks> yw :)
[15:16] <didrocks> rsalveti: seb128: the only downside is that android-* will be pushed 3 times this week-end until the issues are fixed, we'll need to reject it
[15:16] <ricmm> _salem: iow your sensors are working, and they are well wired all the way up and available for powerd. seems to be that powerd isnt even starting it, so it feels like an old powerd version... yet 0.11 is the right one
[15:16] <_salem> ricmm, just rebooted my device and now it works.
[15:16] <ricmm> can you logcat and *restart* the powerd service?
[15:16] <ricmm> ah
[15:16] <ricmm> something was wrong with the powerd startup then
[15:17] <seb128> didrocks, rsalveti: I can NEW it with the understanding that the issues I pointed will be addressed next week
[15:17] <ogra_> ricmm, i wonder if it is the same issue i see on saucy
[15:17] <ogra_> (powerd never starts automatically from the upstart job here)
[15:18] <didrocks> for me it's fine, but better to wait for rsalveti :)
[15:18] <ogra_> there seems to be a race that hits harder on saucy i guess
[15:19] <_salem> ricmm, probably. it was the first run after flashing, not sure if that should matter.
[15:19] <rsalveti> seb128: fine by me
[15:19] <rsalveti> didrocks: why is it going to be uploaded 3 times?
[15:19] <rsalveti> just curious
[15:20] <didrocks> rsalveti: because the NEW queue is not easily accessible to make a diff with
[15:20] <ricmm> _salem: it shouldnt, but maybe something was weird
[15:20] <didrocks> rsalveti: so hard for daily release to detect it
[15:21] <_salem> ricmm, yep, well, thanks for the help, if I manage to reproduce it again I will ping you.
[15:23] <ricmm> _salem: alright, if you do reproduce try to get a logcat of the full boot
[15:24] <rsalveti> didrocks: right
[15:35] <didrocks> seb128: sil2100: stack oif plugged: utah: 18 min, otto: 1.53 min :) (with archive!)
[15:35] <sil2100> Damn...
[15:35] <sil2100> This makes UTAH look really bad
[15:35] <sil2100> ;)
[15:36] <sil2100> But it's anyway silly, it was taking so long to run 1-2 tests, all because of provisioning and such
[15:36] <ogra_> its all desert and casinos, what did you expect ?
[15:37] <seb128> didrocks, \o/
[16:06] <cripted> hi
[16:36] <Dubstar_04> can anyone help with a QML Layout query?
[16:41] <Dubstar_04> nevermind, sorted it!!
[17:02] <beefsugar> Hey, what is the current state of the mako image? does mobile data work now?
[17:05] <rsalveti> beefsugar: https://plus.google.com/100264483712374857174/posts/H4WRch18jEE
[17:07] <beefsugar> ty
[17:08] <beefsugar> excited!
[17:09] <Syraz> So how is the state of it on the N10? been itchin to toss it on for months now..
[17:12] <nik90> dpm: Jouni sent a mail saying that he has pushed the assets to ubuntu-clock-app/design. Do you know which link he is referring to? I checked the code reviews but couldn't find anything
[17:15] <pmcgowan> rsalveti, were instructions published for using the new data stuff?
[17:15] <rsalveti> pmcgowan: not yet
[17:17] <sergiusens> pmcgowan: not yet... MRs still unmerged :-)
[17:17] <Laney> is it known that pressing the button on the N7 doesn't turn the display off?
[17:17] <Laney> just flashed today's image
[17:18] <nik90> mhall119: same question
[17:19] <mhall119> nik90: no iea, and I don't see it on LP either
[17:20] <nik90> mhall119: I will send a reply, however most likely I will get a reply on monday since it is friday evening
[17:21] <nik90> Kaleo_: ping
[17:24] <ufoman> hi
[17:24] <ufoman> is this channel appropiate for asking questions about ubuntu core for nexus 7?
[17:25] <popey> ufoman: try us ☻
[17:26] <ufoman> I have installed ubuntu core on my nexus 7, and accepted the software update
[17:26] <ufoman> it works, but touch does not "click" after performing some actions in the interface
[17:26] <ufoman> it only moves the virtual pointer
[17:26] <tassadar_> there a bug
[17:27] <tassadar_> *there's a bug)
[17:27] <tassadar_> it will stop working after a while..hang on
[17:27] <tassadar_> g { int par(unsigned char b) { b ^= b > 4; b ^= b > 2; b ^= b > 1; b &= 1; return (int) b; } cout << par(5); }
[17:27] <tassadar_> aah
[17:27] <tassadar_> sorry
[17:27] <tassadar_> https://bugs.launchpad.net/ubuntu-nexus7/+bug/1068994
[17:27] <tassadar_> this one
[17:29] <ufoman> oh
[17:29] <ufoman> too bad
[17:29] <ufoman> as it seems to run quite well
[17:29] <tassadar_> yeah, but it is okay if you use mouse
[17:29] <tassadar_> it is a bug in X server, and it's hard to pin down... :/
[17:30] <ufoman> ok
[17:33] <ufoman> yup, mouse works fine
[17:52] <lucasromerodb> ,
[18:00] <niel> is there an ETA on the dedicated phone yet?
[18:06] <dpm> nik90, sorry, I was afk. I was going to ask the same question, but I see you've already replied to the thread. I guess he did a commit instead of a push, and the designs are still on his local drive?
[18:07] <dpm> I couldn't find any code on his LP page, either
[18:10] <mhall119> pmcgowan: does the webbrowser-app not know about the Ubuntu font?
[18:11] <pmcgowan> mhall119, probably not, wonder if we are installing it
[18:14] <pmcgowan> sergiusens, I am getting no permissions on adb suddenly
[18:15] <pmcgowan> nm its ok after a replug, hmmm
[18:16] <pmcgowan> mhall119, actually they are installed so the browser should use them
[18:16] <mhall119> pmcgowan: see https://plus.google.com/109919666334513536939/posts/EDJxstuEzMf
[18:16] <mhall119> it's set to use the Ubuntu font, and it works on chromium on my laptop, but it's not using it on my N7
[18:17] <pmcgowan> mhall119, you made an auth app!?
[18:17] <mhall119> no, aquarius made an auth app
[18:17] <mhall119> I just packaged and themed it
[18:17] <pmcgowan> nice, that was on my list
[18:17] <sergiusens> pmcgowan: adb sometimes messes up
[18:18] <pmcgowan> k
[18:18] <mhall119> pmcgowan: it's all HTML/CSS/Javascript
[18:18] <pmcgowan> mhall119, we need to ask oSoMoN then
[18:18] <mhall119> packaged to install into /usr/share/canonicalauth/ and using chromeless webbrowser-app
[18:19] <pmcgowan> mhall119, I assume ubuntu.com uses that font
[18:20] <nik90> dpm: yeah that could be it..he probably forgot to push it
[18:20] <pmcgowan> mhall119, looks like its using it there
[18:20] <mhall119> pmcgowan: ah, looks like ubuntu.com is loading it from google's font site
[18:20] <mhall119> instead of local
[18:21] <pmcgowan> yep
[18:22] <pmcgowan> mhall119, you sure its finding the style sheet?
[18:23] <mhall119> pmcgowan: that's where it's getting all the colors and borders from
[18:24] <pmcgowan> mhall119, dont know then - make a bug for oSoMoN
[18:27] <mhall119> oSoMoN: https://bugs.launchpad.net/webbrowser-app/+bug/1186372
[18:30] <oSoMoN> mhall119: ack, will look at it on Monday
[18:30] <mhall119> oSoMoN: ah, hang on, it can find "Ubuntu", it's "Ubuntu Light" that it doesn't find
[18:31] <oSoMoN> mhall119: can you please update the bug report with your findings? I really need to EOD here
[18:34] <mhall119> yup
[18:34] <mhall119> just needed to verify
[18:39] <mhall119> setting all the fonts to use "Ubuntu Light", Ubuntu, sans-serif; at least makes it fall back to Ubuntu font
[18:44] <ajalkane> Trying to run autopilot results in:     from autopilot.input import Mouse, Touch, Pointer
[18:44] <ajalkane> ImportError: No module named input
[18:44] <ajalkane> What package should I install?
[18:44] <ajalkane> I've installed what's told here: https://wiki.ubuntu.com/Touch/Testing/Autopilot
[18:44] <ajalkane> But perhaps it's not the full story
[18:55] <mhall119> balloons: ^^
[18:56] <balloons> ajalkane, you just need libautopilot-qt python-autopilot
[18:57] <balloons> ajalkane, we can chat about it as soon as you've finished if your having trouble
[18:58] <ajalkane> balloons: thanks. I did have those installed, but perhaps apt-get update was required - or I made a stupid mistake
[19:05] <lucasromerodb> Hello :-D
[19:07] <mhall119> fginther: ping
[19:07] <fginther> mhall119, pong
[19:07] <mhall119> fginther: hey, we have a new core app we need setup with jenkins
[19:07] <mhall119> https://code.launchpad.net/~music-app-dev/music-app/trunk is the development focus branch
[19:07] <fginther> mhall119, looking
[19:09] <lucasromerodb> I have a design proposal for Shorts, Where do I can upload or send it? is a set of images.
[19:12] <fginther> mhall119, it's setup. I'm also trying to push packages to the daily ppa
[19:13] <mhall119> thanks fginther
[19:17] <popey> mhall119: we should disable autobuild of youtube in the ppa?
[19:29] <mhall119> popey: it's not doing anything anyway, so sure
[19:32] <mhall119> Clock team meeting in #ubuntu-touch-meeting
[19:35] <dumasymptote> hey guys i had a question about building ubuntu-touch from source
[19:36] <dumasymptote> is there a way to build it with a newer version of javac it says the correct version is 1.6 but i have 1.7.0_21 installed
[19:43] <swordfish> popey, Hello again!... First of all thank you for the package and for the inclusion in the collection... I'm trying to merge your branch do I have to do it on my local copy and then commit it to the launchpad or there is a shortcut?
[19:58] <T|ASK> HI, is it right that Canonical plans to publish Ubuntu Phone tonight? Or am I wrong?
[20:06] <T|ASK> With "publish" I mean they plan to publish a first dev release which is installable?
[20:07] <cnf> guess no
[20:07] <cnf> t
[20:07] <T|ASK> I other words are there any official sources to know which devices would probably work with it? I would like to dev an app for it, but I only have a very old HTC Desire
[20:08] <T|ASK> Therefore, it'll be helpful to know which device I should buy to test it
[20:09] <cnf> https://wiki.ubuntu.com/Touch/Devices I guess
[20:15] <T|ASK> cnf: non easy decision. Especially if the nexus phones are not available here
[20:16] <cnf> you could try building it for your device
[20:32] <mhall119> Terminal app team meeting in #ubuntu-touch-meeting
[21:03] <mzanetti> mhall119: http://notyetthere.org/?p=217
[21:04] <mhall119> mzanetti: nice!  Is it on the collection's wiki page?
[21:04] <mhall119> and does it have packaging?
[21:04] <mzanetti> mhall119: currently updating the wiki
[21:04] <mzanetti> mhall119: yes. on my blog you can download a .deb
[21:04] <mzanetti> mhall119: packaging sources are inline in the repo
[21:06] <mzanetti> mhall119: anything else needed to get it into the ppa?
[21:06] <mhall119> nope, as long as I can debuild it, it's good to go
[21:07] <Oranger> mzanetti: I really love your DatePicker and TimePicker :)
[21:07] <mzanetti> :)
[21:08] <Oranger> mzanetti: I think you should see with the Ubuntu SDK team if they planed this component, or if they can use/create something like what you did
[21:08] <mhall119> mzanetti: is that reusable?
[21:09] <mhall119> the date and time picker
[21:09] <mzanetti> mhall119: yes... its 2 components. a Scroller, and the two pickers
[21:09] <mzanetti> mhall119: I think the API is ok now as is. need to document it tho and write tests for it
[21:10] <mhall119> mzanetti: awesome, I'm going to start a new project for collecting these extra widgets
[21:10] <mzanetti> mhall119: also designers are currently discussing it
[21:12] <mhall119> mzanetti: there's a couple of comment lines at the bottom of your debian/copyright that are giving debuild errors, can you delete them?
[21:12] <mzanetti> mhall119: on it
[21:14] <mzanetti> mhall119: pushed
[21:15] <mhall119> wow, weather and calendar app are now on the launcher!
[21:15] <mhall119> popey: ^^
[21:16] <mzanetti> :)
[21:17] <mhall119> now I just need my terminal app in the default buids
[21:18] <mhall119> so I don't have to wait for developer mode to be enabled before I start adding more apps :)
[21:26] <mhall119> Laney: I just flashed my N7, and it seems to not suspend on power press either
[21:46] <Laney> mhall119: thanks for confirming
[21:46] <Laney> I didn't report it btw
[21:54] <wolvelopez_> Hello friends, I am trying to follow the manual to develop the application of "currency converter", but after installing the QtCreator not select a project appears ubuntu, does anyone know why? ... sorry but my English is very bad and use translator
[22:01] <beidl> wolvelopez_: you mean there is no template for an ubuntu app project?
[22:03] <wolvelopez_> beidl: yeah, that's what I mean and I followed all the steps in ubuntu developers
[22:03] <beidl> wolvelopez_: which version of ubuntu are you running on your pc?
[22:15] <beidl> Am I the only one who has a problem with his phones microphone being too quiet when calling? I've heard a few complaints that I sound too quiet whenever I'm running ubuntu touch on my GNex.
[22:20] <wolvelopez_> beidl: 13.04
[22:20] <beidl> wolvelopez_: have you installed the ubuntu-sdk package?
[22:28] <wolvelopez_> beidl: si, he seguido los pasos de http://developer.ubuntu.com/get-started/ y no me ha dado ningun fallo
[22:28] <gregor_> hello, is there any kind of sleep function in qml? setTimeOut isnt working without additions
[22:29] <wolvelopez_> sorry beidl yes, I followed the steps of http://developer.ubuntu.com/get-started/ and has not given me any fault
[22:32] <wolvelopez_> sorry beidl , I am keep trying that here in Spain is late. thank you very much
[22:33] <wolvelopez_> see you
[22:33] <wolvelopez_> bye
[22:43] <popey> mhall119: yay!
[22:57] <aquarius> gregor_, use a Timer
[23:30] <jono> does anyone know if there is a way to send a link to the browser in the SDK?