[00:37] <saidinesh5> Elleo: ping...
[08:47] <mardy> bzoltan_: hi! Do I understand right, that qmake is currently not supported by our sdk?
[09:24] <Mirv> mardy: he's on holiday for today still. currently yes, but qmake support is upcoming AFAIK.
[09:24] <Mirv> cross-compilation is trickier with it than with cmake
[09:33] <mandel> ogra_, whenever you have the time, let me know so that we can talk about the adb work :)
[09:33] <mandel> ogra_, I'll be dealing with my email in the mean time and some udm stuff :)
[09:39] <mardy> Mirv: OK, thanks
[09:40] <ogra_> mandel, will do
[09:40] <mandel> ogra_, I have a number of reviews to do, so take your time, but I'd like to get to the standup saying that I  at least started with it :)
[10:08] <mvo> ogra_: do you have any concerns about http://paste.ubuntu.com/8800923/ for platform.vivid ? all kernels that I remove there are only available up to trusty, linux-image-dove is only available in lucid. I'm trying to get to the bottom of the armhf failure of https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-core-system-image and that seems like one possible source of error (although I still don't get where linux-mx5 comes fro
[10:08] <mvo> m :/)
[10:15] <ogra_> mvo, that looks like the same issue we had with other images when the build tried to run on PPAs ... for the kernels, ask the kernel team
[10:15] <ogra_> mvo, did infinity look into that yet ?
[10:15] <ogra_> he should be able to tell if the build falsely tries to use a PPA builder
[10:16] <mvo> ogra_: aha, I will ask him, thanks
[10:16] <ogra_> i surprised we still have dove ... :)
[10:16] <mvo> ogra_: well, its in the seed but its not in the archive since lucid
[10:17] <ogra_> yeah
[10:17] <mvo> ogra_: smeels like bitrot, this is why  I want to get rid of it
[10:17] <ogra_> right, not sure if we use any of tehse kernels still ... only kernel team knows i guess
[10:17] <ogra_> theoretically they should all be in -generic nowadays
[10:18] <ogra_> but there are some that we still have in older LTS ... not sure they need them in the latest -devel for possible backports etc
[10:20] <mvo> right, I will ask. I can't think why we have them in platform.vivid, but my imagination may just not be good enough ;)
[10:20] <ogra_> like mine :)
[10:29] <ogra_> mandel, soo ...
[10:35] <JamesTait> Good morning all; happy Monday, and happy Cliché Day! :-D
[10:39] <mandel> ogra_, are you free?
[10:39] <ogra_> mandel, i am ...
[10:39] <ogra_> mandel, so you want to apt-get source android-tools
[10:39] <mandel> ogra_, I walked with sergio about what has to be done, I wanted to know if you have more details, for example, the exact signals to listen too etc..
[10:39] <ogra_> mandel, not really, the mtp-server code should have them
[10:40] <ogra_> i guess you want to hook into services.c in core/adbd/ in the source
[10:40] <ogra_> and make the shell wait until the right signal is goming down the dbus
[10:40] <mandel> ogra_, ok, got it, any preference in the lib for dbus to use? I was considering glib one but I'm open to use other
[10:40] <ogra_> glib sounds fine
[10:41] <ogra_> (dont forget to add a build dep etc)
[10:43] <mandel> ogra_, yes, I'll not forget that :)
[10:43] <mandel> ogra_, then I'll start on it, do we have unit tests for that thing? or do I have to do some integration tests/test plan?
[10:43] <ogra_> and be careful with quilt ... its awfully broken in that package for whatever reason
[10:44] <ogra_> mvo's glorious edit-path simply doesnt work with it ... so you need to manually pop/push patches on the stack
[10:44] <ogra_> (i'll fix the whole thing once we switch to the new source)
[10:45] <mandel> ogra_, ok, you just managed to scare me :-/
[10:45] <ogra_> haha
[10:45] <ogra_> it *is* scary
[10:46] <ogra_> just check with debdiff if the changes are *really* in the package in the end
[10:47] <mvo> ogra_: oh, what package is that? maybe I need to look at edit-patch again to see if thats something I could fix
[10:48] <mvo> but lunch first :)
[10:48] <ogra_> mvo, that backage is pure horror :) it is android-tools
[10:48] <ogra_> i will re-do it in vivid during this cycle anyway, so dont bother to much
[10:49] <ogra_> there is more code in patches  than in the upstream source :)
[10:49] <mandel> ogra_, lets fork it!
[10:49]  * mandel hides
[10:49] <ogra_> mandel, kind of :)
[10:50] <ogra_> we'll switch to a 4.4 source anyway ... and i'll try to merge the patches where i can
[10:52] <ogra_> mandel, create_subproc_thread() is the function in services.c you want to stop btw
[10:53] <mandel> ogra_, awesome! thx for that, I was looking at the code atm :)
[10:53] <ogra_> right before it calls create_subprocess for sudo
[11:25] <Elleo> saidinesh5: sorry, wasn't around much at the weekend, around today if you still need something :)
[11:38] <ogra_> mvo__, i'm planning to merge the two branches from jodh_ today (from https://code.launchpad.net/~ubuntu-core-dev/livecd-rootfs/trunk/+activereviews) any objections ?
[11:38] <ogra_> seems to be for your stuff
[11:39] <ogra_> they are largely just copy/paste bits from tough
[11:39] <ogra_> *touch
[11:39] <mvo__> ogra_: no objections - but https://code.launchpad.net/~jamesodhunt/livecd-rootfs/system-image-really-really-please-just-work-fix-resolvconf-for-ubuntu-core/+merge/237800 may not be needed (for us at least) as we deal with this now in the chroot.includes part
[11:40] <ogra_> could you comment on the MP ?
[11:40] <ogra_> i'll leave it out for now til jodh_ had time to comment on it
[11:40] <mvo__> ogra_: done
[11:41] <ogra_> thx
[11:41] <mvo__> yw
[11:42] <ogra_> hmm. just tried to merge the other one ... seems that is already there
[11:43] <ogra_> except for an extra set -x at the top
[12:06] <saidinesh5> Elleo: ping
[12:06] <saidinesh5> still here?
[12:07] <saidinesh5> Elleo: so basically the issue was i couldn't get a development environment for ubuntu-keyboard up and running on my nexus 7
[12:07] <saidinesh5> or
[12:07] <saidinesh5> even on desktop
[12:07] <saidinesh5> on the nexus 7
[12:07] <saidinesh5> sudo apt-get build-dep ubuntu-keyboard pulls in qt5-default which pulls in a ton of X11 dependencies which bricks the device
[12:07] <saidinesh5> on PC
[12:08] <saidinesh5> i have no clue why my ubuntu-sdk is failing to build an arm binary
[12:08] <saidinesh5> it just says qmake exited with error code 1
[12:13] <Elleo> saidinesh5: there are problems cross-build qmake projects at the moment (which is why most have switched to cmake), apparently that's likely to be resolved in the future though (but if it isn't we'll probably finally get around to switch the keyboard to cmake at some point)
[12:14] <saidinesh5> ohh
[12:14] <saidinesh5> but how do you build for the
[12:14] <saidinesh5> device right now?
[12:14] <ogra_> use a chroot on the device
[12:14] <Elleo> saidinesh5: my only guess on the bricking issue would be that it might be pulling in the wrong libgl mesa packages, since it has the option of a couple (either the gles version of the standard gl version)
[12:14] <saidinesh5> chroot on the device?
[12:14] <ogra_> it wont affect the running system then,, even when installing x11 bits
[12:15] <saidinesh5> Elleo: oh i thought it was x11 but yeah even libgl mesa were installed
[12:15] <Elleo> saidinesh5: I build directly on a phone without issues, these are the deps I install: debhelper doxygen libgl1-mesa-dev libgles2-mesa-dev libglib2.0-dev libgsettings-qt-dev libhunspell-dev libpinyin4-dev libplatform-api1-dev libpresage-dev libxml2-utils maliit-framework-dev  pkg-config python-setuptools qt5-default qtbase5-dev qtdeclarative5-dev qtdeclarative5-private-dev xvfb presage
[12:15] <Elleo> well plus build-essential
[12:16] <Elleo> anything else should already be present on the image
[12:16] <saidinesh5> oh
[12:16] <saidinesh5> Elleo: which image do you use?
[12:16] <Elleo> saidinesh5: vivid now, utopic previously for dev (the rtm repos don't have most build stuff in them)
[12:16] <saidinesh5> ohh
[12:16] <saidinesh5> is it available via multirom?
[12:17] <saidinesh5> just a sec
[12:17] <saidinesh5> brb in 5
[12:17] <Elleo> well I use vivid-proposed, but straight utopic/vivid should work too (although I don't think we've promoted a vivid image yet)
[12:17] <Elleo> saidinesh5: basically devel or devel-proposed should be fine
[12:17] <Elleo> saidinesh5: not familiar with multirom I'm afraid, but I'd suspect at least devel would be available
[12:22] <saidinesh5> Elleo: just a sec
[12:22] <saidinesh5> rebooting tablet
[12:22] <saidinesh5> into
[12:22] <saidinesh5> utouch
[12:22] <saidinesh5> there goes the savegame4
[12:22] <saidinesh5> pfffft
[12:33] <saidinesh5> ogra_: btw. any links on how to setup a chroot on the device?
[12:33] <saidinesh5> not sure if i want to brick the device once more...
[12:33] <ogra_> saidinesh5, like you would do on any other ubuntuu :)
[12:33] <saidinesh5> lol okay googling
[12:33] <ogra_> read up about deboostrap and the chroot command
[12:33] <saidinesh5> Ah
[12:34] <ogra_> debootstrap to create tthe chroot ... chroot to enter it and work in it
[12:34] <Tassadar> saidinesh5: vivid doesn't have any images in it yet, so devel still points to utopic, but devel-proposed is vivid-proposed
[12:34] <saidinesh5> Tassadar: i was running utopic devel
[12:35] <saidinesh5> Ubuntu 14.10 r243
[12:37] <saidinesh5> btw. Elleo ogra_ http://paste.kde.org/pdwakoory are the packages pulled in by qt5-default
[12:38] <saidinesh5> so libegl-mesa is there
[12:38] <ogra_> yeah, you dont really want that installed since it might bend the alternative for the driver to mesa
[12:38] <ogra_> which is why i sugegsted working iin a chroot
[12:38] <ogra_> *suggested
[12:39] <saidinesh5> yeah thats what was bricking my device
[12:39] <saidinesh5> that and sshfs (which even breaks multirom)
[12:39] <saidinesh5> sshfs brings in fuse which somehow updates the kenel in a weird way
[12:39] <ogra_> not the kernel, but the initramfs
[12:39] <saidinesh5> mhm
[12:40] <saidinesh5> i think so
[12:40] <saidinesh5> all i could notice was it was in /boot
[12:40] <ogra_> right, it is supposed to update the initrd for devices that need fuse filesystems during boot
[12:40] <ogra_> and seemingly multirom doesnt cope well with that
[12:40] <Tassadar> multirom can't handle apt-get updating the kernel/initrd
[12:41] <Tassadar> because it rewrites the boot partition, which isn't ubuntu's to rewrite when installed in multirom
[12:41] <ogra_> ( i doubt anyone cares, even for non multirom ... apt on touch is an adventure, if it breaks you gotta keep the pieces)
[12:42] <Tassadar> yeah, it can be hacked around, but I'm not sure if it is necessary
[12:42] <saidinesh5> Ahh
[12:42] <saidinesh5> ogra_: could you pastebin yoru schroot config file?
[12:43] <ogra_> i dont have one
[12:43]  * ogra_ doesnt use schroot
[12:43] <ogra_> just plain chroots
[12:43] <saidinesh5> oh
[12:44] <saidinesh5> ogra_: so where do i create the chroot in?
[12:44] <saidinesh5> my home?
[12:44] <saidinesh5> or in / ?
[12:44] <Elleo> saidinesh5: you might actually be able to use the click tools to setup a chroot for you with minimal effort
[12:44] <ogra_> your home
[12:44] <saidinesh5> ohh
[12:44] <ogra_> oh, right, that might work as well for an armhf chroot on your PC
[12:45] <saidinesh5> but for armhf chroot don't i need scratchbox or something?
[12:45] <Elleo> sudo click chroot -a armhf -f ubuntu-sdk-14.10 create <-- might work (on device)
[12:45] <saidinesh5> Elleo: not sure, my ubuntu-sdk seems to be quite broken. it cant even compile the cmakebased helloscopes project
[12:46] <Elleo> saidinesh5: the scopes template is broken for everyone as far as I can see :P
[12:46] <saidinesh5> ohh O_O
[12:46] <Elleo> saidinesh5: there's a missing dependency in the chroot that the sdk setups up: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1387545
[12:46] <saidinesh5> Ahh
[12:46] <saidinesh5> i thought i was my tinkering
[12:47] <Elleo> saidinesh5: on the desktop it'll use qemu for cpu emulation iirc, but I believe there's still some issues with some of the qt tools under those circumstances, could be worth a try first though to be sure
[12:47] <davidcalle> Elleo, saidinesh5, I thought this was fixed in the SDK PPA, are you using it?
[12:47]  * saidinesh5 checks
[12:48] <saidinesh5> Ahh
[12:48] <saidinesh5> ubuntu-sdk-team-ppa-trusty.list
[12:48] <saidinesh5> was the ppa
[12:48] <saidinesh5> i had
[12:48] <Elleo> davidcalle: yep, I've got the sdk-team ppa enabled, and it didn't seem to help at the weekend
[12:48] <saidinesh5> but i think it got disabled during distupgrade
[12:49] <Elleo> davidcalle: although its possible I only tried to update ubuntu-sdk from it
[12:49] <Elleo> davidcalle: so if the fix is in another package I might not have got it
[12:49] <Elleo> davidcalle: ah yeah, there's an update to qtcreator-ubuntu-plugin
[12:51] <davidcalle> Elleo, it should bring new scopes templates (Still C++, but with some Qt libs to ease Json and XML parsing), and hopefully the xgettext fix
[12:51] <Elleo> davidcalle: oh, interesting; I've already got my stuff working with the existing json lib, but might rewrite it
[12:52] <Elleo> davidcalle: how's the Go based scope stuff coming? It'd be really nice to be able to use download-manager and content-hub from a scope, but the C++ APIs for those aren't publicly supported
[12:54] <davidcalle> Elleo, it exists and works, but I think that some issues are still being worked on. cwayne, do you know if we are going to have "official support" for Go soon?
[12:55] <Elleo> davidcalle: ah, okay; I can probably hack around something with launching the browser to download things, but it'd be much nicer to do it directly
[12:55] <cwayne> davidcalle: not sure when we'll have official support
[12:55] <sergiusens> Elleo: go get launchpad.net/udm
[12:55] <Elleo> davidcalle: although, that said the content picker wouldn't be available since that's QML
[12:55] <Elleo> sergiusens: the problem is that UDM breaks ABI from time-to-time
[12:55] <sergiusens> Elleo: it wraps over dbus
[12:55] <Elleo> sergiusens: ah, good point
[12:55] <saidinesh5> Elleo: so click chroot fails after
[12:55] <saidinesh5> E: Couldn't download dists/utopic/main/binary-armhf/Packages
[12:55] <sergiusens> which doesn't break :-)
[12:56] <Elleo> sergiusens: might be able to talk to content-hub directly over dbus too
[12:56] <Elleo> sergiusens: would have to hard code the music app as the recipient of music files, but that's not the end of the world
[12:57] <Elleo> although iirc there were some plans for content-hub stuff built into scopes discussed
[12:57] <Elleo> so it might be worth just waiting for that to become clearer
[12:57] <Elleo> saidinesh5: does your device's network connection work okay?
[12:58] <saidinesh5> http://paste.kde.org/pudmstuml
[12:58] <saidinesh5> Elleo: ^
[12:59] <Elleo> saidinesh5: not sure what to suggest I'm afraid, other than to try setting up a chroot normally; but since that'll also use debootstrap I suspect it might fail in the same way
[12:59] <saidinesh5> ohh
[13:00] <saidinesh5> :|
[13:00] <saidinesh5> technically i should have a same chroot in my ubuntu-sdk right?
[13:01] <saidinesh5> can i just scp it from my PC?
[13:01] <saidinesh5> or it might take too long
[13:01] <saidinesh5> hmm...
[13:01] <Elleo> saidinesh5: I suspect that might get setup a little differently to allow for cpu emulation, not entirely sure the details of that though
[13:02] <saidinesh5> ohh
[13:02] <saidinesh5> hmm...
[13:02] <saidinesh5> also Elleo i tried building a qt5 application just before
[13:02] <saidinesh5> the device bricked
[13:02] <saidinesh5> and tried running it again on a fresh install
[13:03] <saidinesh5> http://paste.kde.org/pznombeqj
[13:03] <saidinesh5> is what i get
[13:03] <Elleo> saidinesh5: try ./skeyer_demo --desktop_file_hint=/usr/share/applications/webbrowser-app.desktop
[13:04] <saidinesh5> O_O
[13:04] <saidinesh5> it works!
[13:04] <Elleo> saidinesh5: mir wont accept a connection from a client unless it knows what app its coming from (which it gets via the .desktop), giving it the .desktop of an unconfined app will get it to load
[13:04] <saidinesh5> Ahh
[13:04] <Elleo> saidinesh5: normally it'd get that automatically when launched from the launcher
[13:06] <saidinesh5> interesting
[13:06] <saidinesh5> Elleo: any notes on how to run a qemu environment on the desktop then?
[13:07] <saidinesh5> the ones installed by ubuntu-sdk
[13:08] <saidinesh5> okay i think i can use click :D
[13:08] <saidinesh5> click chroot blah blah blah run
[13:08] <saidinesh5> but meh
[13:08] <saidinesh5> $ qmake
[13:08] <saidinesh5> qmake: could not find a Qt installation of ''
[13:08] <Elleo> saidinesh5: 'click chroot -a armhf -f ubuntu-sdk-14.10 maint' should give you a shell
[13:09] <saidinesh5> oh
[13:09] <saidinesh5> what is maint for?
[13:09] <saidinesh5> and same problem there too
[13:09] <Elleo> might be that some qt dev packages aren't installed by default
[13:09] <saidinesh5> ohh
[13:09] <Elleo> saidinesh5: maintenance basically iirc
[13:09] <saidinesh5> but shouldnt ubuntu-sdk take care of that?
[13:10] <bzoltan_> Elleo: saidinesh5: that env is not an emulated one... that is a simple multiarch chroot
[13:10] <Elleo> bzoltan_: ah, okay
[13:10] <bzoltan_> saidinesh5:  what exactly you try to do?
[13:10] <saidinesh5> bzoltan_: i wanted to set up a development environment for ubuntu keyboard
[13:11] <Elleo> bzoltan_: which is currently still qmake based
[13:11] <saidinesh5> i cant compile the packages on device cuz the qt5-default pulls in all the libgl packages and breaks the system
[13:11] <bzoltan_> saidinesh5:  ahh, I am sorry, but i am not familiar with the keyboard development env. How different is from the normal app development env?
[13:11] <ogra_> bzoltan_, oh, are you back from vac. ?
[13:12] <ogra_> bzoltan_, i have bug 1388569 for you then :)
[13:12] <bzoltan_> ogra_: No, I am still enjoying it
[13:12] <ogra_> ah, k
[13:12] <saidinesh5> can't set up a chroot on the device because..... i dont know. it just fails to download them http://paste.kde.org/pudmstuml bzoltan_
[13:12] <ogra_> then i'll ping again tomorrow :)
[13:12] <Elleo> saidinesh5: have to pop out to get some lunch quickly, back shortly
[13:12] <saidinesh5> Ah sure.. bon apetit :)
[13:12] <bzoltan_> ogra_:  without clicking to that bug I can tell you that they should use the popup properly ... just like it was problem with the settings app
[13:13] <ogra_> bzoltan_, well, it seems ot be in all popups
[13:13] <bzoltan_> ogra_:  but i will pull kalikiana on it
[13:13] <ogra_> *to
[13:13] <saidinesh5> so now i m trying to get a qemu based shell up and running on the desktop so i can compile something to run on the tablet
[13:13] <ogra_> bzoltan_, thanks
[13:50] <jgdx> mpt, hi, apn for multi sim needs some clarification in bug 1388044
[13:50] <jgdx> specifically how it is laid out
[14:00] <nadsumatal> hello
[14:00] <rickspencer3> hey, when I popped my SIM into my maco, the dialer says that I have to unlock my pin
[14:00] <ogra_> rickspencer3, longstanding issue
[14:00] <rickspencer3> but when I go to settings, it implies that my SIM is unlocked
[14:00] <rickspencer3> ogra_, is there a workaround?
[14:01] <ogra_> set a PIN
[14:01] <rickspencer3> ogra_, arg, so I forget my PIN which I have to enter to set a pin
[14:01]  * rickspencer3 shakes fist
[14:02] <Elleo> rickspencer3: there's an MR that fixes it: https://code.launchpad.net/~tiagosh/telepathy-ofono/fix-sim-lock/+merge/238202
[14:02] <Elleo> rickspencer3: not sure where/when it landed though
[14:02] <ogra_> didnt yet
[14:02] <Elleo> ah, right
[14:02] <ogra_> at least the same issue is still around in the promotion candidate on mako
[14:03] <ogra_> QA saw it on friday
[14:03] <Elleo> rickspencer3: I installed the packages from those manually and it fixed it for me
[14:05] <cwayne> Elleo: any idea when the 'turn off autocorrect for email address' branch will land?
[14:05] <Elleo> cwayne: hopefully this week now that we've cleared up what the issue om26er was having was
[14:08] <davmor2> rickspencer3: if it is the default pin it will be on a website somewhere, if it is a pin you have set try day and month of birth
[14:15] <dobey> rickspencer3: downgrading telepathy-ofono package on my nexus5 fixed it for me. and i haven't seen the issue since (even though i've installed updates and even flashed over to rtm channel now)
[14:20] <mterry> kenvandine, morning!  I saw that u-s-s hit vivid!  :)
[14:20] <kenvandine> mterry, yes... but there are issues :-/
[14:20] <mterry> kenvandine, oh  :(
[14:20] <kenvandine> mterry, not in the wizard, that i know of though :)
[14:20] <kenvandine> the upower transition
[14:20] <kenvandine> the battery panel is causing a crash now
[14:21] <Elleo> saidinesh5: did you try the explicit depends I suggested? I suspect different dependencies might get selected for the qt5 package if libgles2-dev is installed
[14:21] <mterry> kenvandine, oy
[14:21] <saidinesh5> Elleo:  oh wb
[14:21] <mterry> kenvandine, anything I can help with?
[14:21]  * saidinesh5 checks
[14:22] <kenvandine> mterry, you could figure out the crash if you have time :)
[14:22] <saidinesh5> Elleo: it has qt5-default
[14:22] <saidinesh5> so nope... thats a no go
[14:22] <mterry> kenvandine, how does this affect rtm?  I assume the rtm silo did not include the upower stuff
[14:22] <kenvandine> it doesn't
[14:23] <mterry> phew
[14:23] <kenvandine> indeed
[14:23] <Elleo> saidinesh5: yeah, but qtbase5-dev (which is the main thing qt5-default depends on that brings in libgl related things) has optional dependencies for different packages
[14:23] <kenvandine> the battery panel worked at some point in the vivid silo
[14:23] <kenvandine> but there was several pieces landing while it was held in proposed
[14:23] <kenvandine> and powerd was crashing at the same time as uss, but then that stopped crashing
[14:24] <Elleo> saidinesh5: so different packages will get selected if you already explicitly list libgles2-mesa-dev vs libgles2-dev, etc.
[14:24] <saidinesh5> Ohh
[14:24] <saidinesh5> let me check
[14:24] <kenvandine> need to install the dbg packages to get a good trace
[14:24] <Elleo> saidinesh5: I'd suggest trying the line of dependencies I listed and see what it plans to pull in
[14:25] <Elleo> saidinesh5: as that certainly works for me on phones
[14:26] <mterry> kenvandine, want any help with the rtm silo?  Is it just the continue bug or are there other scheduled rtm issues?
[14:26] <saidinesh5> Elleo: http://paste.kde.org/pyqsdkiwg
[14:27] <saidinesh5> so is it okay to go ahead?
[14:27] <Elleo> saidinesh5: probably not, that's still bringing in libegl packages
[14:27] <Elleo> saidinesh5: I guess something must differ between the tablet images and the phone images
[14:27] <saidinesh5> i guess so
[14:27] <kenvandine> mterry, nah
[14:27] <saidinesh5> but Elleo i think this is a phone image
[14:27] <kenvandine> mterry, just waiting for QA verification on that
[14:27] <saidinesh5> i used multirom
[14:28] <saidinesh5> and well it shows me a phone dialer
[14:28] <saidinesh5> even the UI feels like a phone's
[14:28] <Elleo> saidinesh5: it's a nexus 7 specific image though
[14:28] <saidinesh5> ohh
[14:29] <Elleo> saidinesh5: they have different hardware adaptation, the user stuff is all the same at the moment though
[14:29] <saidinesh5> hmm...
[14:29] <saidinesh5> but why is qemu on desktop failing for me
[14:29] <saidinesh5> http://paste.kde.org/p6szhi6v3
[14:30] <saidinesh5> (which it was unable to locate)
[14:32] <Elleo> saidinesh5: actually, a better option might be to use the ubuntu-emulator
[14:32] <Elleo> saidinesh5: then you'll get an armhf environment
[14:32] <saidinesh5> hmm..... but wouldnt it suffer the same fate as broken packages ?
[14:32] <saidinesh5> like in nexus 7
[14:33] <saidinesh5> also from what i remember about android emulator
[14:33] <Elleo> saidinesh5: I'm hoping it'll work more like the nexus 4 which works fine
[14:33] <saidinesh5> it was really slow
[14:33] <saidinesh5> oh
[14:34]  * saidinesh5 is setting up an emulator
[14:35] <saidinesh5> also Elleo i only have 6GB ram
[14:35] <saidinesh5> => emulator might not be that optimal
[14:35] <saidinesh5> but lets see
[14:35] <ogra_> rickspencer3, your "we cant ship with that" means for final, right ? we shouldnt hold back promotion of the milestone for this ?
[14:36] <rickspencer3> ogra_, well, first of all, I was expressing my opinion, not making a final decision ;)
[14:36] <rickspencer3> and second, yeah, I mean for final
[14:36] <ogra_> rickspencer3, ah, cool then
[14:36] <Elleo> saidinesh5: yeah, it'll almost certainly be quite slow, but no slower than qemu based compilation (basically does the same thing); 6GB of RAM should be fine though
[14:36] <rickspencer3> ogra_, thanks for asking
[14:36] <ogra_> :)
[14:36] <saidinesh5> oh
[14:37] <saidinesh5> Elleo: isnt there some nice cross compiler?
[14:37] <Elleo> saidinesh5: that hits problems with qmake based projects at the moment
[14:38] <saidinesh5> Ah
[14:39] <saidinesh5> the only reason i m still on qmake for this one is simply because it nicely gets all the maliit-defines
[14:39] <saidinesh5> otherwise i dont mind moving to CMake
[14:40] <saidinesh5> well that and better QtCreator support
[14:55] <vesar> Hey what is the current command to flash Bq phone? Something that would be equivalent to what devel-proposed channel for nexus4 used to be. I'm getting mixed info here..
[15:00] <saidinesh5> Elleo: btw. whats the ppa for the fixed ubuntu-sdk?
[15:03] <Elleo> saidinesh5: https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/ppa
[15:03] <Elleo> saidinesh5: haven't tested it though, as I already fixed my chroot for scope dev manually
[15:03] <saidinesh5> ohh
[15:03] <saidinesh5> what exactly was the problem Elleo?
[15:03] <saidinesh5> like is it a simple 1-2 line fix?
[15:04] <Elleo> saidinesh5: yeah, it's just that cmake-extras isn't installed in the chroot by default
[15:04] <saidinesh5> Ahh
[15:04] <Elleo> which is used in the scope template
[15:04] <saidinesh5> let me test it out then
[15:07] <saidinesh5> Ahh there seem to be multiple issues
[15:08] <saidinesh5> weird...
[15:09] <saidinesh5> E: Failed to change to directory ‘<data>/src/’: No such file or directory
[15:10] <saidinesh5> I: The directory does not exist inside the chroot.  Use the --directory option to run the command in a different directory.
[15:10] <saidinesh5> Ahh
[15:10] <saidinesh5> looks like the usual troubles with chroot
[15:12] <saidinesh5> so Elleo i cant chroot into another filesystem that is mounted in /media/ ?
[15:16] <Elleo> saidinesh5: you can mount it into the chroot if needed, e.g. mount -o bind /media/ /path/to/your/chroot/media
[15:16] <Elleo> saidinesh5: then anything in /media/ will be accessible in the chroot
[15:16] <saidinesh5> ohh
[15:16]  * saidinesh5 tries
[15:21] <saidinesh5> Elleo: the problem with chroot is still the same
[15:21] <saidinesh5> broken qt5 packages
[15:22]  * saidinesh5 now checks ubuntu emulator
[15:23] <Elleo> saidinesh5: ah, hang on; are you installing the armhf version of the packages?
[15:23] <saidinesh5> yep
[15:23] <Elleo> saidinesh5: although that said apparently since the chroot doesn't use qemu it probably won't be workable with qmake anyway
[15:24] <saidinesh5> :|
[15:24] <Elleo> the ubuntu-emulator's probably the simplest option if it works
[15:24] <saidinesh5> lets see
[15:24] <saidinesh5> i just booted it up
[15:24] <saidinesh5> its very slow though
[15:25] <saidinesh5> and not sure how i m gonna move files from emulator to pc fast enough
[15:25] <saidinesh5> without resorting to adb push pull etc..
[15:25] <Elleo> well adb push is probably the fastest method
[15:25] <Elleo> maybe making a tar first would be faster
[15:26] <saidinesh5> hmm...
[15:26] <saidinesh5> this sucks
[15:27] <saidinesh5> i locked myself out of the emulator
[15:27] <saidinesh5> and the password i ve entered doesnt seem to be working
[15:27] <ogra_> the emulator hardcodes 0000
[15:27] <saidinesh5> Ahh
[15:27] <saidinesh5> thanks ogra_
[15:33] <saidinesh5> Elleo: libegl1-mesa-dev libegl1-mesa-drivers  libgles2-mesa-dev libllvm3.5 libmirclient-dev libmirclient8driver-mesa
[15:33] <Elleo> saidinesh5: I'd suggest just let the emulator try whatever it likes and see what happens
[15:33] <Elleo> saidinesh5: I'm not sure exactly what it is that causes issues on the nexus 7
[15:33] <saidinesh5> does that look like trouble?
[15:34] <Elleo> saidinesh5: might even be multiboot related if some of the packages install kernel modules in the initramfs
[15:34] <Elleo> saidinesh5: try and find out ;)
[15:34] <saidinesh5> lol
[15:35] <Elleo> at least the emulator can be recreated quicker than reflashing a real device
[15:35] <saidinesh5> nah Elleo definitely not multiboot related
[15:35] <saidinesh5> because the moment i install qt5 packages
[15:35] <saidinesh5> i cant start any program either
[15:35] <saidinesh5> mhm
[15:35] <saidinesh5> trying it out
[15:36] <saidinesh5> oh wait
[15:36] <saidinesh5> nope
[15:36] <saidinesh5> i was wrong
[15:37] <Elleo> oh?
[15:37] <saidinesh5> well the pacges are broken in
[15:37] <saidinesh5> emulator too
[15:37] <Elleo> I'll try setting up an emulator image here and see if I can reproduce it
[15:37] <saidinesh5> The following packages have unmet dependencies:
[15:37] <saidinesh5>  qtbase5-dev : Depends: libqt5gui5 (= 5.3.0+dfsg-2ubuntu9) but it is not going to be installed
[15:38] <saidinesh5> when i do sudo apt-get build-dep ubuntu-keyboard
[15:39] <saidinesh5> The following packages have unmet dependencies:
[15:39] <saidinesh5>  qtbase5-dev : Depends: libqt5gui5 (= 5.3.0+dfsg-2ubuntu9) but it is not going to be installed
[15:40] <saidinesh5> grrrr
[15:40] <Elleo> saidinesh5: creating an emulator image now, will let you know what I find when it's finished downloading
[15:41] <saidinesh5> mhm thanks
[15:43] <popey> pitti: I am told you have some scripts which you developed which make it easy to run click app autopilot tests locally in the same way they run in the lab. Is this true?
[15:43] <ogra_> adt-run :)
[15:44] <ogra_> popey, that will only be true once the lab actually switched to adt-run :)
[15:45] <popey> but is there something I could use today to run ap tests on devices in my hand?
[15:45] <ogra_> popey, https://wiki.ubuntu.com/Touch/Testing ?
[15:46] <popey> yeah, thats what I used to run, balloons said pitti had new shiny ways to run them
[15:46] <ogra_> right, thats atd-run
[15:46] <ogra_> *adt
[15:46] <popey> is that "done" though?
[15:47] <ogra_> the code is, the lab transition isnt ...
[15:47] <popey> so i can run that locally, now?
[15:47] <ogra_> currently the lab runs pablet-test-run all over the place
[15:47] <ogra_> pretty much identical to that wikipage still
[15:47] <balloons> ogra_, right but popey actually wants to have the flashing scripts as well
[15:48] <ogra_> thats just u-d-f
[15:48]  * balloons can't find what he's looking for
[15:48] <ogra_> in the lab
[15:48] <balloons> sure, what branch is it all in again though?
[15:48] <ogra_> and i dont think adt-run will change how we deply
[15:48] <ogra_> no idea
[15:48] <balloons> that's what I'm after.. plars would know
[15:50] <plars> balloons: it's not done with adt at this point, but you are talking about the wrappers we use around flashing the device, setting up network, and running tests?
[15:50] <plars> balloons: that's lp:ubuntu-test-cases/touch
[15:50] <balloons> plars, yes.. bingo, thank you
[15:53] <balloons> plars, so if I wanted to clone what you are doing locally, how would you do it?
[15:54] <plars> balloons: the only other pieces you should need installed are utah (only if you plan to run non-autopilot tests), and phablet-tools/u-d-f/etc
[15:54] <balloons> plars, right, so I can skip utah and otherwise follow the readme?
[15:55] <plars> balloons: the addition of other channels has complicated things slightly, let me know when you are ready to try it and I'll walk you through the basics
[15:55] <balloons> plars, sure. popey also wants to do it
[15:55] <plars> balloons: there are some convenience things you can do, like copy your network profile for your local wireless network to ~/.ubuntu-ci/wifi.conf
[15:55] <balloons> ahh right
[15:56] <plars> balloons: popey: I haven't been through the README in a bit, so it could be out of date. I'll try to get a moment after my standup today to update everything there and have you take it for a spin with a fresh set of eyes to see if I missed anythin
[15:56] <popey> thanks
[15:59] <popey> plars: found a bug ☻
[15:59] <popey> j/k ☻
[15:59] <plars> popey: awesome!
[16:13] <plars> popey: balloons: the RTM results at least appear to have improved considerably with some of the recent landings, need to talk to ogra_ today though about further relaxing the systemsettle threshold and it will be even better I think
[16:14] <plars> popey: balloons: is there a particular thing you're trying to reproduce?
[16:14] <popey> plars: played with it, noticed it flashes vivid on my device because devel-proposed points to that, i have switched it to rtm proposed for me.
[16:14] <ogra_> plars, well, lets have one test run with the relaxed setup before relaxing it fiurther :)
[16:15] <plars> popey: yeah, you can set IMAGE_OPTS before the job to something more sensible - at the moment it doesn't try to keep a sensible list of channels, largely because up until recently that was in flux and included authenticated channel servers and such
[16:15] <popey> yeah, thats what I did ☻
[16:15] <plars> ogra_: it's been running with the relaxed settings since friday
[16:16] <ogra_> plars, you said it landed only after the 140 tests finished when we talked friday
[16:16] <plars> ogra_: hmm, I thought it ran before, but I'll double check, I've slept since then :)
[16:16] <ogra_> (and i think thats actually true)
[16:21] <popey> plars: the provision.sh has a "setting up sudo" section which tries to echo things to /etc/sudoers.d/phablet which fails because the phone is read-only (and I want to keep it that way)...
[16:21] <RalphP> popey: "rtm proposed" - is this now like 14.10 Unity ?
[16:21] <popey> RalphP: que?
[16:22] <popey> RalphP: its one of the channels used on ubuntu phone images.
[16:22] <RalphP> popey: like the old dev-proposed
[16:22] <popey> yeah.
[16:22] <ogra_> RTM is its own derivetive distro
[16:22] <RalphP> ok, thanks.
[16:22] <ogra_> *derivative
[16:24] <pitti> popey: well, the lab still uses phablet-click-run, but yes, you should be able to run them with autopkgtest now
[16:24] <pitti> popey: get http://archive.ubuntu.com/ubuntu/pool/main/a/autopkgtest/autopkgtest_3.7git1_all.deb if you don't run vivid yet
[16:25] <pitti> popey: there's one gotcha though, it currently breaks with a local .click (i. e. adt-run foo.click), you need to manually install it first
[16:25] <popey> hmm
[16:25] <popey> this is getting just as complicated as me writing a shell script to do u-d-f and phablet-test-run ...
[16:27] <pitti> popey: well, it's certainly not easier CLI wise; the main advantage is that it doesn't cheat with making the device r/w and using apt-get install etc.
[16:27] <popey> yeah, i dont plan on doing that
[16:27] <pitti> in fact, once it's ready the plan is to change phablet-test-run to just call the right adt-run rune
[16:27] <popey> i basically just want to flash, set all the wizards and nonsense off, screen on, push/install a click and run tests
[16:28] <pitti> popey: right; the setup script does all that, it's just currently broken to install a local .click; I think I'll have that fixed by tomorrow, but if you want to run it today you need that workaround (or, if you test a pre-instelled click it doesn't matter of course)
[16:28] <popey> well it's also broken provisioning
[16:29] <popey> it tries to fudge entries into /etc/sudoers and fails because it's r/o
[16:29] <ogra_> yeah, not designed for adt-run yet
[16:29] <ogra_> you would need to re-write the sudo bits
[16:29] <ogra_> (all of them)
[16:30] <pitti> eek
[16:31] <popey> pitti: http://paste.ubuntu.com/8805086/
[16:32] <ogra_> pitti, you didnt know that ?
[16:32] <pitti> ogra_: no, I only called p-t-r once or twice (and that was hard enough to get working)
[16:33] <ogra_> pitti, oh, thats not p-t-r
[16:33] <ogra_> pitti, thats the scripts that wrap around all this
[16:33] <pitti> anyway, as I said I'll work on it tomorrow morning
[16:33] <pitti> it's just really hard to keep it working, especially as the emulator keeps being broken
[16:33] <ogra_> seeing popey's paste i actually doubt we need the sudo for the alst command there
[16:33] <plars> popey: ah, right we run in rw mode because there are some app tests that need dependencies at this point. That is something that will be addressed when we move to adt
[16:34] <plars> popey: until then, you need to run in rw mode because of those things unfortunately
[16:34] <popey> plars: how can you.. this is the provision script
[16:34] <popey> or do you provision and not wipe, so it stays r/w forever?
[16:34] <ogra_> popey, thats only the screen unlock
[16:34] <popey> eh
[16:34] <plars> popey: no, we do a full provision each time with bootstrap
[16:34] <ogra_> popey, all other bits for provisioning should work justfine with phablet-config
[16:34] <plars> popey: but it sets rw mode before that point
[16:35] <popey> hang on.
[16:35] <plars> with phablet-config
[16:35] <popey> this is me grabbing the code plars linked to and just running... ./scripts/provision.sh -s 0071ae7610994b1d -n path/to/network/config
[16:35] <ogra_> and phablet-confi has either its own sudo handling (same way adt does it) or a dbuis backend that doesnt require sudo at all
[16:35] <popey> thats all i did
[16:35] <popey> i didn't run anything else, just provision
[16:35] <popey> (as per the readme)
[16:35] <popey> which fails...
[16:36] <plars> popey: in that case, it will fully reprovision the device and set rw mode
[16:36] <popey> "it"?
[16:36] <plars> popey: the provision script - it should reboot to bootloader and install from there
[16:36] <plars> popey: where does it fail?
[16:36] <popey> yes. it did
[16:36] <popey> after that
[16:36] <popey> flashing done, then its setting up the network http://paste.ubuntu.com/8805086/
[16:37] <ogra_> which works fine
[16:37] <ogra_> disabling the wizard too
[16:37] <popey> yes, then it does the sudo stuff
[16:37] <ogra_> right
[16:37] <popey> which is where it barfs
[16:37] <ogra_> which i doubt you actually need nowadays for that dbus call
[16:38] <ogra_> if you do ... we'Re slightly screwed even for adt
[16:38] <ogra_> :P
[16:38] <ogra_> mterry, ^^^^ do you still need sudo for unlocking the greeter ?
[16:38] <pitti> no, we don't
[16:38] <ogra_> (for the accounts service dbus call)
[16:38] <pitti> that bit works just fine
[16:38] <pitti> and it's unity, not accounts-service
[16:39] <ogra_> right, i thought i saw it being fixed a while ago
[16:39] <ogra_> ah, the --dest=org.freedesktop.Accounts was confusing me
[16:39] <ogra_> oh, wait
[16:40] <popey> do i need to file a bug somewhere?
[16:40]  * ogra_ just scrolled sideways in that paste 
[16:40] <ogra_> thats totalyl wrong
[16:40] <ogra_> it should use "phablet-config edges-intro --disable"
[16:40] <ogra_> that isnt the unlocking at all
[16:40] <ogra_> just mocking the phablet-config behavior
[16:40]  * mterry sees ogra's question is answered
[16:40] <ogra_> mterry, yeah
[16:41] <ogra_> plars, why dont we use "phablet-config edges-intro --disable" there ?
[16:41] <pitti> the only reason why adt needs sudo for clicks is to reconfigure apparmor
[16:41] <ogra_> pitti, shouldnt
[16:41] <ogra_> phablet-config handles that too via dbus-property-service
[16:42] <ogra_> if we need to enhance it we should do it there
[16:42] <plars> ogra_: at one time, edges-intro needed authentication so we had to work around it. If that's no longer the case, I can restore that
[16:42] <ogra_> yeah, that should be long fixed
[16:42] <plars> right now, we're just using adb shell "sudo dbus-send --system --print-reply --dest=org.freedesktop.        Accounts /org/freedesktop/Accounts/User32011 org.freedesktop.DBus.Properties.   Set string:com.canonical.unity.AccountsService string:demo-edges variant:       boolean:false"
[16:42] <ogra_> yes, thats what i just noticed
[16:42] <plars> ogra_: ack, I'll replace it - but doing it with sudo works as well
[16:43] <ogra_> plars, not in ro mode :)
[16:43] <plars> popey: appears to be hitting some problem where rw mode did not get enabled properly. I'd be curious to see the earlier bit of the log
[16:43] <ogra_> thanks to dbus-property-service you dont need sudo
[16:43] <plars> ogra_: but as I said before - because we use phablet-test-run, we still need rw
[16:43] <popey> plars: http://paste.ubuntu.com/8805226/ full log
[16:43] <ogra_> i thought pitti's adt-run makes that obsolete
[16:44] <plars> ogra_: it should yes, but we don't use that yet. I had problems in earlier attempts and had an email from him over the weekend saying there were a lot more fixes. Just need to try them still and try to squeeze it into a sprint
[16:44] <ogra_> yeah
[16:44] <ogra_> no hurry :)
[16:45] <plars> if I get a moment today, I'll install the vivid adt-run locally and give it another go
[16:45] <plars> ogra_: trust me, I'd like to get to using it also, it would make my life much simpler I think
[16:46] <plars> but have to be really sure it's not going to break the world for us
[16:48] <plars> popey: I don't see where it set writable image there
[16:48] <popey> plars: me either ☻
[16:49] <plars> popey: ah, you are runnin provision directly, not through run-smoke
[16:49] <plars> popey: use the -w arg also with provision
[16:49] <popey> right, thats what the readme says ☻
[16:49] <plars> popey: it should really be the default now that we know we can't get to r/o without going to adt, but I'm not inclined to change that at the moment
[16:50]  * popey runs that
[16:50] <plars> popey: the README surely needs updating though, and iirc it doesn't really say, just says to use -h to see the options
[16:51] <popey> right, and it doesn't mention run-smoke, which is why i didnt run that..
[16:51] <plars> popey: run-smoke just wraps up the whole process of provisioning and running tests so you don't have to do them as separate steps unless you want to
[16:52] <popey> ok
[16:53] <plars> popey: so if you want it to provision with rtm, and run just the dropping letters tests for example, you could do:
[16:53] <plars> IMAGE_OPT="--bootstrap --developer-mode --channel ubuntu-touch/ubuntu-rtm/14.09-proposed" ./run-smoke -a dropping_letters_app
[16:53] <plars> popey: note: it'll look for your wifi.conf under ~/.ubuntu-ci/wifi.conf
[16:54] <popey> k
[16:54] <plars> popey: if you want to continue running things like that without reinstalling, you can also add -n or --no-provision)
[16:54] <popey> kk
[16:59] <Elleo> saidinesh5: looks like the emulator creates an i386 environment by default now, I get failures when passing armhf as the arch to create
[16:59] <Elleo> saidinesh5: so I guess that's a no-go too :/
[17:01] <popey> gnnnnn 2014/11/03 17:01:12 Cannot push /home/alan/.cache/ubuntuimages/pool/ubuntu-79963ea0bc0a02dfde922d4dfd7a08cea4689fe4028510873fdf9814ae4f4111.tar.xz.asc to device: free space on /cache/recovery is unknown
[17:02] <pitti> sorry, got disconnected; (1) it doesn't work for clicks installed by adt-run, (2) it's way too slow
[17:27] <popey> plars: this run-smoke is doing a load of apt-get stuff....
[17:28] <ogra_> thats why the image needs to be writable ;)
[17:28] <popey> autopilot I see and others
[17:29] <ogra_> yep
[17:29] <plars> popey: yes, depending on the test you run, some have dependencies for the testing
[17:29] <ogra_> thats the stuff that adt-run will actually fix
[17:29] <plars> incidentally, some of them don't seem to work for autopkgtest runs yet, particularly the ones that we still install as debian packages rather than click (webbrowser, unity8, etc)
[17:29] <popey> kk
[17:30] <plars> so many of these will need some work to get parity with what we have today
[17:33] <markuman> I try to install ubuntu on my nexus 4
[17:33] <markuman> https://paste.xinu.at/Gy3e/
[17:34] <ogra_> looks fine
[17:34] <ogra_> (the devel channel is prett old though)
[17:34] <markuman> after rebooting and watching the ubuntu icon sevaral minutes it ask for "ROM may flash stock recovery on boot"
[17:35] <ogra_> it should just auto-reboot after the rotating ubuntu logo
[17:35] <ogra_> it surely does here
[17:35] <markuman> yeah, but it ask my "no" or "yes - disable recovery flash"
[17:36] <ogra_> i think it doesnt matter what you pick there (though you shouldnt even have gotten into recovery at all after it finished the unpacking (the rotating logo))
[17:36] <ogra_> just reboot without going into recovery
[17:37] <ogra_> it should get you into ubuntu
[17:37] <markuman> ok
[17:38] <markuman> ogra_: "Hi, welcome to your ubuntu phone" :)
[17:38] <ogra_> (buit you should really use a different channel ... rtm-proposed or devel-proposed rather than devel)
[17:40] <markuman> ogra_: can i change it inside ubuntu touch or do i have to use adb?
[17:41] <ogra_> you can either use adb (sudo system-image-cli --switch <channel_you_want> -v)  or ubuntu-device-flash again
[17:43] <kenvandine> Laney, i really should have caught that in my review of your branch :)
[17:43] <Laney> yeah me too
[17:44] <kenvandine> just easy to miss a simple line placement thing like that
[17:46] <markuman> ogra_: do i have to activate debugging somehwere again?
[17:46] <ogra_> in system settings
[17:47] <markuman> ogra_: ah ok
[17:47] <ogra_> (developer mode ... under "about this device")
[17:48] <markuman> system-image-cli --switch rpm-proposed -v?
[17:48] <markuman> do i have to reboot into bootloader again?
[17:49] <pitti> plars, popey: if you want to play around, http://people.canonical.com/~pitti/tmp/autopkgtest_3.7git2_all.deb fixes the issue with local clicks (no test case yet, need to reproduce in something like a container first)
[17:49] <ogra_> use --lost-channels for the exact channel notation
[17:49] <ogra_> err
[17:49] <ogra_> --list-channles
[17:49] <dobey> markuman: rtm not rpm
[17:49] <markuman> ok
[17:49] <ogra_> and you need sudo
[17:49] <markuman> got it
[17:49] <ogra_> (with the PIN or password you set in the UI)
[17:49] <dobey> ubuntu-touch/ubuntu-rtm/14.09-proposed is the full channel path/name
[17:50] <markuman> and from bootloader or running ubunt?
[17:50] <pitti> plars, popey: my full command, for reference: adt-run --setup-commands 'mount -o remount,ro /' /tmp/com.ubuntu.calculator_1.3.339_all.click --- ssh -s adb
[17:50] <ogra_> from the adb shell
[17:50] <markuman> yeah but should i do sudo adb reboot bootloader before?
[17:50] <ogra_> no
[17:50] <markuman> ok
[17:50] <ogra_> from the running adb shell
[17:50] <pitti> plars, popey: I always run the setup-commands for safety, as both emulator and dual-boot are r/w by default unfortunately
[17:50] <pitti> (as I don't want to screw up my install with apt-get)
[17:51] <pitti> plars, popey: as usual, if your password isn't "0000", you need to append -- -ps3kr1t
[17:51] <plars> pitti: cool, that was something I was hoping to revisit today anyway, so I'll pull that one
[17:51] <plars> pitti: what was the issue with local clicks? I guess that's something popey was hitting?
[17:52] <pitti> plars:
[17:52] <pitti> adt-run [18:34:55]: Updating AppArmor rules to allow autopilot introspection
[17:52] <pitti> [Errno 2] No such file or directory: '/tmp/com.ubuntu.calculator_1.3.283_all.click'
[17:52] <pitti> adt-run [18:34:57]: ERROR: unexpected error: Failed to update click AppArmor rules
[17:52] <pitti> plars: something like that
[17:52] <popey> plars: sadly after all that my dropping-letters test fails with system idle
[17:52] <pitti> plars: i. e. testbed vs. host .click file path confusion
[17:52] <plars> popey: did it manage to unlock the screen?
[17:52] <popey> yes
[17:53] <popey>   + idle level: 92.425
[17:53] <popey> never got under 91
[17:53] <popey> er, above 92
[17:53] <popey> :D
[17:53] <plars> popey: ah, yes... system idle level has been the topic of much debate lately. We relaxed it a bit, but not enough to hit that level. What were the big offenders?
[17:54] <popey> /system/bin/sensors.qcom
[17:54] <pitti> plars, popey: also uploaded to vivid now FTR
[17:54] <popey> will run some more tests as that was just one run. need more data!
[17:56] <plars> popey: sensors? I don't recall seeing that one before but maybe ogra has spotted it recently with his script that scrapes the big processes in top. Or maybe you were shaking the device and driving the sensors crazy during the run? :)
[17:56] <popey> this is on mako btw
[17:56] <ogra_> plars, nope
[17:56]  * popey leaves it running for a bit
[17:57] <ogra_> plars, i didnt check mako yet ... only krillin
[17:57]  * balloons tries to follow along with the conversation.. I hope you are taking notes popey?>
[17:58] <ogra_> he will just give you the perfectly working code once he is done ;)
[17:58] <ogra_> who needs notes :P
[17:59] <plars> ogra_: popey: usually on mako, it's unity8, unity8-dash, or media-hub-server that kills systemsettle for me
[17:59] <ogra_> yeah
[17:59] <ogra_> thats the common meme
[17:59] <dobey> wtf
[17:59] <ogra_> and something tvoss is currently working on
[17:59] <dobey> i just filed a bug against lp:clock-app
[17:59] <plars> https://jenkins.qa.ubuntu.com/job/utopic-touch_stable-mako-smoke-daily/395/artifact/clientlogs/unity8/topafter.log/*view*/ is a good recent example from rtm/mako
[17:59] <dobey> but clock-app does not appear in the "Affects" list on lp
[18:00] <nik90> dobey: its ubuntu-clock-app
[18:00] <ogra_> plars, the prob is that these processes go wild even if you kill unity8 (not only if it crashes unconditionally)
[18:00] <dobey> nik90: what the heck is clock-app then?
[18:00] <nik90> dobey: god knows..I think it is a old project name that was supposed to be removed
[18:01] <dobey> oh it's inactive
[18:01] <dobey> why did launchpad even let me file a bug
[18:01] <dobey> weird
[18:02] <dobey> great, and i can't remove the bad project from the bug, via the web
[18:02] <nik90> dobey: can you give me the bug link
[18:02] <dobey> and iirc, i can't "no longer affects" a bug from the API
[18:02] <dobey> whee
[18:02] <dobey> nik90: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1388931
[18:03] <nik90> dobey: thnx, I will comment there for more visibility
[18:12] <om26er> mterry, Hi!
[18:13] <om26er> mterry, re: https://code.launchpad.net/~mterry/ubuntu-system-settings/passphrase-continue-rtm/+merge/240271 there is a mention of 4 fixes in the commit message, but only two of the mentioned issues are fixed.
[18:13] <om26er> I see the string change was reverted, so basically only the 4th mentioned issue there is not fixed.
[18:16] <om26er> kenvandine, perhaps you could help me with that ? ^
[18:16] <om26er> its ubuntu-rtm/landing-013
[18:22] <popey> plars: hmm.. doing second flash.. it's been sat at this for 20 mins... 2014/11/03 17:58:07 Done pushing /home/alan/.cache/ubuntuimages/pool/device-b3355af0ca59fde927537eea2d77e5d5452061bc55dac8456ff2c0eecff63faf.tar.xz to device
[18:22] <popey> need to go out, will check again when I get back
[18:24] <plars> popey: what does your device seen to be doing? That seems to just be stuck in udf
[18:24] <popey> was sat in recovery mode
[18:24] <plars> Sounds like UDF failed
[18:25]  * popey kicks it off again and goes out
[18:25] <ogra_> sounds like it didnt go to bootloader
[18:25] <markuman> is it possible to close programms in ubuntu touch?
[18:26] <chrisc> swipe them away
[18:26] <dobey> markuman: when not in foreground, they are stopped. swiping from right edge to get app overview, and then swiping up on an app will kill it
[18:26] <chrisc> drag the screen from the right edge and then swipe the ones you want to close
[18:27] <markuman> k thx
[18:27] <markuman> can i import carddav contacts?
[18:28] <ogra_> only google contacts atm i think
[18:28] <popey> ok, now I'm massively confused.
[18:28] <popey> $ IMAGE_OPT="--bootstrap --developer-mode --channel ubuntu-touch/ubuntu-rtm/14.09-proposed" ./scripts/run-smoke -a dropping_letters_app
[18:28] <popey> whats wrong with that?
[18:29] <popey> run-smoke is complaining that I haven't specified -s as it's required
[18:29] <ogra_> passwd ;)
[18:30] <popey> $ IMAGE_OPT="--bootstrap --developer-mode --channel ubuntu-touch/ubuntu-rtm/14.09-proposed" ./scripts/run-smoke -a dropping_letters_app
[18:30] <popey> thats the command I previously ran
[18:30] <popey> identical
[18:30] <popey> it previously ran (albeit with system settle issues) - now it complains that -s isnt set.. me no understand
[18:32] <popey> aha! no device showing up, thats why
[18:32] <ogra_> just set -s
[18:32] <ogra_> :P
[18:32] <plars> popey: either you plugged in another device or the one you have is not visible to adb
[18:32] <popey> didnt have to last time.
[18:32] <popey> will forcibly set -s this time
[18:32] <popey> thanks
[18:33] <ogra_> note that the emulator is also a device for adb ;)
[18:33] <mhall119> jdstrand: taking your advice and flashing to r118
[18:33] <plars> Indeed
[18:36] <popey> ok, its stuck again i think. sat doing nothing after 2014/11/03 18:34:33 Done pushing /home/alan/.cache/ubuntuimages/pool/custom-761e8a93754d4170fc8f1d4dad38567fb260cca55a8f42141d2da6c682ac43bf.tar.xz to device
[18:36] <popey> its in recovery now.
[18:37] <markuman> how can i add programms to the left panel?
[18:38] <jdstrand> mhall119: cool. it isn't a flawless experience, but it has so far been much better than promoted 5. oh. I should mentioned I also installed oxide and webbrowser-app from http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtm&q=landing-015 because it has fixes for big oxide memleaks. that said, fair warning, those are going to be the packages that land in rtm (the PM team said that they wanted a backported fix to 1.2 due to
[18:38] <ogra_> markuman, open them from the apps scope ... if they run, tap and hold the icon
[18:38] <jdstrand> mhall119: those aren't*
[18:38] <ogra_> markuman, in the left panel i mean :)
[18:38] <kenvandine> om26er, which isn't fixed?
[18:39] <markuman> ogra_: k thx
[18:39] <mhall119> jdstrand: really as long as ofono doesn't have to be restarted and the dash is a little more stable, I'll be happy
[18:40] <mhall119> I've been living with oxide memory hunger for a while
[18:40] <jdstrand> mhall119: yeah, that ofono issue was annoying. it seems to be fixed. the dash may be affected by the oxide memleak, so if it isn't better, try the silo
[18:40] <ogra_> jdstrand, mhall119 wait 10min and there will be a promoted #6
[18:40] <mhall119> ogra_: now you tell me :(
[18:40] <ogra_> (just running the promotion scripts here)
[18:40] <OrokuSaki> hi! nobody seems to know so I am asking you guys.. anyone have problems with gnome-fallback on trusty with armhf? I upgraded my distro from raring to trusty, and gnome-fallback won't work... and the onboard keyboard is just a black rectangle.. even with fbdev xorg driver... or freedreno which is working. I moved to unicorn.. same problem..
[18:40] <mhall119> it's already rebooting into 118
[18:40] <ogra_> watching #ubuntu-ci-eng helps ;)
[18:41] <OrokuSaki> I noticed somehow I seem to have some ubuntu touch packages accessible or perhaps that is what apt-get thinks I am on.. ubuntu touch? since I am trusty and armhm?
[18:41] <kenvandine> om26er, they all look fixed to me
[18:42] <OrokuSaki> Is that possible ogra? Upgrading from 13.04 raring armhf to 14.04 trusty or 14.10 would give me graphic stuff meant for touch instead of desktop?
[18:42] <mhall119> ogra_: but balloons will make me write tests if I'm in there
[18:42] <ogra_> no
[18:42] <ogra_> mhall119, perfect !!! come over !!!!
[18:42] <OrokuSaki> I had a 13.04 desktop with freedreno... and I am upgrading with a 3.4 kernel (since I can't run ubuntu touch with cm11 sources and I get bored)
[18:42] <balloons> :p
[18:43] <om26er> kenvandine, When pressing Back on the Wi-Fi screen, go to "Lock security" page instead of the "Choose a password" page.
[18:43] <OrokuSaki> Works great with Fedora 21 and gnome 3.14 or kde.. but no go with Ubuntu even trying gnome-fallback
[18:43] <OrokuSaki> I get some LibGL error I think
[18:43] <OrokuSaki> At work. (rofl)
[18:43] <om26er> that is not fixed. neither is "Fix phrasing of "4 numbers" to "4 digits only"" fixed, but that was reverted I can see in a commit.
[18:43] <om26er> kenvandine, which image did you test on ? I am testing on 140 on krillin.
[18:43] <kenvandine> the string revert was planned
[18:43] <ogra_> OrokuSaki, there is no way any ubuntu-touch stuff would be installed by ubuntu-desktop ... but since 13.04 nobody has done anything for -desktop on armhf
[18:44] <ogra_> OrokuSaki, so it could be broken as hell, no idea
[18:44] <mhall119> oh, we have a rotation lock indicator now
[18:44] <OrokuSaki> onboard keyboard is just a black rectangle..with unity greeter.. and after that.. background with no panels.. compiz I don't expect to work.. but I think old gnome would
[18:44] <kenvandine> i tested on 139
[18:44] <kenvandine> krillin
[18:44] <OrokuSaki> I think it is broken as hell. =)
[18:44] <OrokuSaki> Mess with it later.. give me something to do
[18:44] <kenvandine> om26er, i just tested it again on mako, but from the vivid build
[18:44]  * kenvandine tries again on rtm/krillin
[18:44] <ogra_> OrokuSaki, you definitely will need binary drivers that fully support EGL for unity7 to work
[18:44] <OrokuSaki> I read x86 people without 3d acceleration have this problem
[18:45] <OrokuSaki> Yeah but I am not trying unity... just gnome-fallback.. not even gdm-greeter seems to like me
[18:45] <OrokuSaki> unity-greeter works great.. except for onboard keyboard
[18:45] <kenvandine> om26er, oh... you're right!
[18:45] <ogra_> yeah, no idea, i dont touch -desktop on arm anymore
[18:45] <kenvandine> i wonder if something got lost there in the backport
[18:45] <OrokuSaki> I usually use unity greeter to go to gnome-fallback\flashback stuff
[18:46] <OrokuSaki> Vivid seems to be getting freedreno support with mesa.. which is cool.
[18:46] <OrokuSaki> Thought I would let ya guys know though.. arm desktop 14.04 has graphic issues... which.. I wish ubuntu would do more desktop releases for arm... =)
[18:47] <OrokuSaki> 13.04 was the last.. then you gotta dist-upgrade etc
[18:47] <ogra_> feel free to contribute ...
[18:47] <OrokuSaki> nod
[18:47] <ogra_> patches wont be rejected
[18:47] <ogra_> (got to #ubuntu-desktop though)
[18:47] <OrokuSaki> there is a ppa a guy seems to have fixed stuff for x86.. will give him a shout see what he recompiled etc
[18:50] <OrokuSaki> Can't wait for the cm11 version again... =( Saki out!
[18:51] <kenvandine> mterry, i think something got hosed in your backport branch
[18:51] <kenvandine> +                pageStack.load(Qt.resolvedUrl("passwd-set.qml"))
[18:52] <kenvandine> i think that should be 31-passwd-set.qml
[18:53] <kenvandine> mterry, or rename the file
[18:53] <kenvandine> mterry, which would probably be better
[18:53]  * mhall119 flashes again to RTM #6
[18:53] <mhall119> thanks ogra_
[18:54] <ogra_> :)
[18:54] <mhall119> ogra_: is this based on -proposed #118?
[18:54] <ogra_> yes
[18:54] <ogra_> its the same
[18:54] <markuman> is it possible to remove the video and the music dashboard?
[18:55] <om26er> kenvandine, since you marked that branch as 'Needs fixing' I can stop testing the silo now ?
[18:55] <mhall119> markuman: from the phone dash or the desktop dash?
[18:55] <ogra_> markuman, there is a little star in the top right corner
[18:55] <ogra_> indicating they are selected favorites
[18:55] <markuman> mhall119: phone dash
[18:55] <mhall119> markuman: as ogra_ said, un-select the start in the top-right corner to remove it from the dash
[18:55] <kenvandine> om26er, yes, for now
[18:55] <mhall119> s/start/star/
[18:56] <markuman> ogra_: thx
[18:56] <kenvandine> om26er, we need mterry to fix that
[18:56] <ogra_> if you want them back, swipe from the bottom
[18:56] <kenvandine> om26er, sorry about that
[18:56] <ogra_> there you can select scopes
[18:56] <mhall119> you can add all kinds of other scopes that way too ^^
[18:56] <om26er> kenvandine, ok, no problem :)
[18:56] <gcollura> can anyone review my MR? https://code.launchpad.net/~gcollura/content-hub/fix-1384490/+merge/240156
[18:56] <markuman> ogra_: got it. thx
[18:57] <popey> bfiller: do you have someone who can review the above branch? maybe kenvandine or Elleo ?
[18:57] <kenvandine> Elleo, can you look at that?
[18:57] <Elleo> popey, gcollura: if you don't mind waiting until tomorrow I'd be happy to review it
[18:57] <Elleo> heading out for the evening now :)
[18:57] <kenvandine> Elleo, i know you were looking at fixing that already right?
[18:58] <Elleo> kenvandine: it was on my list of things to fix, I hadn't done anything towards it yet though, so it's great to have an MR contributed :)
[18:58] <gcollura> Elleo, thank you no problem, I'm patient :)
[18:58] <kenvandine> Elleo, thanks, i'd prefer you look at that one:)
[18:58] <kenvandine> gcollura, thanks for the branch!
[18:58] <gcollura> kenvandine, you're welcome :)
[18:59] <mhall119> kenvandine: is the content hub move bug #1373086 fixed in RTM #6?
[18:59] <kenvandine> mterry, confirmed, it's failing to load passwd-set.qml because the backport didn't include the rename of the file
[18:59] <mhall119> gcollura: thanks for the MR!
[18:59] <markuman> how to can i make a screenshot?
[19:00] <markuman> is there a wiki/faq for all those questions?
[19:00] <om26er> kenvandine, should I mark the silo as failed ?
[19:00] <kenvandine> mhall119, yes
[19:00] <mhall119> kenvandine: \o/ now my MemeBook app will be useful :)
[19:00] <kenvandine> om26er, that's fine... will it show back up on your radar when i make the silo as passed again?
[19:00] <kenvandine> tested that is
[19:01] <om26er> kenvandine, yes, it will.
[19:01] <mhall119> hmmm, storage reporting in r6 is strange
[19:01] <kenvandine> mhall119, on mako?
[19:01] <mhall119> yeah
[19:02] <kenvandine> storage reporting on mako is terrible
[19:02] <gcollura> markuman, do you want to take screeshots on the device?
[19:02] <kenvandine> because of the way the mounts work
[19:02] <kenvandine> not sure what we can do about it
[19:02] <mhall119> says I have only 2.1GB storage and Ubuntu uses 0 bytes
[19:02] <markuman> gcollura: yes
[19:02] <kenvandine> i sent a plea to the ubuntu-phone list for advice... and no replies
[19:02] <kenvandine> it's because of the loop mounts and stuff
[19:02] <gcollura> markuman, you need to install phablet-tools and run the command: phablet-screenshot filename.png
[19:02] <mhall119> kenvandine: yeah, it's pretty hairy
[19:02] <kenvandine> mhall119, so for now that is a mako only issue...
[19:03] <kenvandine> other devices won't do that
[19:03] <mhall119> not even the other Nexus devices?
[19:03] <kenvandine> not sure...
[19:03] <kenvandine> i still don't understand why we do that on mako
[19:03] <kenvandine> i don't really want to understand either that part of the stack :)
[19:03] <mhall119> evolution I think, probably dates back to the pre-flipped days
[19:05] <popey> baaaaah 2014/11/03 19:05:11 Cannot push /home/alan/.cache/ubuntuimages/pool/ubuntu-79963ea0bc0a02dfde922d4dfd7a08cea4689fe4028510873fdf9814ae4f4111.tar.xz.asc to device: free space on /cache/recovery is unknown
[19:06]  * popey starts again
[19:20] <n3tJ4ckr> Does anyone know if there is a rtm changelog?
[19:22] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/rtm/
[19:23] <n3tJ4ckr> thanks ogra
[19:37] <popey> plars: well I'm confused, it flat out wont flash now
[19:37] <popey> sits there in recovery forever
[19:37] <plars> popey: show me the command line you're running?
[19:38] <popey> http://paste.ubuntu.com/8807302/
[19:43] <plars> popey: so it's rebooting to the bootloader, and running ubuntu-device-flash, but never makes it out of ubuntu-device-flash? Does UDF complain at any point? (I'm guessing no, it has a nasty habit of failing without much information on why)
[19:43] <plars> popey: also, have pastebin of the output?
[19:43] <plars> I'll try it locally also, but my mako has no battery so I can only try krillin
[19:43] <mterry> kenvandine, omg so sorry
[19:44] <mterry> kenvandine, was out for lunch/gym
[19:44] <popey> plars: it ends up in recovery for ages then falls over
[19:44] <popey> plars: http://paste.ubuntu.com/8807373/ thats the output of the most recent run, right now its sat in recovery
[19:45] <kenvandine> mterry, the joys of cherry picking :)
[19:46] <plars> popey: 118 ran just fine in the lab, not sure why it would fail locally. I'm guessing somethings off with your mako? You could try to run udf by hand, but as you can see from the command line it runs, there's nothing special about it
[19:46] <mterry> kenvandine, yeah that was dumb.  Should have tested fresh cherry picked branch, but probably had left-over file from other branch
[19:46] <mterry> in my /usr/share
[19:46] <popey> plars: why is it doing --bootstrap?
[19:47] <popey> surely that's not necessary
[19:47] <mterry> kenvandine, pushed rename to bzr but let me test everything on my phone for realz
[19:47] <plars> popey: we always install from bootloader - that was the recommendation from the phonedations team
[19:47] <popey> ok
[19:47]  * mterry flashes
[19:47]  * popey averts his eyes
[19:47] <mterry> :)
[19:52] <stgraber> slangasek: first pass at some documentation, should finish filling in the blanks later today: https://wiki.ubuntu.com/ImageBasedUpgrades/ServerOperation
[20:00] <kenvandine> mterry, om26er_: i'm rebuilding silo 13 with the fix
[20:02] <davmor2> mterry: shame on you, code of conduct and all that, now you have upset poor popey 's sense of humour and he is being funny again, I hope you're happy with yourself,  I know I was thanks for giggle popey :)
[20:03] <mterry> davmor2, hah
[20:08] <mterry> kenvandine, new branch seems to work fine on my krillin
[20:08] <mterry> kenvandine, made sure to clean out /usr/share/ubuntu/settings/wizard/qml/Pages first
[20:08] <kenvandine> mterry, great, thanks
[20:13] <slangasek> stgraber: excellent!  Thanks :)
[20:21] <sergiusens> popey: plars installing from using bootstrap ensures recovery uses the latest kernel and recovery
[20:21] <popey> ok. I can't fathom why this install hangs when run from the test scripts
[20:22]  * popey wipes
[20:23] <sergiusens> popey: from the pastebin, I can't either
[20:23] <popey> trying a wipe and start fresh
[20:24] <popey> dunno if it's relavent but it's a 16GB mako, not an 8GB one...
[20:24] <sergiusens> popey: bootstrap does a wipe already
[20:25] <sergiusens> popey: I would like to see 'dmesg' and the recovery logs when it hangs though
[20:29] <popey> sergiusens: well thats odd, i did a clean flash and it remembered my passphrase
[20:29] <popey> oh, i didnt bootstrap that time.
[20:29] <taiebot> Hi all any update on this bug. https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1323837 going this week end abroad and ll have to find an extra phone to put my sim card in roaming mode. I know its not priority but would like to see a time frame or a possible hack as it is quite inconvenient when i am abroad.
[20:36] <dobey> taiebot: do you not see any of that if you open the phone app and tap the settings gear icon?
[20:39] <taiebot> dobey: no simtoolkit is really missing from UT  http://support.vodafone.com.au/articles/FAQ/SIM-Toolkit so i can not access the sim card where i can select roaming mode. I really think i should change provider but UT should still provide this as there might be other providers doing this. I have also read about banks using sim toolkit in Asia.
[20:46] <popey> chrisccoulson: visiting player.fm on my phone is this expected? http://popey.mooo.com/screenshots/device-2014-11-03-204537.png
[20:47] <popey> ahayzen_: http://linux.softpedia.com/blog/Ubuntu-Touch-to-Feature-a-Beautiful-Music-App-463931.shtml
[20:50] <chrisccoulson> popey, looks like a webbrowser-app bug - the error is definitely valid, but it looks like it's for a subresource network connection. The browser should just ignore those because there isn't a sane way to display them (and we don't allow you to override them in oxide anyway)
[20:50] <chrisccoulson> chrome and firefox just ignore these silently
[20:50] <popey> ok, will file a bug
[20:51] <popey> ta
[20:51] <chrisccoulson> in fact, I though I'd already reported this
[20:51] <chrisccoulson> one second
[20:51] <popey> ok
[20:51] <dobey> taiebot: i don't know what vodafone's sim toolkit is. if i open the phone settings, i can change sim settings like call forwarding, call waiting, and access provider-specific numbers stored on the SIM
[20:52] <chrisccoulson> popey, bug 1377194 - the first point is related to this
[20:53] <ahayzen_> popey, blimey!
[20:54] <dobey> popey: it's really fun for webapps with no chrome. how do you even know the site is secure, when it does work? :)
[20:57] <popey> thanks chrisccoulson
[20:57] <kenvandine> om26er_, i've confirmed mterry's fix in silo 13
[20:57] <mterry> w00t
[20:59] <om26er_> kenvandine, heh, me too! I was in the process of testing the wizard
[20:59] <kenvandine> thx
[21:00] <taiebot> dobey: yes but the STK is missing. i am just hoping it will not be a forgotten bug as I think this is a must have for any phone. This used to be how you could save contacts on your simcard on an old nokia phone also you could save texts on your simcard. I would ask the CAG if they really are planning to keep  using the sim toolkit  Most of them are certainly not using it anymore they prefer using  proper apps.
[21:04] <dobey> taiebot: that seems like something that the carrier adds to their phoens. on an old nokia phone, all my contacts and sms were stored on the sim.
[21:07] <taiebot> dobey: so you think it will be the carrier duty to install this on UT? I would have thought the first phones would be sim free phone ( not attached to any carrier).
[21:07] <sergiusens> taiebot: dobey stk also requires implementation/integration in ofono and higher
[21:08] <sergiusens> but I don't think stk is something we are going to focus on
[21:08] <taiebot> sergiusens: will it ever be implemented ? or this is old technology that UT would not support
[21:09] <sergiusens> taiebot: I can't answer that as I don't know; maybe if you write the code; stuff can happen ;-)
[21:10] <taiebot> sergiusens, dobey: It would be good to know as it is a watch-out for consumer. I am the first one to report such a bug but who knows if UT gain into popularity.
[21:11] <sergiusens> taiebot: more than a bug it's just a missing feature which is not on the roadmap that I know of
[21:13] <taiebot> sergiusens: i am pushing to put this on the roadmap :-D
[21:14] <dobey> hmm
[21:14] <dobey> well, my webos phone just says "no sim services available" when i open the sim toolkit app on it, with my sim installed
[21:14] <sergiusens> dobey: well, the carrier does indeed need to install something onto the sim for it to work as well ;-)
[21:15] <dobey> sergiusens: yes, of course, but if there's nothing there, it's hard for me to test what's supposed to be there :)
[21:19] <dobey> i'll see if a really old att sim has anything on it
[21:23] <dobey> nothing there either apparently. did get a "SIM not provisioned" message though. but nothing in sim toolkit app
[21:24] <taiebot> dobey: it might be very carrier and country dependant
[21:24] <taiebot> Here a review in africa of google sim toolkit http://blog.nyaruka.com/androids-achilles-heal-the-sim-toolkit
[21:25] <dobey> taiebot: it's an att branded hp pre3, for the us market.
[21:29] <taiebot> dobey, serguisens: will put this  article on my bug might get some more love like this http://blog.nyaruka.com/androids-achilles-heal-the-sim-toolkit
[21:29] <popey> sergiusens: while my phone is sat in recovery mode I can't get in via adb shell to get dmesg logs!
[21:30] <sergiusens> popey: hah, well at least it's not a u-d-f issue
[21:30] <sergiusens> popey: what does adb devices say?
[21:31] <popey> 0071ae7610994b1d        recovery
[21:31] <popey> adb shell just hangs there
[21:31] <sergiusens> popey: what if you adb kill-server; sudo adb start-server; adb shell ?
[21:32] <popey> udf crapped out
[21:32] <popey> and i get a shell prompt on the device
[21:32] <sergiusens> popey: yeah; is this a new install?
[21:32] <sergiusens> popey: you can try udf again now that adb is running as root on your host
[21:32] <popey> hang on
[21:32] <popey> about an hour ago I did udf just fine
[21:33] <sergiusens> oh
[21:33] <popey> now running it with --bootstrap its failing
[21:33] <popey> + ubuntu-device-flash --password ubuntuci --bootstrap --developer-mode --channel ubuntu-touch/ubuntu-rtm/14.09-proposed
[21:33] <sergiusens> popey: from recovery?
[21:33] <popey> thats the command line
[21:33] <sergiusens> ack
[21:34] <popey> well the script puts it into bootloader and then runs udf
[21:34] <popey> frustrating because I can flash it fine without --bootstrap
[21:35] <popey> http://paste.ubuntu.com/8808538/ is the dmesg from recovery mode
[21:38] <sergiusens> popey: these sent uevent USB_STATE=CONNECTED only happen if you physically disconnect the cable or if usb on your host has gone bonkers; are you on a usb hub?
[21:38] <sergiusens> can you reset it?
[21:38] <popey> no
[21:38] <popey> its the port on my laptop
[21:39] <sergiusens> popey: how about changing the port?
[21:39] <popey> ok
[21:39]  * popey starts again
[21:40] <popey> thanks for the help
[21:58] <dobey> where are logs stored for mms failures?
[22:04] <thomi> slangasek: Does the Foundations team look after bootchart?
[22:09] <slangasek> thomi: in a pinch...
[22:14] <thomi> slangasek: we're trying to work on the bootspeed tests (desktop and touch), but there are two bootchart bugs that are blocking us
[22:14] <slangasek> bug #s?
[22:14] <thomi> slangasek: https://bugs.launchpad.net/ubuntu/+source/bootchart/+bug/1381177 and https://bugs.launchpad.net/ubuntu/+source/bootchart/+bug/1384450
[22:15] <thomi> We're sprinting on these tests this week and next, and these bugs are blocking our progress on the bootchart side of things
[22:15] <slangasek> ah.  yes, the package assumes that it can integrate with the kernel/initramfs hooks
[22:16] <slangasek> ogra_, rsalveti: ^^ have you solved this problem for other packages with initramfs hooks?
[22:17] <rsalveti> I think it works for mako but not yet for krillin
[22:17] <slangasek> oh?
[22:17] <rsalveti> we might have a barajas bug for krillin
[22:18] <rsalveti> I don't think modules are fully working yet for krillin
[22:18] <rsalveti> and there is also no kernel package
[22:18] <slangasek> right
[22:18] <rsalveti> complained about that many times already
[22:18] <slangasek> but the initramfs isn't managed by kernel packaging even if it exists
[22:18] <rsalveti> no, just makes the modules part a bit easier
[22:19] <rsalveti> we'd need modules in there and also the proper hooks for flash-kernel to update the boot img
[22:19] <rsalveti> or similar
[22:20] <brendand> barry, can the phased updates test only be run on mako? https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-system-image
[22:20] <thomi> rsalveti: slangasek: so... whose plate does that work fall on?
[22:20] <rsalveti> thomi: us (ogra) and barajas
[22:21] <barry> brendand: well, you can run it on krillin if you fake the device.  that's because the only place we actually have a deployed phased update is on stgraber's staging server
[22:21] <barry> brendand: that's why you want to use --dry-run
[22:21] <brendand> barry, ah yeah i see you can pass the device to system-image-cli
[22:21] <thomi> rsalveti: Should I talk to ogra to get an ETA on a fix, or run this up through the management escalation chain?
[22:22] <barry> brendand: yep
[22:22] <rsalveti> thomi: please ping ogra_ first, I can discuss this tomorrow morning with him
[22:22] <brendand> barry, so there's no risk that it won't just not work on krillin later?
[22:22] <rsalveti> and see what is missing for it
[22:22] <thomi> rsalveti: will do - I guess it's past his EOD, so I'll email.
[22:22] <rsalveti> adding management will not help much at this point
[22:22] <rsalveti> thomi: yup
[22:22] <thomi> slangasek: what about the first bug? That would seemm to be in your camp a bit more?
[22:23] <thomi> rsalveti: thansk
[22:23] <barry> brendand: the risk due to this change should be low, since it has nothing to do with the device.  it was just a convenient channel/device for stgraber to set up the test on.  it's really the index.json file that has all the goodness
[22:23] <rsalveti> slangasek: are we still doing binary sync from vivid into rtm or just src copy instead?
[22:33] <ogra_> thomi, ETA -> tomorrow EU evening ...
[22:33] <ogra_> sorry, that slipped through :(
[22:37] <thomi> ogra_: oh, you're still around - thanks!
[22:37] <slangasek> rsalveti: vivid->rtm should be source copy only (with a differing version number)
[22:38] <slangasek> thomi: the first bug looks like it's ours, yes
[22:38] <rsalveti> slangasek: do we need to add rtm in the version string?
[22:38] <rsalveti> slangasek: even if something already landed in vivid?
[22:39] <thomi> slangasek: are you able to suggest an ETA for that bugfix please?
[22:39] <slangasek> rsalveti: it's important that there be a unique version number for each upload, but Launchpad won't enforce this for you; the easiest way to ensure this is to always add rtm in the version string, but if you're sure you're using an unclaimed version number, then ok
[22:40] <slangasek> barry: would you have some time today to look at bug #1381177? it's a critical issue for thomi
[22:40] <rsalveti> right
[22:40] <barry> slangasek: yep, i can look
[22:41] <thomi> yay! I get to hassle barry some more :D
[22:41] <slangasek> barry: cheers
[22:44] <barry> thomi any chance you have a bootchart.tgz that triggers the bug?
[22:45] <thomi> barry: I asked Max (nuclearbob) to join us, he should be able to get it
[22:46] <ogra_> slangasek, fyi. export FLASH_KERNEL_SKIP=true
[22:46] <slangasek> ok
[22:46] <ogra_> in cease you ever need it
[22:47] <ogra_> *case
[22:47] <slangasek> of course, any of these workarounds will still not give you bootchart support in the initramfs on the phone
[22:47] <ogra_> we dont have proper initramfs support on krillin
[22:47] <ogra_> or rather proper update support for it
[22:48] <slangasek> nor on mako, AFAIK?
[22:48] <ogra_> (and i have never seen the initramfs side work on arm anyway, so this is moot until someone researches and finds out why there is no data collected)
[22:49] <slangasek> hmm
[22:49] <ogra_> mako updates fine
[22:49] <ogra_> all supported arches that we proted work
[22:49] <ogra_> *ported
[22:51] <ogra_> (anyway, i'm not really here ... will try to find a way to inject the var tomorrow for now)
[22:51] <ogra_> (and no idea about the index error, it works just fine here)
[22:51] <ogra_> (but will try to repro)
[22:58] <saidinesh5> Elleo: oh .... so any other nice plans?
[22:58] <saidinesh5> i started migration to cmake though
[22:59] <Elleo> saidinesh5: buy a nexus 4? :P
[22:59] <saidinesh5> nah.. not during a job hunt :P
[22:59] <Elleo> saidinesh5: afraid I'm out of other suggestions, switching to cmake's probably the most sensible joice
[22:59] <Elleo> choice*
[22:59] <saidinesh5> mhm... just last week i refactored the whole thing to a sensible way using qmake lol
[23:00] <Elleo> heh
[23:00] <saidinesh5> i wanted to try out cmake but then thought more important things first
[23:00] <saidinesh5> so did it with qmake
[23:00] <saidinesh5> qmake can be quite annoying though
[23:00] <saidinesh5> oh btw Elleo did i show you how it looks like?
[23:00] <Elleo> saidinesh5: nope?
[23:01] <saidinesh5> https://www.youtube.com/watch?v=3zgKIa4Baf0
[23:02] <Elleo> saidinesh5: nice, looks very swish :)
[23:02] <saidinesh5> heh swish?
[23:02] <Elleo> ~fancy
[23:02] <saidinesh5> that flash animation program?
[23:02] <saidinesh5> Aahhh
[23:02] <Marzel> Good evening!
[23:03] <saidinesh5> yeah i actually was wondering about a cleaner way to represent which key has been pressed, so used the glowing light thing
[23:03] <saidinesh5> evening Marzel
[23:03] <Elleo> saidinesh5: yeah, looks good :)
[23:04] <saidinesh5> also  i was working to make it eat directly from android dictionaries right now
[23:04] <Marzel> I 've tried to change my channel to devel-purposed. But if I run ubuntu-device-flash, I always get "error status 255". What does this mean?
[23:04] <saidinesh5> well after cmake porting i guesss
[23:04] <saidinesh5> was hoping there would be some dirty trick to reuse presage or something like that to get all the prediction etc.
[23:04] <saidinesh5> but i think i ll have to write it myself
[23:05] <Elleo> saidinesh5: presage might be usable for prediction, it's not great for swype style correction though, since it doesn't take any spatial information into account
[23:06] <Elleo> although I'm planning on writing a prediction module for it to do some spatial stuff when I have time
[23:06] <saidinesh5> mhm..  1 step at a time for me
[23:06] <saidinesh5> oh?
[23:06] <saidinesh5> like?
[23:06] <Elleo> just basic stuff, so it can take account of nearby keys in its predictions
[23:06] <saidinesh5> currently i m just modifying levenstein's distance algorithm
[23:07] <Elleo> e.g. at the moment "thr" predicts "through", whereas if you take spatial key positions into account its more likely to be "the"
[23:07] <saidinesh5> to account for nearby keys  etc...
[23:07] <saidinesh5> Ah
[23:07] <saidinesh5> thats not that hard to hack i imagine
[23:07] <saidinesh5> that's hwo i started too
[23:08] <Elleo> nah, shouldn't be; the main thing will be fiddling out the best weightings vs the rest of the prediction model
[23:08] <saidinesh5> yeah indeed
[23:08] <saidinesh5> thats what irks me too
[23:08] <saidinesh5> but i realized i would need Unit tests etc..
[23:08] <saidinesh5> to test them all
[23:08] <saidinesh5> thats how the current plan is to get a half decent maliit plugin
[23:08] <saidinesh5> and collect lots of unit tests
[23:08] <Elleo> saidinesh5: is skeyer open source?
[23:09] <saidinesh5> collect/make
[23:09] <Marzel> I 've tried to change my channel to devel-purposed. But if I run ubuntu-device-flash, I always get "error status 255". What does this mean? Anybody an idea? saidinesh5? :)
[23:09] <saidinesh5> Elleo: it is intended to be. just didnt open it up yet cuz i wanted to have something substantial
[23:09] <Elleo> saidinesh5: cool, well when you do let me know; I'll happily help hack on it :)
[23:09] <saidinesh5> so far that involves 1 hard disk crash, lots of wasted time on maliit :P
[23:10] <saidinesh5> Ah sure .. :)
[23:15] <saidinesh5> Marzel: i m not sure about your problem though
[23:18] <Marzel> saidinesh5: Hm...Google couldn't tell me something more. And I don't have any idea, where the problem could come from...
[23:19] <saidinesh5> Marzel: why not directly use fastboot to flash things?
[23:19] <saidinesh5> adb and fastboot to flash the images
[23:19] <Marzel> How to use?
[23:20]  * saidinesh5 checks
[23:20] <saidinesh5> btw. Marzel which device do you use?
[23:20] <Marzel> Nexus 4
[23:20] <Marzel> (mako 16 GB)
[23:21] <saidinesh5> Ahh Marzel then why not use multirom?
[23:21] <saidinesh5> it works quite well for me
[23:21] <saidinesh5> and that way you get to happily dualboot
[23:21] <stgraber> slangasek: there you go, filled in the remaining sections of the wiki page. Let me know if there's something that's not covered.
[23:21] <Marzel> Because, I ve two phones to try ubuntu. ;)
[23:22] <saidinesh5> Marzel: nevertheless multirom is very nice way to install ubuntu if you ask me
[23:22] <saidinesh5> https://play.google.com/store/apps/details?id=com.tassadar.multirommgr
[23:22] <saidinesh5> simply install that app on a rooted device
[23:22] <saidinesh5> and it does everything for you
[23:23] <Marzel> Hm... But it worked in September...why not now?
[23:23] <saidinesh5> lol well .. lots of things seem broken even for me
[23:23] <Marzel> (So, the phone is running ubuntu. I only want to change from devel to devel-puposed... ;) )
[23:24] <saidinesh5> Ahh
[23:24] <saidinesh5> maybe that change is just editing some ppa in /etc/apt ?
[23:24] <saidinesh5> not sure
[23:24] <Marzel> On phone or on laptop?
[23:25] <Marzel> Sry... :D
[23:26] <saidinesh5> heh on phone
[23:27] <matv1> soo this might have been already but after updating to rtm 6 my U1 account crashes when i want to install an app..
[23:27] <matv1> has someone seen this happen?
[23:31] <Marzel> matv1 Yes, I had nearly the same problem. Only remove this account and add it again...
[23:32] <Marzel> matv1 Sorry, not nearly. ;)
[23:32] <Marzel> saidinesh5 nothing...
[23:33] <saidinesh5> hmm .....
[23:33]  * saidinesh5 shrugs
[23:34] <matv1> Marzel are you sure? I know about a bug in the previous promoted image where U1 account seemed in order but failed to work.
[23:34] <matv1> Now, I the account just gets deleted when i install an app from the store.
[23:35] <matv1> so in other words, I can add the account again but when i go into the store and try install an app, that fails and the account is deleted again
[23:36] <matv1> does that sound like what you got?
[23:37] <Marzel> matv1 Oh, no. This is not that I had....
[23:37] <matv1> Marzel okay
[23:38] <matv1> Marzel are u running rtm 6 image?
[23:39] <matv1> Marzel in which case you might be able to reproduce
[23:40] <Marzel> matv1 No, I've utopic r¿243? My Bug comes from time to time....
[23:41] <Marzel> matv1 Which phone do you have?
[23:41] <matv1> Marzel Mako
[23:41] <matv1> ie Nexus4
[23:43] <saidinesh5> ogra_: could you look into why this is failing for me? http://paste.kde.org/pvh8w5ff4
[23:43] <Marzel> Ok.... I didnt know, that mako could have rtm6... :D When have u installed it?
[23:43] <saidinesh5> creating a chroot using click
[23:43] <matv1> Marzel today
[23:45] <matv1> I am thinking a reboot might help but it might be usefull to adbpull some logs first. Except i am not really sure what would be usefull with this issue
[23:47] <Marzel> matv1 Ok... I tried to change channel today, but I always get error 255. So, I see, this should be not a server-prolem...
[23:49] <matv1> Marzel agree
[23:50] <Marzel> matv1 But I doesn't find something about this error status... :/
[23:51] <matv1> Right. It looks like a new one to me too. I was hoping to catch someone from Canonical still up :)
[23:51] <popey> hah
[23:51] <popey> oops
[23:51] <popey> shhhh
[23:51] <matv1> popey!
[23:51] <matv1> the very man :)
[23:51] <popey> bah
[23:51] <popey> wasup? ☻
[23:51] <matv1> sorry
[23:52] <matv1> my U1 account crashes and gets deleted when i add an app from the store
[23:52] <popey> well that's new
[23:52] <popey> which image/device?
[23:52] <matv1> after updating to rtm 6 earlier today
[23:53] <matv1> Mako
[23:53] <saidinesh5> Elleo: btw yes, click is only meant to run on desktop machines
[23:53] <saidinesh5> so i cant use it to create chroot
[23:53] <popey> I'm on #6 here but not added a u1 account yet
[23:53] <popey> let me try
[23:53] <matv1> sure
[23:53] <saidinesh5> http://archive.ubuntu.com/ubuntu/dists/utopic/main/ doesnt have binary-armhf
[23:54] <saidinesh5> which is what i need on the device
[23:54] <matv1> then get an app from the store
[23:54] <saidinesh5> so i will have to manually debootstrap it myself
[23:54] <saidinesh5> sigh
[23:55] <popey> saidinesh5: http://derived.archive.canonical.com/ubuntu-rtm/pool/main/c/click/
[23:57] <popey> ok, added account
[23:57] <matv1> popey cool can you install a new app now?
[23:58] <popey> installing dekko now
[23:58] <matv1> okay i got the new grooveshark one but that shouldnt matter
[23:58] <Elleo> saidinesh5: ah, okay
[23:59] <popey> matv1: yep, no problem
[23:59] <popey> and now I turn into a pumpkin, sorry!
[23:59] <popey> need beauty sleep
[23:59] <matv1> haha okay thnks for trying. weĺl see tomorw