[00:14] <landstalker> good evening/early morning everyone
[00:16] <landstalker> installing touch onto my 2012 Nexus 7, after the last step installing the very last autodeploy.zip of the ubuntu touch, it reboots, installs, then, I just get a black screen
[00:16] <landstalker> current command running now: adb push trusty-preinstalled-touch-armhf.zip /sdcard/autodeploy.zip && adb reboot recovery
[00:17] <landstalker> this will be my third attempt
[00:22] <landstalker> if this last install doesn't work, its firmly bed time
[00:28] <landstalker> bed time
[00:37] <ajalkane> Trying to install autopilot 1.4 to Ubuntu 13.10 using ppa:autopilot/1.4 but getting this with apt-get upgrade:
[00:37] <ajalkane> The following packages have been kept back: ubuntu-sdk-libs ubuntu-ui-toolkit-autopilot ubuntu-ui-toolkit-doc
[00:37] <ajalkane> Am I missing something?
[00:56] <popey> ajalkane: i just added that ppa and then "apt-get update" and then "apt-get dist-upgrade" and it installed
[00:56] <popey> Setting up python-autopilot (1.4+14.04.20131125bzr410saucy0) ...
[00:56] <popey> no problem
[00:56] <popey> (on 13.10)
[01:05] <thomi> charles: still around?
[01:05] <charles> thomi: yep
[01:05] <charles> thomi: what's up?
[01:06] <thomi> charles: I'm still trying to get upstart working on my laptop. I wonder if you have any ideas from the mail thread?
[01:06] <thomi> charles: maybe other people I can poke to try and get an answer?
[01:09] <ajalkane> I thought dist-uprade would do some naughty stuff... okay I'll run it
[01:09] <popey> dist-upgrade is always the thing to do
[01:10] <ajalkane> Still get ubuntu-ui-toolkit-autopilot being kept back, but I'll try anyway if this works
[01:11] <veebers> ajalkane: So there still is an issue with that ppa and Saucy. The back-porting hit a snag and didn't proceed. We ahve another option available to us which we should hope to implement soon. Sorry about the delay
[01:12] <charles> thomi: let me see if I can reproduce the crash you reported in mail on a non-dev system
[01:13] <ajalkane> veebers: ah ok. Thanks for the info. I'll wait for the fix then.
[01:28] <charles> thomi, I'm seeing this too, even with a deb built from trunk where all the unit tests passed.
[01:29] <thomi> charles: cool, at least it's not just me
[01:29] <charles> thomi, imo you've found a large hole in the test coverage... :-)
[01:29] <thomi> yay!
[02:06] <Beldar> .
[02:33] <cwayne> plars: ah, much better :) http://ci.ubuntu.com/smokeng/trusty/touch_custom/mako/131:20140116.1:20140115.1/6117/
[02:56] <plars> cwayne: way better :)
[05:46] <pitti> ogra_: ah, we read power button from xev? we can surely simulate that, yes (either with AP or with python-evdev, or even with umockdev)
[06:34] <pablo__> help /quit
[08:02] <tsdgeos> Mirv: i commented on https://bugs.launchpad.net/ubuntu/+source/telepathy-qt5/+bug/1267835
[08:06] <Mirv> tsdgeos: ok, great! I'll test if it works with both 5.0 and 5.2 and propose a branch with a new patch to it (since it's not our upstream)
[08:07] <tsdgeos> Mirv: i think it worked fine for me here in 5.0 and 5.2 but yeah a double test is in order, it's too early in the morning so i may have not done the testing correctly :D
[08:09] <Mirv> in times like this it'd be nice if builders were even faster. qtbase needing a rebuild because libxcb-sync transition, a couple of retries, qtdeclarative snapshot waiting its turn after that, and only after that I can turn my attention these other packages, assuming the qtbase rebuild resolves the other problems in PPAs.
[08:09] <Mirv> but if it would be the old PPA builders, the armhf build wouldn't be ready today..
[08:23] <AmriUnix> hello guys I need to know!!!  can I install ubunti touch onzte grand x in??????
[08:32] <pitti> didrocks: yay
[08:33] <didrocks> pitti: hey! ;)
[08:33] <popey> Happy Friday everyone!
[08:35] <didrocks> It *is* and happy Friday! :)
[08:35] <didrocks> popey: thanks for the g+ post btw, it heated my heart ;)
[08:36] <popey> :D
[08:36] <popey> thought you'd like that
[08:37] <didrocks> heh, I still investigated a little bit in the crashers to ensure we were really safe, but all was green!
[08:37] <didrocks> waiting for ogra_ to wake up to promote an image now (slacker! ;))
[08:37] <popey> Maybe he's stuck in traffic on that long and terrible commute to the office!?
[08:38] <popey> I myself had a tricky time this morning climbing over two cats to get to my laptop
[08:38] <pitti> aka. "coffee maker is broken"? :-)
[08:38] <dholbach> good morning
[08:38] <pitti> popey: lol
[08:38] <didrocks> popey: waow, what an adventure! :)
[08:39]  * didrocks waits for a "I twisted my legs when going to work"
[08:39] <popey> It is when one of them hasn't been fed yet. You take your life in your hands in our kitchen in the morning.
[08:39] <popey> Scratched ankles is not an uncommon ailment!
[08:39] <didrocks> ahah :)
[08:43] <Anmol> hello everyone!
[08:43] <Anmol> i need some help
[08:44] <Anmol> i want to start developing apps for ubuntu touch what programming languages i need to know?
[08:48] <Anmol> heyy
[08:48] <Anmol> any one here to help?
[08:48] <Anmol> i have some questions
[08:49] <jgdx> Anmol, hi, many questions can be answered over at http://developer.ubuntu.com/apps/
[08:50] <popey> Anmol: hi
[08:50] <Anmol> i installed ubuntu touch 14.04 on nexus 4  it now shows black screen on boot up  can u tell whatsa the problem?
[08:50] <popey> Anmol: what process did you follow to install it?
[08:51] <tvoss> mzanetti, ping
[08:51] <Anmol> i first flashed android 4.2,2
[08:51] <Anmol> then i went to fastboot
[08:51] <Anmol> and flashed all boot recovery and system
[08:51] <Anmol> then rebooted to recvoery and installed both zips
[08:51] <Anmol> not it boots with black screen
[08:52] <tvoss> mzanetti, do you know about some qml component that gives visualization of visible gps satellites?
[08:52] <popey> can you access the device via adb Anmol ?
[08:52] <Anmol> yes i can
[08:52] <popey> Anmol: and do you get an ubuntu prompt?
[08:52] <Anmol> device is mounted as mtp
[08:53] <Anmol> yes usind adb shell
[08:53] <popey> system-image-cli -i
[08:53] <popey> what version does it report?
[08:53] <Anmol> current build number: 0 device name: mako channel: daily last update: Unknown
[08:53] <popey> that looks odd
[08:53] <Anmol> ? what happened
[08:54] <Anmol> is there some problem with android version?
[08:54] <popey> Anmol: what channel is reported?
[08:54] <Anmol> latest 14.04
[08:55] <popey> http://paste.ubuntu.com/6766765/
[08:55] <popey> thats what my dev phone looks like
[08:55] <popey> (nexus 4)
[08:55] <Anmol> how ca i check that?
[08:55] <popey> thats the output from "adb shell system-image-cli -i"
[08:56] <popey> can you pastebin the entire output from yours?
[08:56] <Anmol> current build number: 0 device name: mako channel: daily last update: Unknown
[08:56] <Anmol> this is the output i get from terminal
[08:57] <Anmol> should i try flashing it over another android version?
[08:57] <popey> hmm
[08:57] <mzanetti> tvoss: no, I don't think Qt supports that atm
[08:57] <popey> I don't flash mine the way you did
[08:57] <Anmol> what version of android you used?
[08:57] <popey> Anmol: my nexus 4 had whatever it came with, 4.2 probably, i flashed months ago
[08:58] <popey> i use "phablet-flash" to flash my device
[08:58] <popey> see https://wiki.ubuntu.com/Touch/Install for details of the recommended way to flash devices
[08:58] <Anmol> i have the manually downloaded the files
[09:00] <popey> which ones?
[09:00] <popey> can you tell me which files you grabbed?
[09:00] <Anmol> manual download the latest daily build 14.04  from here http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/
[09:01] <Anmol> boot ,recovery.system armel armhf for mako
[09:02] <popey> but not the main one, trusty-preinstalled?
[09:02] <popey> that may be why you have a blank screen
[09:02] <Anmol> trusty-preinstalled-touch-armhf.zip
[09:02] <popey> the zip at the bottom
[09:02] <Anmol> i downloaded it
[09:02] <Anmol> i flashed it
[09:02] <Anmol> all five files
[09:04] <Anmol> i am now flashing again with kitkat android 4.4
[09:04] <popey> hmm, i don't know. when ogra awakens (shortly) poke him, he will know.
[09:04] <popey> no, dont do that
[09:04] <Anmol> why?
[09:04] <Anmol> kitkat isnt supported?
[09:04] <popey> not yet
[09:04] <popey> AIUI
[09:05] <Anmol> so i should stick with 4.2.2 ?
[09:05] <popey> hybris needs porting to 4.4
[09:05] <popey> yes
[09:05] <popey> for now
[09:05] <Anmol> okay thanks
[09:05] <popey> i think it's the radio firmware that breaks us in 4.4
[09:05] <Anmol> :(
[09:06] <Anmol> but check dual boot ubuntu and android they have provided with a radio for 4.4
[09:06] <popey> it'll be fixed soon I suspect
[09:06] <Anmol> https://wiki.ubuntu.com/Touch/DualBootInstallation
[09:06] <Anmol> its fixed
[09:06] <popey> right, it's an older one AIUI
[09:06] <popey> so that's good
[09:07] <Anmol> yep
[09:07] <Anmol> when will ogra_ come back?
[09:08] <popey> Anmol: soon
[09:08] <Anmol> okay
[09:08] <popey> oh, ogra_ is here
[09:08] <popey> ☻
[09:08] <Anmol> thanks  :)
[09:09] <ogra_> morning
[09:09] <popey> Good morning.
[09:09] <Anmol> hello morning ogra
[09:09] <Anmol> i need some help
[09:09] <ogra_> Anmol, i'm not sure the manual install process still works since we use signed system images
[09:09] <Anmol> so what should i do?
[09:09] <popey> we should deprecate them if not.
[09:10] <ogra_> popey, right, i need to talk to stgraber about that
[09:10] <Anmol> :(
[09:10] <popey> Anmol: what OS is your host running?
[09:10] <Anmol> ubuntu 13.04
[09:11] <popey> oh, use phablet-flash from the phablet-tools ppa then.
[09:11] <Anmol> i will have to download it again?
[09:11] <popey> it will download it
[09:11] <Anmol> ohh shit :'(
[09:11] <ogra_> right, what popey said
[09:11] <Anmol> cant i use the files i downloaded?
[09:12] <Anmol> manually>
[09:12] <ogra_> no, they are not  the right ones
[09:12] <Anmol> okay
[09:12] <popey> sorry.
[09:12] <ogra_> these are only the input files for the signed images
[09:12] <Anmol> so why dont the ubuntu team remove that wrong article :( ?
[09:13] <Anmol> when manual is not working!!
[09:13] <popey> Anmol: a valid question
[09:13] <ogra_> Anmol, because nobody checked manual installs in a while
[09:13] <Anmol> okay
[09:13] <popey> thanks for your valuable testing though, now we probably can deprecate that set of instructions!
[09:13] <popey> so, there is a positive to this ☻
[09:13] <Anmol> thank you lovely people :)
[09:14] <popey> heh
[09:14] <ogra_> Anmol, if they still work and the wikipage just needs changing we will hear that from the system-image developer, but he lives in a US timezone, it will take some hours for him to wake up
[09:14] <Anmol> okay
[09:15] <Anmol> i want to start writing apps for ubuntu touch what languages i need to know and some source of tutorials?
[09:15] <ogra_> http://developer.ubuntu.com should be a good starting point
[09:15] <popey> qml, qt, c++
[09:16] <ogra_> html5
[09:16] <ogra_> :)
[09:16] <Anmol> thanks and some tutorials?
[09:16] <ogra_> javascript too ...
[09:16] <ogra_> see the url above, there should be tutorials
[09:16] <Anmol> okay please tell me your google account so that i can consult you in future ?
[09:17] <ogra_> there is also an ubuntu app developer community on google plus where people often share howtos and instructions
[09:18] <ogra_> just come here or go to #ubuntu-app-devel, thats better (i might not always be around, others might know certain things better etc)
[09:18] <Anmol> thanks for the help ogra and popey :)
[09:19] <popey> np
[09:19] <Anmol> so what should i use to flash it phablet-flash ? just?
[09:19] <popey> phablet-flash ubuntu-system --bootstrap --channel=devel
[09:20] <Anmol> :)
[09:20] <popey> and yeah, a bunch of devs hang out in #ubuntu-app-devel
[09:20] <popey> and we have a G+ community
[09:20] <Anmol> whats the name of g+ community
[09:21] <popey> https://plus.google.com/u/0/communities/111350780270925540549
[09:21] <Anmol> (y)
[09:21] <Anmol> thanks
[09:22] <popey> np
[09:58] <bitnumus> hi all, just flashing ubuntu touch for the first time onto my nexus 10. I'm currently at  (on device)  'ROM may flash stock recovery on boot, fix?'.  The install guide says to wait at any steps like this, should i continue? its been around 15minutes so far
[10:03] <davmor2> Morning all
[10:06] <bitnumus> davmor2, morning, can you help with my issue above ?
[10:09] <davmor2> bitnumus: pass never seen that screen but I know it takes a good long while to flash
[10:09] <bitnumus> it says 'Ubuntu Update Complete'
[10:10] <bitnumus> on device that is
[10:14] <bitnumus> ERROR:phablet-flash:Installation is taking too long or an error occured along the way.
[10:15] <bitnumus> There is no mention of this in >  https://wiki.ubuntu.com/Touch/Install
[10:15] <bitnumus> so what am i supposed to do ?
[10:18] <ogra_> bitnumus, reboot the N10 and see
[10:18] <bitnumus> i just clicked no
[10:18] <bitnumus> and i'm into ubuntu now
[10:18] <bitnumus> first thing, connecting to WiFi, the keyboard is on its side and i can't use it lol
[10:20] <bitnumus> pretty the shift key closes the keyboard also
[10:20] <bitnumus> i thought it was stable ?
[10:21] <ogra_> well, there are reasons we are about to drop everything but N4 and the 2013 N7 soon
[10:21] <ogra_> file bugs though, so it gets fixed
[10:22] <ogra_> which channel did you flash
[10:23] <ogra_> to get your network set up you can use pahblet-network from a laptop with working WLAN, that will copy over the WLAN settings to the N10
[10:26] <bitnumus> --channel stable
[10:26] <bitnumus> why drop nxus 10, its probably the best device to use this with
[10:26] <bitnumus> i won't use it on anything else, maybe my HTC one but not until its actually stable
[10:26] <ogra_> better use the devel channel, it has far more fixes
[10:27] <ogra_> stable is really more to provide app devs a non moving base
[10:27] <bitnumus> ogra_, ok cool, is there a simply way to upgrade from this channel ?
[10:27] <ogra_> adb shell ...
[10:27] <ogra_> system-image-cli -c devel -b 0 -v
[10:28] <ogra_> note that the download manager gives no feedback, just be patient
[10:29] <bitnumus> Error: https://system-image.ubuntu.com/gpg/image-master.tar.xz:NETWORK ERROR
[10:29] <bitnumus> maybe i'm safest starting frmo scratch
[10:29] <ogra_> err, did you get your wlan set up yet ?
[10:29] <ogra_> thats indeed a requirement to download images :)
[10:30] <bitnumus> ogra_, i've listerally only just touched any of this 30minutes ago
[10:30] <popey> ☻
[10:30] <popey> yeah, connect to wifi and then run that command, should work.
[10:30] <ogra_> right
[10:30] <popey> or re-flash from scratch
[10:30] <bitnumus> ok, is that easier than running   phablet-flash ubuntu-system --channel devel --bootstrap   then ?
[10:30] <popey> not especially
[10:31] <popey> you don't need --bootstrap
[10:31] <ogra_> its the same, just running on the device
[10:31]  * ogra_ upgrades his daily phone to image 132
[10:32] <ogra_> popey, hmm, did you do an OTA upgrade to 132 when testing it ?
[10:33] <popey> yes
[10:33] <ogra_> this boot took endlessly long
[10:33] <popey> and updated my daily phone too
[10:33] <popey> yes, it did
[10:33] <pitti> kalikiana, tvoss: any chance to review https://code.launchpad.net/~pitti/qtubuntu-sensors/integration-tests/+merge/201742 soon?
[10:33] <tvoss> pitti, yup, sorry for the delay
[10:34] <pitti> tvoss: thanks
[10:35] <pitti> (sorry, I didn't mean to sound "why didn't it happen yet"; just a gentle reminder)
[10:42] <bitnumus> black screen this time :O
[10:44] <tvoss> pitti, nothing serious, a question for the qemu-issue mostly
[10:44] <pitti> tvoss: thanks
[10:44] <tvoss> pitti, I think noting down the qemu bug for missing timerfd support would be helpful, too
[10:44] <pitti> tvoss: that's not new from this MP, that's already with the simulation sensor backend in lp:platform-api
[10:45] <pitti> but TBH, we get a lot of failures in emulated qemu
[10:45] <pitti> I hope Erik will fix this, he said he was going to work on it
[10:48] <davmor2> ogra_: can you plug your maguro into your computer and let me know if the mtp works, I'm still getting failures here however the n4 and grouper are working fine
[10:53] <landstalker> morning
[10:54] <landstalker> is there a latest version of Ubuntu-Touch I can try on my Nexus 7 2012? The version I got from the installation instructions just boots to a black screen, I can still get on it via adb shell
[10:57] <ogra_> landstalker, use the devel channel
[10:57] <landstalker> irc or apt?
[10:58] <pitti> tvoss: thanks; will update on Monday, I need to leave early today
[10:59] <pitti> tvoss: i. e. fix the include and point towards the sensor data format documentation
[10:59] <tvoss> pitti, ack and thx, have a nice weekend
[11:00] <bitnumus> ogra_, that devel flash is giving a black screen, any ideas?
[11:03] <ogra_> hmm
[11:04] <bitnumus> i'm back into CWM
[11:04] <ogra_> works here
[11:04] <bitnumus> can i use phablet from here?
[11:04] <ogra_> as long as there is adb root sccess you should be able to, yes
[11:04] <ogra_> *access
[11:05] <bitnumus> might just try it again then
[11:05] <bitnumus> it keeps asking during the process about flashing a new recovery
[11:05] <ogra_> yes, it needs to
[11:05] <bitnumus> 'ROM may flash stock recovery on boot, fix?'.
[11:05] <bitnumus> yes or no to this, i've been pressing no
[11:06] <ogra_> you need the ubuntu recovery so gpg works to read the signature of the images
[11:06] <ogra_> other recovery images do not have gpg on board
[11:06] <bitnumus> so is that a yes or no? lol
[11:06] <bitnumus> the install guide says to press nothing
[11:07] <ogra_> right, it should do that automatically
[11:07] <bitnumus> it doesnt, so what to press here
[11:07] <bitnumus> also, "phablet-flash will not work unless you have booted your device (it must not be displaying the boot loader screen and "adb devices" should list your device). "
[11:07] <bitnumus> so i can't even flash it now ?
[11:07] <ogra_> you should see a robot on violet background with a progressbar underneath during the process
[11:07] <ogra_> if you see that, it uses the ubuntu  recovery
[11:08] <bitnumus> not sure if i'm explaining myself well enough, its giving me a prompt which i pasted above
[11:08] <ogra_> i have no idea where that prompt could come from
[11:08] <ogra_> unless you use --bootstrap or some such
[11:09] <bitnumus> well i can't do anything now, so should i reinstall android and then use phablet again ?
[11:09] <ogra_> no
[11:09] <ogra_> if you have the ubuuntu recovery you can just flash again
[11:09] <bitnumus> no i'm in default recovery
[11:10] <bitnumus> android laying on his back
[11:10] <ogra_> thats not recovery
[11:10] <ogra_> thats fastboot flash mode
[11:10] <bitnumus> right
[11:10] <bitnumus> its CWM
[11:10] <ogra_> no
[11:10] <ogra_> thats in the rom of the hone
[11:10] <ogra_> *phone
[11:11] <ogra_> (with a giant "Start" on the screen by default)
[11:11] <bitnumus> its CWM 6.0.2.8
[11:11] <bitnumus> has ubuntu logo!
[11:11] <ogra_> ah, sounds good then
[11:12] <ogra_> (but there shoulld be no lying android)
[11:12] <bitnumus> yea there isn't now i was on the home bit
[11:12] <bitnumus> ok i can get it via adb
[11:12] <bitnumus> in*
[11:13] <ogra_> so all is good ...
[11:14] <landstalker> bitnumus: you installing on a Nexus 7? I'm getting a black screen when I try to boot into Ubuntu Touch
[11:14] <bitnumus> landstalker, nexus 10 for me
[11:14] <bitnumus> ogra_, in what respect? lol
[11:14] <bitnumus> do i need to try and install it manually from here then
[11:14] <ogra_> bitnumus, you got the right recovery in place already
[11:14] <ogra_> no
[11:14] <bitnumus> phablet wont let me do anything
[11:14] <ogra_> it should just bot
[11:14] <bitnumus> INFO:phablet-flash:Device detected as /sbin/sh: getprop: not found
[11:14] <ogra_> (note that the first boot takes quite long)
[11:15] <bitnumus> no, it keeps cycling google,  google,   google
[11:15] <ogra_> ~2min or a little more
[11:15] <bitnumus> i need to flash it again, how can i do that from recovery
[11:15] <ogra_> use "-d manta" with phablet-flash
[11:16] <landstalker> bitnumus: you sound like you're having the same issue as me. I have boot, recovery and system installed via fastboot flash and the last two steps involve installing the zip's. I do that, then it's supposed to boot into Ubuntu Touch, but doesn't.
[11:16] <ogra_> landstalker, you need to use phablet-flash ... i dont think the manual process works anymore
[11:16] <bitnumus> ERROR:phablet-flash:Backup requested but cannot be completed succesfully, try with --system-image-ready if the system is already on an Image Based Ubuntu System to force it or use --bootstrap if data saving is not important or the system is not already on an Image Based Ubuntu System
[11:16] <bitnumus> i'll try with that switch then ogra_ ?
[11:16] <bitnumus> --system-image-ready
[11:16] <landstalker> ogra_: don't think that's available in Fedora :)
[11:16] <ogra_> bitnumus, no, --bootstrap instead
[11:17] <landstalker> oh, maybe it is
[11:23] <bitnumus> ogra_, same prompt
[11:24] <bitnumus> ROM may flash stock recovery on boot, Fix?   >  Yes, no, go back
[11:26] <landstalker> this phablet-flash is downloading: quantal named images, I installed trusty. Which is right?
[11:27] <ogra_> landstalker, you want trusty
[11:28] <ogra_> bitnumus, wait for sergiuens to come around, he maintains phablet-flash ... i have never seen that prompt
[11:28] <popey> are you using phablet-flash from the ppa?
[11:28] <popey> apt-cache policy phablet-tools
[11:28] <bitnumus> yes
[11:29] <bitnumus> that prompt aside, its booted but screen is blank again
[11:29] <bitnumus> installation according to phablet successfully finished
[11:29] <bitnumus> ah, we're there!
[11:29] <landstalker> no, phablet-tools from here popey: http://rpm.pbone.net/index.php3/stat/4/idpl/23727034/dir/fedora_19/com/phablet-tools-0.1-6.1.noarch.rpm.html
[11:30] <bitnumus> ey keyboard is fixed
[11:30] <bitnumus> whats ogra_ , popey
[11:30] <bitnumus> thanks**
[11:30] <ogra_> :)
[11:31] <ogra_> but dont expect to much, the N10 has quality problems ...
[11:31] <ogra_> (like the old N7 does)
[11:31] <landstalker> I'll wait for this to finish, see if it bricks my N7, then if not, I'll change the URL to trusty and let it try again.
[11:33] <asac> bzoltan1: is the framework version used anywhere right now in click meta data etc.?
[11:33] <ogra_> saucy is definitely far behind trusty ... it was a snaphot to give app devs a non moving target, it lacks a lot of features that were added throughout the trusty cycle
[11:33] <ogra_> asac, iirc in click
[11:33] <asac> bzoltan1: so if we would move to 14.04 framework, will the click apps just be disabled and not be available for download from store ?
[11:33] <asac> e.g. if i install an image that doesnt have 13.10 framework anymore, does all that stuff work?
[11:34]  * ogra_ guesses thats rather a question for the click lens developers than for the sdk team 
[11:34] <asac> beuno: ^^ maybe also you for the store side
[11:34] <asac> beuno: do you guys already honor framework versionm somehow when serving what click apps are installable?
[11:34] <bzoltan1> asac: the dfault framework in the  templates  is ubuntu-sdk-13.10
[11:35] <bzoltan1> asac: I do not know how the framework field of the manifest file is handled on the platform side.
[11:36] <bzoltan1> asac: as far as I know you can still force to install click packages and ignore the frameworks
[11:37] <asac> right
[11:37] <asac> so i think we need to find out:
[11:37] <asac>  1. does our image disable apps that have no compatible framework anymore
[11:37] <asac>  2. does the store already honour this and connected to that: does the click scope etc. actually send that info to store
[11:37] <asac> bzoltan1: force install?
[11:38] <asac> bzoltan1: do we have special "force" UI?
[11:38] <ogra_> asac, from cmdline
[11:38] <asac> or is that through cmdline?
[11:38] <asac> ah... sure
[11:38] <asac> well that makes sense
[11:38]  * beuno reads
[11:38] <asac> but in the click scope etc. we should disable/grey out the apps that dont work anymore, no?
[11:38] <beuno> asac, bzoltan1, yes
[11:38] <beuno> the client tells the server what framework(s) it has
[11:38] <ogra_> not grey out ... hide them
[11:38] <beuno> and the server filters results based o that
[11:38] <asac> beuno: so click scope sends you a list of frameworks supported by device?
[11:38] <beuno> asac, it does
[11:39] <asac> beuno: a list? :)
[11:39] <asac> or just one?
[11:39] <asac> sorry, need to double check so i dont makea  check mark on something
[11:39] <beuno> asac, just one atm, still need to change it to support multiple ones
[11:39] <beuno> which is what I have on my plate right now
[11:39] <beuno> the transition between framework story
[11:56] <Anmol> hi everyone :)
[11:56] <Anmol> can i backup my ubuntu touch from recovery?
[12:07] <Anmol> #ubuntu-app-devel
[12:36] <Mirv> tsdgeos: the new qtdeclarative snapshot + cherry picks is now in beta2 PPA, but I'm not yet noticing new successful builds with help from that after relaunching a bunch of them
[12:36] <tsdgeos> no?
[12:37] <tsdgeos> at least they should fail "later"?
[12:37] <Mirv> tsdgeos: the problem of course is that there are so many packages that I fail to remember which failed so that maybe could succeed now
[12:37] <tsdgeos> Mirv: the toolkit still fails i gather?
[12:37] <Mirv> tsdgeos: yes, looks similar to before
[12:37] <tsdgeos> damn
[12:37] <tsdgeos> do you have the url?
[12:39] <Mirv> tsdgeos: https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-daily/+sourcepub/3829605/+listing-archive-extra only amd64 so far, looks familiar. but I wonder if it's because of qtpim would be broken and I've one branch from Chris to fix its own tests now which I'm planning to test next.
[12:40] <tsdgeos> let me see if i can repro that here
[12:40] <Mirv> not that datepicker for example would directly use it, but still ui-toolkit uses qtpim in some places
[12:40] <Mirv> I also uploaded test build of telepathy-qt5 now so I can push the branch for proposing (and have the branch build meanwhile unblocking more packages)
[12:41] <tsdgeos> Mirv: are you building ubuntu-ui-toolkit package or ubuntu-ui-toolkit  from bzr?
[12:41] <landstalker> hmm, I don't think Ubuntu Touch works on Nexus 7 wifi (2012) if you're trying manual. I did try phablet-flash but as I don't run Ubuntu on my desktop, this didnt' work
[12:43] <Mirv> tsdgeos: bzr trunk always
[12:43] <tsdgeos> ok
[12:43] <Mirv> so those builds come from Launchpad recipe like https://code.launchpad.net/~canonical-qt5-edgers/+recipe/daily-qt52-ubuntu-ui-toolkit
[12:44] <Mirv> it's possible that now the problems me and zsombi got are gone, but they were not the same as what happens on the PPA builders in the first place
[12:56] <landstalker> out of interest, for anyone that has done this, once you flash the trusty-preinstalled-touch-armhf.zip image file (you've rebooted and the android has installed it, without error) on the next reboot when it should go into Ubuntu Touch, how long does it take on your screens to show this?
[13:00] <tsdgeos> Mirv: zsombi: it's now failing in tst_Layouts::testCase_OverlaidInItemLayout for me
[13:00] <tsdgeos> i can't repro the crash in the ppa builders
[13:00] <tsdgeos> lunch!
[13:11] <landstalker> any suggestions on what useful information I can glean from a freshly installed Ubuntu Touch Trusty on a 2012 Nexus 7 which doen't display anything on screen but that I can get a root shell via adb shell?
[13:17] <ogra_> sergiusens, rsalveti, http://people.canonical.com/~ogra/ubuntu-touch/edge-skin.tgz could one of you pull that into the tree (and tell the emulator to use that skin)
[13:17] <ogra_> should go under the skins dir
[13:17] <daker> pixel perfect edge skin or not
[13:17] <ogra_> daker, well, working edge skin :)
[13:18] <daker> :)
[13:18] <ogra_> it doesnt use 720p currently
[13:18] <sergiusens> ogra_, yup
[13:18] <ogra_> need to experiment with the pixel density settings for that, but i'll keep it updated on changes
[13:24] <mandel> barry, I'm fixing the logging from udm, I have plans to move the logs from /var/log/syslog to /var/log/ubuntu-download-manager.log with rolling logs, what do you think about it?
[13:24] <sergiusens> no rolling logs on the phone :-)
[13:25] <mandel> sergiusens, wait, what?
[13:25] <mandel> sergiusens, so I just step on them?
[13:25] <sergiusens> mandel, I think so; ogra_ ?
[13:26] <mandel> ew.. I'm ok with removing the old ones etc.. but for debugging will be a small pita
[13:26] <ogra_> we use logrotate atm
[13:26] <sergiusens> ogra_, I would argue that we are storing to many logs
[13:26] <ogra_> you would need to provide a "throw them away" config for it
[13:26] <sergiusens> mandel, yeah, de`bug is fine; production ain't
[13:26] <ogra_> de'bug :) the dutch developer
[13:27] <ogra_> sergiusens, we might, i think we shrunk the amount a lot already
[13:27] <mandel> ogra_, ok, cause I just made the change to glog from qdbug (it sucks) and I'm rotating logs, can you point me to some docs about the throw them away config??
[13:28] <ogra_> man logrotate ? or man logrotate.conf
[13:29] <mandel> ogra_, thx, I'll take a look
[13:29]  * mandel lunch 
[13:29] <ogra_> there is a lot of stuff in /etc/logrotate.d/
[13:31] <Mirv> arrr multitasking
[13:32] <sergiusens> ogra_, that was my dying keyboard :-)
[13:32] <Mirv> tsdgeos: so just forget I mentioned qtpim, I managed to make sure Chris' patch works to fix test building and all tests pass, so it's not related at least in any way. it's all about how ui-toolkit triggers something in QML/V4/xvfb/etc..
[13:32] <ogra_> :)
[13:32] <tsdgeos> Mirv: yeah :/
[13:32] <tsdgeos> Mirv: the thing is, i'm running a chroot with xvfb too
[13:33] <tsdgeos> so i'm confused of why it fails on the ppa and not here :S
[13:33]  * ogra_ notes that argentinian keyboards start speaking dutch when they die 
[13:33] <sergiusens> ogra_, it's a US keyboard; aregntinian ones are useless, the main key I use '/' needs a modifier ;-)
[13:33] <sergiusens> and is out of reach...
[13:33] <ogra_> same as german where / is shift+7
[13:39] <Mirv> tsdgeos: telepathy-qt5 looks good so far, I'm updating the symbols still
[13:39] <tsdgeos> Mirv: cool
[13:41] <landstalker> could be this bug:       https://bugs.launchpad.net/ubuntu-tf101/+bug/1153306
[13:43] <ogra_> landstalker, unllikely, that bug is so old that it wont apply to any of the recent images
[13:43] <ogra_> the whole image design changed several times since
[13:44] <ogra_> the current trusty image definitely works here on a grouper (N7)
[13:45] <ogra_> (with the known graphics driver issues though)
[13:46] <popey> we should "wontfix" all the old TF101 bugs
[13:46] <popey> or at least review them
[13:52] <tsdgeos> +1
[13:53] <cwayne> what's our plan re: maguro and grouper and manta bugs?
[13:53] <landstalker> ogra_: any preferred place for me to dump a logcat?
[13:53] <ogra_> cwayne, integrate the fixs for them the community sends us :P
[13:54] <ogra_> *fixes
[13:54] <cwayne> good answer :D
[13:54] <landstalker> ogra_: I wonder if the 8GB Nexus 7 is different in anyway to the 16GB or 32GB varients
[13:54] <ogra_> landstalker, i'm running trusty image 132 just fine on my 8G N7 here
[13:55] <ogra_> hmm,, or ... well ... i did last night ... now the battery is dead once again
[13:56] <landstalker> ogra_: is that the one listed here? http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/
[13:56]  * cwayne ran 131 on grouper yesterday succesfully fwiw
[13:56] <Mirv> yay, qtubuntu-camera fixed and built! thanks tsdgeos + jhodapp for looking at qtvideo-node next
[13:57] <ogra_> landstalker, it is the latest image from the trusty channel you get with phablet-flash ... the files on cdimage are only the input files for the system ikmages phablet-flash uses
[13:57] <jhodapp> Mirv, np, btw do you need this done quickly, or in the next few weeks?
[13:57] <ogra_> but yeah, /current has the files that are used for building 132
[13:57] <landstalker> ok, I'm not running Ubuntu on my desktop and the only available phablet-flash that is in an rpm is quite old
[13:58] <landstalker> phablet-tools-0.1-6.1
[13:58] <ogra_> well, phablet-flash is just python
[13:58] <landstalker> ok, I could unpack the .deb I guess if its just a python script
[13:58] <ogra_> you should be able to pull the bzr tree and run it from there if your fedora install has the necessary bits and pieces installed
[13:58] <sergiusens> landstalker, use the go one
[13:59] <ogra_> oh, right, there is a go one now
[13:59] <landstalker> whats go?
[13:59] <ogra_> a language
[13:59] <ogra_> :)
[14:00] <sergiusens> landstalker, http://discourse.ubuntu.com/t/phablet-flash-in-golang/1297/2?u=sergiusens
[14:00] <sergiusens> I bet it would work if I just give you the binary
[14:00] <landstalker> right, how is that better then a python version?
[14:00] <landstalker> I was about to look at getting the files from here: http://bazaar.launchpad.net/~phablet-team/phablet-tools/trunk/files
[14:00] <sergiusens> it should work everywhere without to many hassles
[14:01] <ogra_> right, go usually builds static binaries, you should just be able to execute it
[14:01] <sergiusens> just grab the deb and extract it and use it from anywhere
[14:02] <landstalker> for those who might be interested, this is my logcat: http://pastebin.com/1vF0LN5n
[14:03] <Mirv> jhodapp: preferably ~quickly, since we'd like to have images with Qt 5.2 enabled (= everything rebuilt) soon, but that said there are some more highly visible packages having problems at this very moment
[14:03] <Mirv> so not a few weeks, but not "TODAAAYY!" either :)
[14:04] <jhodapp> Mirv, that's what I suspected, I'll see if I can change qtvideo-node without much issue
[14:04] <popey> sergiusens: approved calendar
[14:05] <landstalker> ok, I'm with you, go probably a better/easier way
[14:05] <ok> hallo
[14:05] <Guest91595> ok
[14:06] <Guest91595> ubuntu touc for galaxy s4
[14:16] <barry> mandel, sergiusens shouldn't the system itself prune logs when/if appropriate?  it shouldn't be up to each application to manage its logs - the behavior would be too inconsistent
[14:19] <ogra_> sergiusens, so looking at the emulator documentation, we should either use -scale or -dpi-device to force the pixel compression ... both are ignored for me (though my emulator install isnt up to date, but i dont think we changed anything that would them be not ignored)
[14:19] <ogra_> *would make them
[14:22] <landstalker> sergiusens: I'm kind of presuming you wrote udbflash? I'm running udbflash ubuntu-system --channel devel-proposed-customized --bootstrap
[14:23] <sergiusens> barry, yeah, I agree with that
[14:23] <barry> i just want logs that are useful :)
[14:23] <sergiusens> ogra_, let me check
[14:24] <sergiusens> landstalker, read the comment bellow
[14:24] <ogra_> barry, thats why i said we should have a throw away rule for logrotate
[14:26] <landstalker> sergiusens: ahhh crap, didn't notice the name change. It seems to be doing it's stuff anyway. Currently it's rebooted into recovery
[14:26] <ogra_> landstalker, not sure youwant -customized :)
[14:27]  * ogra_ would have gone with "devel" only for a start ... 
[14:27] <ogra_> that contains the tested images
[14:28] <landstalker> it's ok, it didn't work anyway. I've no idea what each image breaks down to. I'll shoot for devel as it rebooted into recovery, I assume to install via autodeploy, but nothing happened. So going to run it again.
[14:28] <ogra_> sergiusens, oh, i take that back ... with -scale 320dpi i now get an emulator window about twice as big as my fullHD screen here :P
[14:29] <landstalker> now going with: ./ubuntu-device-flash ubuntu-system --channel devel --bootstrap --wipe
[14:30] <landstalker> hmm, devel is installing stable version 101
[14:30] <landstalker> [lee@fedora17 bin]$ ./ubuntu-device-flash ubuntu-system --channel devel --bootstrap --wipe
[14:30] <landstalker> 2014/01/17 14:29:02 Device is |grouper|
[14:30] <landstalker> 2014/01/17 14:29:03 Flashing version 101 from stable channel and server https://system-image.ubuntu.com to device grouper
[14:30] <landstalker> 2014/01/17 14:29:03 saucy is a channel alias to stable
[14:30] <ogra_> then try trusty ...
[14:30] <ogra_> instead of devel
[14:31] <ogra_> sergiusens, ^^^that looks kind of wrong
[14:31] <landstalker> I'll try that once it's finished, I'm not sure what stage it's upto so don't want to potentially brick it
[14:31] <ogra_> LOL
[14:31] <ogra_> ok, -scale 0.1 gets me a 64px wide emulator window
[14:31] <ogra_> looks cute though
[14:32]  * ogra_ wonders if he can interact with that small screen 
[14:32] <landstalker> is it a "term" of endearment?
[14:32]  * landstalker gets his coat
[14:32] <ogra_> haha, i can !
[14:32] <ogra_> cute
[14:32] <ogra_> barbie phone on my desktop
[14:34] <popey> mzanetti: https://twitter.com/bbcclick - most recent tweet ☻
[14:35] <mzanetti> popey: who's bbcclick?
[14:36] <popey> BBC - The TV company, Click is their tech show
[14:36] <mzanetti> ah, cool :)
[14:36] <popey> http://www.bbc.co.uk/programmes/b006m9ry
[14:37] <sergiusens> landstalker, ogra_ the 'ubuntu-system' shouldn't be there!
[14:37] <davmor2> mzanetti: is it nearly landed yet? will be the chant at you till it lands now you know that right ;)
[14:37] <sergiusens> landstalker, you don't need to wipe if you are bootstrapping
[14:37] <mzanetti> davmor2: I'm afraid so :D
[14:38] <sergiusens> popey, slick
[14:38] <ogra_> http://people.canonical.com/~ogra/ubuntu-touch/emulator/tiny-emulator.png
[14:38] <ogra_> aint it sweet ?
[14:39] <popey> awwww
[14:39] <popey> like it's been put in the oven and shrunk
[14:39] <ogra_> and you can interact with it
[14:39] <popey> like a shrinky-dinky
[14:39] <ogra_> yeah, kept it in the pocket when doing laundry
[14:39] <popey> hehe
[14:39] <landstalker> ahh ok sergiusens I was just applying the phablet command and making assumptions
[14:39] <mzanetti> this is how it always looks like on my retina screen ^^
[14:39] <ogra_> just had to dry it ... still working :)
[14:39] <mzanetti> can I make it bigger now?
[14:40] <landstalker> third time a charm, does this seem reasonable? ubuntu-device-flash --channel devel --bootstrap
[14:40] <davmor2> ogra_: NO we are meant to keep the announcement a ubuntu touch for rings a secret.  D'oh
[14:40] <ogra_> mzanetti, you should be able to hack the start script and use the -scale parameter for the emulator command
[14:40] <mzanetti> nice... so I might be able to use it finally :)
[14:40] <mzanetti> thanks ogra_
[14:40] <ogra_> davmor2, i totally didnt mention what project it is for, *you* just reveled it
[14:40] <ogra_> *revealed
[14:41] <ogra_> mzanetti, though it might be that it doesnt accept values above 1.0
[14:41] <mzanetti> waaahhh :D
[14:41] <ogra_> (the shot is with 0.1)
[14:41] <davmor2> ogra_: touche
[14:41] <ogra_> :)
[14:45] <sergiusens> ogra_, if you rebuild android; the skin will come (needs new tar)
[14:45] <ogra_> yay, thanks
[14:45] <ogra_> just have to make a proper icon now
[14:45] <sergiusens> ogra_, don't have access/knowledge on where the tar was built
[14:45] <sergiusens> cwayne, care to do a small review for me?
[14:45] <ogra_> yeah, lets leave that to xnox or rsalveti
[14:45] <sergiusens> ogra_, I think stgraber can as well
[14:46] <ogra_> i think the package has a get-upstream-source in debian/rules or so
[14:46] <sergiusens> ogra_, you can always distro patch ;-)
[14:46] <ogra_> but before i break it i'll rather wait :)
[14:46] <sergiusens> ogra_, I can add the skin to ubuntu-emulator itself as well
[14:47] <ogra_> yeah, that would be good
[14:47] <sergiusens> I was thinking it might even be a better idea
[14:47] <ogra_> yup
[14:47] <sergiusens> ogra_, let me just do that
[14:47] <ogra_> definitely better during development so we dont need to rebuild the world for it
[14:48] <ogra_> especially as long as we dont have the right scale value and resolution i will likely have to adjust the png a few times til it is right
[14:48] <cwayne> sergiusens: sure thing
[14:50] <sergiusens> cwayne, here it is: https://code.launchpad.net/~sergiusens/goget-ubuntu-touch/list_cmd/+merge/201871
[14:51] <jdstrand> cyphermox: hi! I'm a dogfooder and I'm seeing some odd dns issues on my phone
[14:52] <cyphermox> ah?
[14:52] <jdstrand> cyphermox: so, I'm on wireless right not (ie, not 3g) and have a local 192.168 address on wlan0
[14:52] <jdstrand> (fine)
[14:52] <landstalker> sergiusens: ./ubuntu-device-flash --channel devel --bootstrap just seems to hang
[14:52] <jdstrand> cyphermox: and I see that dnsmasq is using the correct resolvers (also fine)
[14:54] <jdstrand> cyphermox: however, it seems when I plug my phone into my laptop via usb, rmnet_usb0 get setup like so: http://paste.ubuntu.com/6768316/
[14:54] <jdstrand> cyphermox: and then my phone starts making dns queries to 10.177.0.34:53
[14:54] <landstalker> ok, think I got it. I rebooted using adb into bootloader
[14:54] <cyphermox> weird. why is 3G getting brought up when you plug USB/
[14:55] <jdstrand> yes :)
[14:55] <jdstrand> which is why I'm talking to you :)
[14:55] <cyphermox> could you send me more logs?
[14:55] <jdstrand> cyphermox: sure, what do you want?
[14:56] <cyphermox> jdstrand: just syslog, but there should be more relevant data before the "Auto-activating"
[14:56] <jdstrand> yeah
[14:56] <ogra_> mzanetti, aha
[14:57] <cyphermox> I wonder if you have an extra gadget enabled for some reason, and that pokes NM into believing rmnet_usb0 is to be activated
[14:57] <ogra_> mzanetti, "<scale> is a number between 0.1 and 3 that represents the desired scaling factor. "
[14:57] <jdstrand> cyphermox: fyi: http://paste.ubuntu.com/6768325/
[14:57] <mzanetti> ogra_: nice. 2 should work for me
[14:57] <ogra_> mzanetti, so upwards should work fine
[14:57] <jdstrand> cyphermox: extra gadget?
[14:57] <cyphermox> jdstrand: rmnet_usb0 is the device for 3G
[14:57] <landstalker> nope, didn't work
[14:57] <cyphermox> yeah
[14:57] <landstalker> 2014/01/17 14:57:13 Cannot push /home/lee/.cache/ubuntuimages/devel/grouper/version-132.tar.xz to device
[14:57] <cyphermox> jdstrand: like enabled rndis in sys.usb.config
[14:58] <jdstrand> cyphermox: radvd is on this network
[14:59] <cyphermox> but in general, NM can try to bring up any valid connections if some details change about the devices, though I don't understand why it would catch any random usb connection. I should relaly be looking for an USB network device
[14:59] <cyphermox> jdstrand: radvd on rmnet_usb0?
[14:59] <jdstrand> cyphermox: let me double check the correlation with plugging in the device to the laptop
[14:59] <cyphermox> most providers don't do IPv6
[15:00] <jdstrand> cyphermox: no, sorry, on wlan0-- but it doesn't actually get an ip cause of the config I use
[15:00] <cyphermox> ok
[15:01] <cyphermox> we can look at IPv6 separately because I expect you'd see the exact same behavior on a desktop
[15:02] <jdstrand> cyphermox: actually, I made an assumption between plugging the device into the laptop and the device name. I unplugged, waited a few moments then plugged back in and syslog didn't show any change on rmnet_usb0
[15:02] <jdstrand> cyphermox: so the question is-- why are both up
[15:02]  * jdstrand gets you syslog
[15:03] <cyphermox> jdstrand: did you disconnect cellular yourself, and if so, how did you do it?
[15:03] <jdstrand> cyphermox: I did not disconnect or connect cellular myself
[15:03] <jdstrand> cyphermox: I have in the past, but not today
[15:03] <cyphermox> ok
[15:04] <cyphermox> well, I'd expect cellular to be up whenever it's available, unless explicitly disconnected
[15:04] <mandel> barry, I'll add rolling logs and will take a look what needs to be done for logrotate
[15:04] <cyphermox> so that should explain the extra nameservers there -- those are nameservers from the cellular data connection
[15:05] <jdstrand> cyphermox: so you are saying it is behaving as expected?
[15:05] <mandel> barry, the change to have our own file is not an issue for you, correct?
[15:05] <cyphermox> jdstrand: I think it is? unless there's extra things in syslog. what are you expecting it to do at this point?
[15:05] <jdstrand> cyphermox: yes, definitely from the cellular connection based on the log
[15:05] <barry> mandel: just the opposite - i think it's a big win
[15:06] <mandel> barry, great then :)
[15:06] <jdstrand> cyphermox: wouldn't I only have an ip if data was on? and if I'm on wireless, shouldn't data be off? and if not, if on on wireless, shouldn't it do the queries through it?
[15:07] <cyphermox> no, cellular data would still be on, but the routing should make it so that it doesn't get used
[15:07] <cyphermox> I see what you mean then
[15:07] <cyphermox> the DNS entries probably should not be there,
[15:08] <jdstrand> cyphermox: right, I noticed this because dns queries were going to the cell dns servers via my default route, rather than using the ones for wlan0
[15:08] <cyphermox> yeah
[15:08] <jdstrand> cyphermox: do you still need syslog?
[15:09] <cyphermox> maybe not after all
[15:09] <cyphermox> this is somewhat of a conflicting requirement though. You might want to always have the other devices' DNS entries if you're connected to wired and wireless on a desktop, for instance
[15:09] <jdstrand> shall I file a bug? and if so, against what?
[15:10] <cyphermox> yes, please file a bug against network-manager
[15:10] <balloons> ping mardy
[15:10] <cyphermox> maybe I should explicitly exclude modem devices when merging DNS data
[15:12] <cwayne> pitti: cyphermox: I think we're ready to upload the systemd changes for machine-info
[15:12] <cyphermox> cwayne: ack
[15:13] <cyphermox> awe_: I'm seeing something weird here
[15:13] <awe_> where's here?
[15:13] <cyphermox> awe_: after restart ofono because I found my phone was not connected to mobile data, I get a message about no SIM being present
[15:13] <cyphermox> awe_: my phone
[15:13] <awe_> mako?
[15:14] <awe_> can you take a quick peek @ the syslog and tell me if there are any ofonod error messages?
[15:15] <awe_> cyphermox, actually pretty sure it was maguro that could have issues with SIM & power-on; there's a MR pending that makes online/offline work much better; maguro had an issue where SIM_STATUS and IO calls would fail if the radio wasn't "Online"; whereas mako allowed these operations
[15:15] <cyphermox> this is on mako
[15:16] <cyphermox> let me check if there's something
[15:16] <awe_> ok; fyi the pending MR is: https://code.launchpad.net/~phablet-team/ofono/rilmodem-power-ussd/+merge/200909
[15:16] <awe_> rsalveti, any ETA on this one?
[15:17] <awe_> rsalveti, also may have another following soon on it's heels for a couple of recent bugs
[15:17] <landstalker> sergiusens: sorry, doesn't appear to work. It gets as far as rebooting into recovery to flash, then nothing happens
[15:17] <landstalker> http://pastebin.com/cK2jz44K
[15:18] <Elleo> bfiller: this is me (Mike Sheldon) on IRC for future reference :)
[15:18] <bfiller> Elleo: thanks Mike :)
[15:19] <cyphermox> awe_: there were issues with reading SIM structures earlier, but it didn't block a connection from being established
[15:19] <cyphermox> I'll reboot, watch it, and if it happens again I'll let you know
[15:20] <awe_> cyphermox, ok, if it does please get me the log messages for ofonod
[15:20] <awe_> cyphermox, there usually a couple log messages for certain SIM/USIM files that can't be read
[15:20] <awe_> because ofono tries to read as many files as it can, and some just aren't defined
[15:21] <awe_> but if the SIM is coming up !present, then that's something else...
[15:21] <awe_> also, if you hit it again, and you're feeling adventurous, grab the debs from the MR I posted above and try 'em
[15:22] <cyphermox> ok
[15:24] <cyphermox> awe_: seeing SMS History probe for modem.
[15:24] <cyphermox>  are you keeping SMS in the SIM store now? :)
[15:26] <awe_> no
[15:27] <awe_> SMS history is used for SMS delivery report notification
[15:27] <awe_> no SIM write support in rilmodem
[15:27] <awe_> however that might change soon, as it's something used by the message-waiting interface
[15:28] <cyphermox> heh, I was just asking because I didn't remember seeing that message before
[15:28] <awe_> it's been for a few weeks now...
[15:29] <cyphermox> I don't spend huge amounts of time looking at syslog on my phone, the urfkill development happens on my laptop first and then transfers on the phone when it looks like it works
[15:33] <jdstrand> cyphermox: fyi, bug #1270189
[15:33] <jdstrand> cyphermox: I put in some more thought on how to resolve it in the bug
[15:33] <cyphermox> ogra_: /persist, does that come up on boot in Ubuntu or does that come from when the android container starts?
[15:33] <cyphermox> jdstrand: thanks!
[15:33] <ogra_> cyphermox, /persist ?
[15:33] <cyphermox> yeah
[15:33] <ogra_> never head of that
[15:33] <ogra_> *heard
[15:34] <cyphermox> /android/persist :)
[15:34] <cyphermox> like /android/firmware and whatnot
[15:34] <cyphermox> it's just another partition that comes straight from the device
[15:35] <ogra_> cyphermox, well, then it comes from android, very weird, i dont have that here
[15:35] <sergiusens> landstalker, restart the adb server as root; your udev rules might be missing some bits
[15:35] <cyphermox> ogra_: on mako?
[15:36] <ogra_> cyphermox, yeah
[15:36] <cyphermox> if you don't have it bluetooth wouldn't be able to start
[15:36] <Anmol> hi developers :)
[15:37] <Anmol> i have a question
[15:37]  * ogra_ checks again 
[15:37] <balloons> ping kenvandine -- has mardy just not been around? Still wondering about online accounts api :-)
[15:38] <ogra_> cyphermox, oh, i do ...
[15:38] <ogra_> cyphermox, definitely an android thing
[15:38] <davmor2> Anmol: you are best to just ask then if someone can help they will
[15:38] <cyphermox> crap :(
[15:38] <kenvandine> balloons, not sure, i haven't talked to him in a couple days
[15:38] <Anmol> i want to dual boot nexus 4 with ubuntu touch i ran the script dualboot.sh
[15:39] <Anmol> can i use the files downloaded from phablet flash on my desktop on that installer?>
[15:40] <ogra_> cyphermox, why ?
[15:40] <cyphermox> hoping it's there early enough to rely on it in a udev rule
[15:41] <ogra_> it will most likely be mounted by the initrd
[15:41] <ogra_> udev starts really late inteh boot anyway
[15:41] <ogra_> after the container
[15:41] <Anmol> ogra!! how are you! i used phablet flash and it booted into ubuntu Thanks
[15:41] <Anmol> cna i dual boot using those files?
[15:41] <ogra_> Anmol, enjoy :)
[15:42] <ogra_> no idea, i never used dual boot
[15:42] <pmcgowan> ondra, ^^
[15:42] <ogra_> yeah, ask ondra
[15:42] <Anmol> ondra
[15:42] <cyphermox> ogra_: thanks, going to give it a spin
[15:43] <landstalker> sergiusens: it's already running as root and I've got a full udev ruleset, remember, I was able to manually do all the steps, it just wouldn't boot
[15:43] <sergiusens> landstalker, I can't remember what I have not read :-)
[15:43] <ondra> pmcgowan: looking
[15:43] <ondra> Anmol:
[15:43] <ogra_> sergiusens, what ?!?
[15:43]  * ogra_ shakes head
[15:44] <ogra_> you really need to work on that :P
[15:44] <sergiusens> ogra_, lol; I was about to explain it in detail for you
[15:44] <ogra_> :)
[15:44] <landstalker> sergiusens: ahh ok, I've already gone through the manual steps, fastboot flash the three files, then adb push both zip's and install, one at a time using autodeploy.zip name
[15:44] <sergiusens> landstalker, so you ran ubuntu-device-flash --bootstrap --channel devel ?
[15:45] <sergiusens> landstalker, that's not how you get latest though
[15:45] <landstalker> I'm currently doing this, from the initial bootloader screen
[15:45] <landstalker> ./ubuntu-device-flash -bootstrap -channel=trusty
[15:45] <landstalker> that has taken me into recovery, and is currently: 2014/01/17 15:43:41 Done pushing /home/lee/.cache/ubuntuimages/pool/device-7b30ad21714dba06f9022d6d43c8dbe5fa93854b0db167b440d333434f57242b.tar.xz.asc to device
[15:45] <ogra_> looks fine
[15:45] <ogra_> it should start flashing
[15:45] <landstalker> so the device is sat on recovery screen, and I'm just waiting :)
[15:46] <landstalker> is its anything like my last attempts, it will end with these lines
[15:46] <landstalker> 2014/01/17 15:32:59 Created ubuntu_command: /home/lee/.cache/ubuntuimages/ubuntu_commands394727820
[15:46] <landstalker> 2014/01/17 15:32:59 Rebooting into recovery to flash
[15:46] <landstalker> then nothing seemed to happen, I went looking for the ubuntu_commands file and it wasn't there
[15:47] <landstalker> ahhh it's doing it now
[15:47] <landstalker> spin you little android bleeder
[15:47] <sergiusens> landstalker, grouper you say
[15:47] <sergiusens> it's veeeery slow
[15:48] <landstalker> we talking tens of minutes or hours here?
[15:48] <sergiusens> remember; look at the device screen only if there's an error on the console you ran the command from ;-)
[15:48] <sergiusens> landstalker, minutes; 10 minutes to push, 10 to flash iirc
[15:48] <sergiusens> dont't use grouper myself for that specific reason, slow io
[15:49] <landstalker> well, it had quite and device was left on recovery screen. 10 minutes is fine, I've been playing with those numbers. I've tried this about 10 times now, using manual and your method, and the phablet-flash tool what was in rpm
[15:49] <landstalker> I thought grouper was Nexus 7?
[15:49] <ogra_> it is
[15:49] <ogra_> the 2012 version
[15:50] <ogra_> sergiusens, but shouldnt he see the android with the progressbar underneath ?
[15:51] <sergiusens> ogra_, not while files are pushing
[15:51] <sergiusens> just messages on host
[15:51] <ogra_> ah
[15:52]  * ogra_ hasnt flashed from scratch in a while 
[15:52] <ogra_> OTA makes you lazy
[15:53] <balloons> kenvandine, anyone else I can speak to or ?
[15:53] <landstalker> I've currently got the progress bar, so I'm happy it's doing, ooo, rebooting
[15:54] <landstalker> Google... Google... Googlee.... Googlee... come on, give me purple
[15:55] <landstalker> black screen, hmm
[15:55] <landstalker> Oooooo, woot
[15:55] <ogra_> patience
[15:55] <ogra_> :)
[15:55] <landstalker> well, no, I actually had to press the power button to wake it :)
[15:55] <landstalker> so, can I be the first to say, this is not a simple install :D
[15:55] <ogra_> yeah, the first boot might take lonnger than the screen timeout
[15:56] <ogra_> it is, if you have an ubuntu machine to install from :)
[15:56] <landstalker> true, but needing ubuntu to install ubuntu, a bit of that snake head tail thing going on, arboris?
[15:56] <ogra_> then it is just one copy/paste from the wiki after you installed the phablet-tools package
[15:57] <sil2100> tvoss: hello!
[15:57] <beuno> also, the target is for it to be pre-installed, right?  :)
[15:57] <ogra_> landstalker, you might hit a display driver bug where the display turns into a disco strobe ... in case you get that, adb shell rm /home/phablet/.display-mir && adb shell reboot
[15:58] <ogra_> that will switch you to surfaceflinger
[15:59] <landstalker> great, thanks. So, is sergiusens doesn't use grouper, what DO you use?
[15:59] <sergiusens> mako, manta
[15:59] <ogra_> mako ...
[15:59] <ogra_> maguro, grouper, manta for fiddling with stuff ...
[15:59] <ogra_> but mako as my daily phone
[16:00] <landstalker> all on a Nexus 7?
[16:02] <ogra_> no, nexus4 ...
[16:02] <landstalker> right, works, connected to my wireless
[16:02] <ogra_> (mako is nexus4)
[16:02] <landstalker> yeah,I'm on Nexus 7, so used grouper as I thought I would. So Nexus 7 2012 device is a bit slow for Ubuntu, not the image?
[16:03] <ogra_> grouper (nexus7) uses a tegra chip ... the driver isnt so great with Mir
[16:03] <ogra_> the best supported device we have is the mako (nexus4) ... thats snappy as hell
[16:04] <landstalker> I do have a Nexus 4, but its my phone, I barely use my Nexus 7
[16:04] <ogra_> my nexus4 is my phone too ;)
[16:05] <landstalker> ok, does doing the above you mentioned, without getting the strobe, switch from Mir to surfaceflinger?
[16:05] <ogra_> sure
[16:05] <nocomp> ola
[16:05] <ogra_> note that it disables some features that are only available in Mir
[16:05] <ogra_> so i wouldnt switch to SF if i dont need to
[16:06] <landstalker> I see
[16:06] <landstalker> briefly, what features would I lose?
[16:07] <landstalker> lol, just got strobe bug and now black screen
[16:07] <landstalker> I've touched it about 30 times including typing in a very long code
[16:07] <ogra_> app management works differently
[16:08] <landstalker> ahh its back again
[16:08] <doflah> what's the difference between QtMobility Sensors and QtSensors and is either supported on mako yet?
[16:13] <pmcgowan> doflah, qtsensors is supported, qtmobility is deprecated with 5.0
[16:14] <OttOmanTR> I hope Ubuntu Touch would bring more secure OS than Android http://blogs.360.cn/360mobile/2014/01/17/oldboot-the-first-bootkit-on-android/
[16:15] <ogra_> OttOmanTR, http://mdeslaur.blogspot.de/2013/12/ubuntu-touch-and-user-privacy.html
[16:16] <OttOmanTR> ogra_: reading
[16:21] <doflah> okay, I imported QtSensors 5.0 and included a RotationSensor - qtcreator gives it a red underline, but the program seems to run anyway
[16:22] <doflah> and mako is giving me readingChanged events so it looks like it's working
[16:24] <OttOmanTR> ogra_: Is it the same security model that iOS using?
[16:24] <ogra_> OttOmanTR, no
[16:24] <ogra_> it is the model that was developed for Ubuntu Touch
[16:25] <OttOmanTR> I saw a dialog on an iPhone that was informing me that xxxx app is wanting to access the address book.
[16:26] <ogra_> sure, there might be similarities in the UI
[16:26] <OttOmanTR> ogra_: ok
[16:27] <OttOmanTR> ogra_:  android's not having selective permissions is so stupid
[16:27] <landstalker> ok, thanks all, I've got to get some real work done now though. I'll consider writing a guide for Fedora installing Ubuntu Touch based on my findings and what worked for me. thank you all
[16:28] <ogra_> enjoy
[16:37] <mardy> balloons: hi! I'm on parental leave, just checking IRC from time to time
[16:38] <balloons> mardy, hi! Sorry to bother you while on leave! I'm trying to figure out the best way to use an online account as part of an autopilot test. It seems elopio too is looking into this. I was hoping perhaps there was a better way than what I've started hacking on
[16:39] <balloons> so I guess if I can bug you long enough to ask, is there an api or good way to do this? Or no?
[17:44] <mardy> balloons: what do you mean by "use an online account"? Is it something that you'd do from the app being tested, or from the python test itself?
[17:48] <balloons> mardy, so we have an app that in this case connects with evernote. I need to test the app. The tests can run if I've already setup an evernote account and authenticated it in online accounts. We need a way to do this programmatically so the autopilot test can run on a fresh machine using a test account
[17:48] <rickspencer3> sergiusens not sure if you're around, but you seem like a good guy for this question
[17:48] <rickspencer3> I suspect that my phone's drive is full
[17:49] <rickspencer3> wondering if there are any system dirs or anything that I should check to make sure there's not cruft filling up the drive somewhere (and a related bug to fix)
[17:49] <ogra_> rickspencer3, logs most likely
[17:49] <ogra_> (as we discussed a few times today ... we need to make sure they get thrown away, not rotated)
[17:50] <rickspencer3> ogra_, so, known issue I should drop it, or do you want me to look?
[17:50] <mardy> balloons: OK, so I'd say that your best bet is using account-console
[17:50] <ogra_> rickspencer3, drop it ?
[17:50] <mardy> balloons: it's a command-line tool which you can use to create accounts
[17:50] <balloons> mardy, oO.. tell me more :-)
[17:51] <rickspencer3> drop it == assume that you assume folks have it handled, just rm * in /var/logs and go about my business ;)
[17:51] <mardy> balloons: it's written in python, so if you prefer you could even directly steal its code and do the creation from within your autopilot test
[17:51] <ogra_> rickspencer3, well, depends how full it is :)
[17:51] <ogra_> rickspencer3, du -hcs /var/log/*
[17:51] <mardy> balloons: there's one big catch, though...
[17:51] <rickspencer3> hmmm, I know -h, but not cs
[17:51]  * rickspencer3 tries
[17:52] <mardy> balloons: soon we'll enforce access control on the accounts
[17:52] <rickspencer3> 844M	total
[17:52] <rickspencer3> seems like a lot of logs ;)
[17:52] <ogra_> geeez !
[17:52] <mardy> balloons: meaning that before an app will be able to use an account, it needs to ask permissions to the user
[17:52] <rickspencer3> ogra_,
[17:52] <rickspencer3> 265M	/var/log/kern.log
[17:52] <rickspencer3> 311M	/var/log/kern.log.1
[17:52] <mardy> balloons: and this will involve popping up a UI, and doing some stuff
[17:52] <ogra_> wow
[17:52] <rickspencer3> the kernel logs are quite nuaghty
[17:53] <rickspencer3> syslogs too
[17:53] <ogra_> rickspencer3, file a bug please
[17:53] <balloons> mardy, will there be a way to avoid doing that for our tests?
[17:53] <mardy> balloons: I tried, but I couldn't do that with autopilot (at least, not on the device)
[17:53] <rickspencer3> ogra_, will do
[17:53] <cwayne> pitti: ping (re: systemd + livecdrootfs)
[17:53] <ogra_> thx
[17:53] <balloons> elopio, see above and follow along :-) ^^
[17:53] <balloons> mardy, is this an apparmor thing or something in online accounts or ?
[17:53] <mardy> balloons: yes, it makes sense that we add a new parameter to the account-console tool, to add a certain app to the ACL
[17:54] <ogra_> rickspencer3, feel free to assign me, i'll look next week
[17:54] <pmcgowan> rickspencer3, check /var/crash
[17:54] <rickspencer3> ogra_, may I assume it's safe to rm all those logs?
[17:54] <pmcgowan> that gets big here
[17:54] <mardy> balloons: both; OA uses apparmor to determine who's the caller, and decides whether to allow the access or not
[17:54] <ogra_> pmcgowan, well, 800M logs is already a lot
[17:54] <pmcgowan> ogra_, yeah I have 300M
[17:54] <ogra_> but yeah, crashes too
[17:55] <rickspencer3> this is why we have Avengers
[17:55] <rickspencer3> I bet since i use my pone so much ... I get bitten by this worse than some
[17:55] <elopio> balloons, mardy: reading.
[17:55] <pmcgowan> rickspencer3, delete all the .gz files thats safe
[17:55] <cwayne> mardy: hey (since you're here :) ) is the app-access branch waiting for that mir re-parenting bug?
[17:55] <rickspencer3> ogra_, what project do you want me to file the bug agains?
[17:55] <ogra_> pitti, ev, is there any way we could clean up /var/crash regulary (i.e. throw away .crash files if they didnt get processed for a week or some such)
[17:56] <elopio> mardy: I have a list of requirements to make online accounts more testable.
[17:56] <elopio> while you are on leave, who's in charge?
[17:56] <mardy> balloons: so, if we have a way to ask account-console to add an app to the ACL for an account, that could be made to work without invoking any UI
[17:56] <ogra_> rickspencer3, rsyslogd in ubuntu
[17:56] <ogra_> or better logrotate
[17:56] <ogra_> we need to set it to throw away old logs instead of compressing and keeping them
[17:56] <balloons> mardy, hmm ok. Using account-console sounds like the way to go. This app isn't the only one with this issue :-)
[17:57] <ogra_> but there is also to much logging from the kernel i suppose
[17:57] <mardy> elopio: I have no clue :-) I'd say that the best help could come from kenvandine
[17:57] <mardy> elopio: though he's not on charge, he knows most about OA after me :-)
[17:57] <balloons> mardy, other options would be to use autopilot to drive the UI for online accounts (ugh), or use a fake sso server or fake the auth request, etc..
[17:58] <mardy> cwayne: hi! No, it's mainly waiting for me to be back from parental leave and fix a few issues that alex-abreu found during the review
[17:58] <elopio> mardy: when are you back?
[17:58] <mardy> cwayne: I'll try to do that while on leave, actually, but the issue is that I've really not much free time
[17:58] <elopio> not pushing, just want to know :)
[17:58] <mardy> elopio: 27th
[17:58] <cwayne> mardy: noo, enjoy your leave! (and congratulations!) I was mostly just curious :)
[17:59] <mardy> balloons: I'd vote for adding the feature to account-console, it's going to be useful in some recovery situations :-)
[17:59] <balloons> elopio, do you see issues with using account-console?
[17:59] <rickspencer3> thanks ogra_
[17:59] <rickspencer3> https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1270248
[18:00] <balloons> so to confirm mardy account-console will work now, but work needs to be done to ensure it will continue to work after you land the ACL changes right?
[18:01] <mardy> balloons: care to file a bug? (account-plugins project)
[18:01] <mardy> balloons: correct
[18:01] <elopio> balloons: well, I see some problems. First, it will modify the user keyring.
[18:02] <elopio> se we can't run these tests on a developer machine.
[18:02] <balloons> mardy, I'd be happy to. I just want to make sure the work happens inline with the acl changes so things stay running smooth for us. Is account console packaged, so we can have a dependency on it?
[18:02] <elopio> I think we can live with this while mardy is away.
[18:03] <elopio> balloons: account-plugin-tools
[18:04] <rickspencer3> ogra_, thanks, hopefully my phone will work ok now
[18:04] <rickspencer3> I deleted the kernel and sys logs
[18:04]  * ogra_ crosses fingers
[18:04] <balloons> elopio, ok. Can we backup and replace the keyring? Regardless yes, I think mardy has given us an answer for now. So ty!
[18:04] <elopio> balloons: maybe. Still not ideal. Ideal would be to use a fake one.
[18:05] <elopio> but yes, I agree. We have a lot of information now to start playing.
[18:41] <balloons> mardy, ty for help.. bug filed; https://bugs.launchpad.net/account-plugins/+bug/1270264
[20:06] <davmor2> if I type weather in dash search on the phone is it not meant to tell me the weather from my location? I'm sure I read that somewhere in scopes
[20:11] <beuno> davmor2, yes on the desktop, I would assume yes on the phone
[20:16] <cwayne> davmor2: yeah, based on geoip
[21:30] <sergiusens> is mr balloons in da house?
[21:30] <balloons> lol sergiusens
[21:31] <sergiusens> balloons, go something for you
[21:31] <balloons> oO is it what I'm thinking it is?
[21:36] <sergiusens> balloons, what was your bug number?
[21:36] <balloons> https://bugs.launchpad.net/phablet-tools/+bug/1269163
[21:39] <balloons> click buddy I love it
[21:39] <sergiusens> balloons, https://code.launchpad.net/~sergiusens/phablet-tools/click-buddy/+merge/202178 would work with https://code.launchpad.net/~sergiusens/ubuntu-calculator-app/cmake/+merge/202176
[21:39] <sergiusens> balloons, :-)
[21:39] <balloons> so awesome..
[21:40] <sergiusens> balloons, I just need validation of the general strategy and then move on to all others
[21:41] <balloons> right.. if it works as expected, we can apply everywhere
[21:41] <sergiusens> balloons, well I just tested it on the calculator branch I gave you :-)
[21:43] <sergiusens> balloons, give it a go, and feel free to approve the phablet-tools one as it would be a prereq for the whole flow
[21:43] <sergiusens> rsalveti, mind reviewing as well ^^
[21:43] <sergiusens> gf is here; going to go down and say hello
[21:43]  * sergiusens will bbl
[21:45] <balloons> I'll run it now
[23:08] <landstalker> thanks for everyones help today, I've written a guide to installing Ubuntu Touch onto a Nexus 7 from Fedora 20, it's extrememly rough and long: {include download link for udev rules}
[23:08] <landstalker> wrong, bit
[23:09] <landstalker> http://www.leenukes.co.uk/2014/01/17/installing-ubuntu-touch-onto-nexus-7-2012-from-fedora-20-in-depth/
[23:10] <popey> nice one landstalker
[23:13] <cwayne> or, in ubuntu: apt-get install ubuntu-device-flash; ubuntu-device-flash
[23:13] <cwayne> done
[23:13] <cwayne> :D
[23:14] <cwayne> but landstalker this is nice, well written :)
[23:14] <cwayne> there's a guide for flashing from OSX too
[23:39] <mhall119> landstalker: nice writeup!
[23:47] <landstalker> thanks, took a while which shouldn't have done really, I go into too much depth and then get bored and leave out important bits
[23:48] <mhall119> I was happy to see the new golang udf bringing this to more than just Ubuntu
[23:49] <mhall119> much of the rest of it probably get's done in Ubuntu when you install the SDK packages
[23:50] <mhall119> the Ubuntu SDK that is
[23:50] <mhall119> I don't recall installing the Android SDK, just the packages with the adb tools
[23:50] <mhall119> but I may have already had the Android SDK installed from previous experimentations
[23:51] <mhall119> is sudo not part of a default Fedora install?
[23:54] <landstalker> yeah I was talking to the guy who wrote it on here earlier, not much documentation for it from what I could see, which was a bit of a stumbling block
[23:55] <landstalker> mhall119: you don't really need the whole SDK, but for arguments sake, I did that whole thing. You're right though, I could narrow it down. I also don't think ubuntu-device-flash uses sudo but meh
[23:55] <landstalker> I put that in there as that's what I was using when I was manually flashing and getting nowhere
[23:58] <mhall119> yeah, udf is still pretty new, I'm sure docs will be forthcoming
[23:58] <mhall119> and by "I'm sure" I mean "I'll take a work item to make somebody write them" :)