[00:43] <FuuqUmiist> so what ever happen to the Ubuntu phone?
[00:44] <FuuqUmiist> will it have better privacy for users than google's android?
[00:46] <FuuqUmiist> imagine if Ubuntu Touch was released before google android... the whole world would probably be using it by now
[00:48] <popey> FuuqUmiist: we're still working on it ☻
[01:05] <FuuqUmiist> http://www.salon.com/2014/01/13/google_just_moved_into_your_house/
[01:25] <softcoder> hello i need help to figure out a problem
[01:26] <softcoder> using touch on nexus 4 and want to add a wifi connection to my router
[01:26] <softcoder> using latest dualboot (android + ubu)
[01:27] <softcoder> when i try to enter my long wifi pwd.. after about 30-60 seconds of typing (cause the wifi pwd is long) touch leaves the screen and goes back to system settings on its own
[01:27] <softcoder> since copy / paste text does not work i cannot copy and paste the pwd into the edit box
[01:27] <softcoder> any ideas what ican do??
[01:27] <popey> plug phone into laptop and use "phablet-network" to transfer the wifi setting to the phone
[01:28] <softcoder> how does phablet network work?
[01:28] <popey> it copies the network settings from /etc/somewhere to the phone
[01:28] <softcoder> i do have the phone plugged in via usb to this desktop ubuntu
[01:28] <popey> the pc needs to be on the wifi
[01:28] <softcoder> grrr
[01:28] <softcoder> is there no other way?
[01:28] <popey> make the key shorter
[01:29] <popey> or...
[01:29] <popey> use adb shell, to get a prompt on the phone, then "stop powerd" (I think)
[01:29] <popey> that will stop the screen blanking while you type the key in
[01:29] <popey> then you can "adb shell" and "start powerd"
[01:29] <softcoder> i wil ltry that!
[01:30] <popey> good luck
[01:30] <popey> I'm off to bed, dreaming of wifi keys
[01:30] <popey> nn
[01:30] <softcoder> thx
[01:33] <softcoder> that did not help
[01:33] <softcoder> anyone else with other ideas?
[01:33] <softcoder> stopping powerd did not disable to timeout entering wifi pwd
[01:34] <softcoder> can i just edit a text via via adb ??
[02:28] <softcoder> got it working
[02:29] <softcoder> adb root and adb shell
[02:29] <softcoder> then vi the conf file located:
[02:29] <softcoder> /etc/NetworkManager/system-connections/
[02:29] <softcoder> i intiially entered the pwd test so i knew which key to modify
[02:29] <softcoder> psk=test
[02:30] <softcoder> replace test with the real password, then save the file and voila
[02:37] <cwayne> cyphermox: hm, so when you do hostnamectl --pretty set-hostname "Nexus 4", hciconfig hci0 name shows Name: '"Nexus 4"'
[06:43] <softcoder> after doing an upgrade on my nexus 4
[06:43] <softcoder> i can no longer boot into android (hangs on google text)
[06:43] <softcoder> if i pick recovery it boots into ubuntu
[06:43] <softcoder> any ideas how i can fix the dual boot so android boots?
[06:46] <softcoder> on apt-get upgrade now
[06:46] <softcoder> it says:
[06:46] <softcoder> The following packages have been kept back:
[06:46] <softcoder> autopilot-touch gstreamer1.0-hybris gstreamer1.0-plugins-bad
[06:46] <softcoder>   libgstreamer-plugins-bad1.0-0 libpython3.3-minimal libpython3.3-stdlib
[06:46] <softcoder>   libqt4-dbus libqt4-declarative libqt4-network libqt4-script libqt4-sql
[06:46] <softcoder>   libqt4-xml libqt4-xmlpatterns libqt5concurrent5 libqt5core5 libqt5dbus5
[06:46] <softcoder>   libqt5gui5 libqt5network5 libqt5opengl5 libqt5opengl5-dev
[06:46] <softcoder>   libqt5printsupport5 libqt5sql5 libqt5sql5-sqlite libqt5test5 libqt5widgets5
[06:46] <softcoder>   libqt5xml5 libqtcore4 libqtgui4 python3.3 python3.3-minimal qt5-qmake
[06:46] <softcoder>   qtbase5-dev qtbase5-dev-tools ubuntu-sdk-libs ubuntu-touch
[06:46] <softcoder> why?
[07:04] <shiggitay> how goes the codin' ? :)
[07:09] <softcoder> can anyone here tell me how to get my android partition booting (nexus 4 dual boot)?
[07:09] <softcoder> is there a way to tell it fix the dual boot for the androdi poart?
[07:28] <softcoder> t - 15 minutes till i try to reflash back to android... can anyone tell me how to get my android partition booting?
[08:06] <dholbach> good morning
[08:08] <shiggitay> hello thar
[08:09] <shiggitay> :)
[08:09] <shiggitay> sup mrc_
[08:33] <softcoder> ok can anyone tell me how to fix a frozen android boot on nexus 4
[08:33] <softcoder> using dual boot.. can boot into ubuntu via recoery but not default android
[08:40] <softcoder> fastboot flash boot boot.img
[08:40] <softcoder> fastboot flash recovery recovery.img
[08:40] <softcoder> and both working
[09:07] <Tachyon`> any fix for dual boot on 4.4.2 yet?
[09:59] <tsdgeos> Mirv: zsombi: so i found out that http://paste.ubuntu.com/6761226/ fails under 'xvfb-run -a -s "-screen 0 800x600x24" qmltestrunner' but work under plain 'qmltestrunner'
[09:59] <tsdgeos> if using 5.2
[09:59] <tsdgeos> trying to find out why
[10:21] <zsombi> tsdgeos: excellent! wth is going on with xvfb?
[10:22] <tsdgeos> zsombi: seems the main window is not getting the initial "focus in" event
[10:22] <tsdgeos> and thus focus is borked since that
[10:22] <zsombi> tsdgeos: hmm...
[10:22] <tsdgeos> trying to find out why
[10:26] <ogra_> ricmm_, have there been recent unity-mir chganges that could cause bug 1269414 ?
[10:27] <ogra_> seems music stops a few seconds after suspend on the recent images
[10:27] <ogra_> (and there was a unity-mir update from 0.2+14.04.20140108.1-0ubuntu1 to 0.2+14.04.20140114.1-0ubuntu1)
[10:31] <ogra_> dholbach, happy birthday old fart !
[10:31] <ogra_> :)
[10:32] <dholbach> thanks ogra_
[10:52] <pitti> jibel: ah, I'm getting
[10:52] <pitti> tr: fehlerhaft positioniertes [:upper:]- und/oder [:lower:]-Konstrukt
[10:52] <pitti> 2014-01-16 11:48:45: Failure: Unknown port type:
[10:52] <pitti> jibel: with run-adt-test sometimes; fixed in r273, but I wonder why that doesn't always happen
[10:54]  * tsdgeos wins \o/
[10:55] <tsdgeos> now i only need them to accept the patch :D
[11:00] <tsdgeos> zsombi: Mirv: https://codereview.qt-project.org/#change,75675 fixes the text_area.qml problems for me
[11:01] <davmor2> Morning all
[11:07] <Mirv> tsdgeos: simply awesome. I'll cherry-pick that. with luck it would resolve multiple problems.
[11:09] <Mirv> also, the "random" word here got my attention.. https://bugreports.qt-project.org/browse/QTBUG-35840
[11:11] <Mirv> I hope 5.2.1 qtdeclarative would fix some of the remaining issues, but before at least that one is fixed I'm not jumping to take another newer snapshot.
[11:12] <pitti> jibel: sorry, -ECHANNEL; I thought this was #u-quality
[11:43] <Paolas> Hello all!
[11:43] <Paolas> please to help me...
[11:44] <Paolas> where download link zip for gt-p3100 tablet full 3g wifi for ubuntu edge ?
[11:45] <ogra_> !devices
[11:45] <ogra_> Paolas, if it is not on that wiki page then it does not exist i guess
[11:46] <ogra_> (also there is no ubuntu edge ... that was a device we never built .... the OS is called ubuntu touch (or ubuntu for phones)
[11:47] <Paolas> i dont know...
[11:47] <Paolas> where link download  ?
[12:53] <sergiusens> jdstrand, wrt to pre parsing the apparmor profiles; I would need to run the easyprof stuff as well; right?
[13:13] <jdstrand> sergiusens: ah, yes, becuase the profiles don't yet exist in /var/lib/apparmor/profiles
[13:14] <sergiusens> jdstrand, yup; a bit more complicated than anticipated; also I only got the cache written to using -S and redirecting to a file
[13:14] <sergiusens> they aren't totally equvalent though; which makes me think I may be missing some includes
[13:16] <jdstrand> that may be a bug. jjohansen ^
[13:20] <sergiusens> remember that I'm doing it from desktop though
[13:21] <jdstrand> sergiusens: so, for generating the profiles, you should be able to chroot into the image, install the clicks, then use 'aa-clickhook' to generate the profiles. for it to work though, you should *not* have /sys/kernel/securityfs/apparmor available
[13:22] <jdstrand> sergiusens: acutally, you don't have to run aa-clickhook separately, click does that
[13:22] <sergiusens> jdstrand, yeah, I was skimming through the python code for the hook
[13:22] <jdstrand> sergiusens: but aa-clickhook will generate the profile fine with /sys/kernel/securityfs/apparmor unavailable (it will warn that it can't load them
[13:23]  * jdstrand nods
[13:23] <sergiusens> chrooting may provide it's other complications
[13:24]  * sergiusens goes back to drawing board
[13:46] <jgdxx> is there a bug for lack of media queries support in UT browser?
[13:47] <ogra_> media queries ?
[13:48] <jgdxx> ogra_, css media queries.
[13:48] <ogra_> ah
[13:48] <jgdxx> could be I'm running a really old image, or that something else is gebroken
[13:48] <ogra_> hmm, the few i used in webapp development used to work
[13:48] <ogra_> but that was a while ago
[13:50] <jgdxx> ogra_, kay. I'll dig some more and file bugs.
[13:50] <ogra_> ++
[13:58] <daker> jgdxx: they do work
[14:00] <jgdx> daker, okay, I think it's the text input zoom I got a beef with. It was autofocus and I jumped the gun.
[14:01] <daker> jgdx: that's a normal behaviour
[14:02] <jgdx> daker, yeah, but it's broken http://ubuntuone.com/4db3Gcd43WR6MNN3SFBENg
[14:02] <daker> jgdx: why ?
[14:02] <daker> juste double tap
[14:03] <jgdx> daker, I'm using an emulator. Would that be a double click?
[14:03] <daker> jgdx: i think yes
[14:04] <jgdx> daker, broken in that the resulting zoom is too great. It introduces a vertical scroll and hides 50% of the text input.
[14:06] <daker> jgdx: can you open the webbrowser-app, and navigate to https://login.ubuntu.com/
[14:06] <jgdx> daker, I'm there
[14:07] <daker> oSoMoN: can you test this ?
[14:09] <jgdx> pre focus http://ubuntuone.com/00N9B9SV2sJUgxm9g0pdaQ post focus http://ubuntuone.com/4db3Gcd43WR6MNN3SFBENg
[14:10] <jdstrand> sergiusens: fyi, I updated https://wiki.ubuntu.com/Touch/Emulator#Handling_disk_snapshots for ubuntu-emulator
[14:12] <sergiusens> jdstrand, looks good :-)
[14:18] <oSoMoN> daker, what exactly do you want me to test?
[14:18] <daker> oSoMoN: what jgdx was saying
[14:18] <daker> oSoMoN: jgdx> pre focus http://ubuntuone.com/00N9B9SV2sJUgxm9g0pdaQ post focus http://ubuntuone.com/4db3Gcd43WR6MNN3SFBENg
[14:19] <daker> that's a normal behaviour, right ?
[14:22] <oSoMoN> daker, jgdx: the autozoom behaviour on text field focus is normal and expected, however in this specific case it kind of makes the situation worse
[14:23] <oSoMoN> I don’t know how this autozoom feature is implemented, maybe we could tweak it
[14:24] <tsdgeos> bfiller: who reviews https://code.launchpad.net/~aacid/qtubuntu-camera/no_priv_headers/+merge/201933 now that gusch is gone?
[14:25] <bfiller> tsdgeos: don't really have anyone yet, maybe rsalveti can take a look. seems like a easy review
[14:25] <tsdgeos> bfiller: yeah, basically should be a "if it builds, ship it"
[14:25] <tsdgeos> bfiller: built for me, but let's wait for CI :D
[14:27] <sergiusens> tsdgeos, do you know why the private headers were originally used? just out of curiosity
[14:28] <tsdgeos> sergiusens: no clue tbh
[14:28] <tsdgeos> i'd go with "copy&paste"
[14:28] <tsdgeos> but it'd be total guess
[14:28] <tsdgeos> or maybe it used to be private and then moved to public?
[14:29] <tsdgeos> which leaves me wondering if it will build with qt5.0 (it builds with 5.2 which is what i was trying to achive since Mirv has killed the  multimedia-private .deb)
[14:29] <tsdgeos> let's wait for CI as said :D
[14:33] <jgdx> oSoMoN, daker: the stock browsers on both ios and android will not zoom beyond the text field. E.g. http://ubuntuone.com/70dBf35QkHtPJSFjtffTQK They merely reposition the viewport. Are we ignoring the width meta property perhaps?
[14:33] <sergiusens> tsdgeos, yeah, otherwise, the change is fine from my PoV
[14:40] <oSoMoN> jgdx, mmm, that’s interesting, it looks like we could do a better job, would you mind filing a bug at https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+filebug and explaining your findings there (with the screeshots)?
[14:41] <tsdgeos> sergiusens: CI passed :)
[14:46] <asac> sergiusens: hey. so do we have a click build tool or something?
[14:46] <cwayne> anyone else see indicator tab bar titles not showing up?
[14:47] <asac> cwayne: which build/platform?
[14:48] <cwayne> asac: -proposed, mako
[14:48] <asac> davmor2: didrocks: ^^ heard of?
[14:49] <didrocks> asac: cwayne: no, I have all of them
[14:49] <didrocks> cwayne: can be an indicator crashing, won't be the first time :)
[14:51] <aquarius> hey, dudes. The Google Nexus wireless charger (https://play.google.com/store/devices/details/Nexus_Wireless_Charger?id=nexus_wireless_charger&hl=en)... does it require some sort of OS support? Specifically, will it work right with a Nexus 4 which is running Ubuntu?
[14:51] <didrocks> cwayne: did you try rebooting?
[14:51] <jgdx> oSoMoN, sure thing. Thanks
[14:51] <didrocks> oh, a aquarius ;)
[14:51] <aquarius> heya didrocks!
[14:51] <ogra_> aquarius, i have a zens qi charger and it didnt work the last time i tried, even though it should not have any QS specific thing
[14:51] <ogra_> *OS
[14:52] <ogra_> aquarius, but i think you can count on the fact that we'll fix it even if it doesnt
[14:53] <ogra_> (btw, dont get a zens for the N4 ... surface is to slippery for it ... it slides down if it is not 100% flat)
[14:54] <ogra_> oh, looking at that pic i guess it will have the same slippery issues
[14:55] <Hourd> I've ordered one of these for mine http://www.amazon.co.uk/gp/product/B00F5UAFDM/
[14:56] <Hourd> Hope it will have enough grip for my super slippy N4, but I have an N5 as well
[14:57] <aquarius> ogra_, ya, but I'm loath to spend sixty quid on a charger that might not work :)
[14:58] <aquarius> ogra_, am worried that it needs some sort of weird proprietary driver which we won't have
[14:58] <ogra_> http://www.amazon.co.uk/Zens-Qi-Single-Wireless-Charger/dp/B005PL5GSA/ref=sr_1_6?s=electronics&ie=UTF8&qid=1389884290&sr=1-6&keywords=zens+qi+charger
[14:58] <ogra_> thats mine
[14:58] <ogra_> aquarius, if andriod has it, we do too
[14:58]  * popey adds to wishlist
[14:59] <aquarius> ogra_, really? why doesn't yours work, then? I mean, to my mind charging ought to not require a driver because otherwise it wouldn't work if you're powered off :)
[14:59] <ogra_> aquarius, i didnt research at all
[14:59] <ogra_> i put it on it once, noted it doesnt charge and used the cable
[14:59] <aquarius> ogra_, oh, so it might not work under Android either? it Just Doesn't Work? :)
[14:59] <aquarius> heh.
[15:00] <ogra_> havent checked since
[15:00] <ogra_> it works under android
[15:00] <Hourd> some need to be positioned just right
[15:00] <davmor2> cwayne: what are you missing?
[15:00] <ogra_> and once i find the time i'll try again and fix it on ubuntu too
[15:00] <sergiusens> ogra_, it might be charging and just a problem with out indicator?
[15:00] <cwayne> davmor2: the tab titles
[15:00] <sergiusens> our*
[15:01] <ogra_> sergiusens, could be
[15:02] <davmor2> cwayne: I see indicator tabs, I see in app title tabs if that is what you are meaning
[15:03] <davmor2> cwayne: not all apps have the titles though I think
[15:04] <cwayne> davmor2: the indicator tab titles
[15:04] <cwayne> like Location
[15:04] <cwayne> aren't showing up for me
[15:07] <davmor2> cwayne: the only one I don't see is bluetooth but that is because it is disabled
[15:07] <cwayne> im seeing the indicators just not the titles, the actual words
[15:07] <cwayne> when im swiping through them
[15:08] <cwayne> youre obviously not seeing the same problem :)
[15:08] <davmor2> cwayne: so I see them on maguro and mako
[15:11] <annerajb> anybody have any updates on 4.4 phablet framework?
[15:11] <ogra_> annerajb, ongoing
[15:11] <mterry> ogra_, hello!  So I'm off tomorrow and Monday, but to my knowledge, nested mode is only waiting on a release of unity-system-compositor.  Which I assume has been held up while we sort out the problems getting a promotable image.  Once that is out, maguro should work again.  I tested grouper with latest hybris and it works fine.  So does mako
[15:12] <ogra_> with luck there are public images next week
[15:12] <ogra_> mterry, yep, tested grouper and maguro here too ... but the MP needs a signoff from the u-s-c team still
[15:13] <annerajb> ogra_, any repositories to look at?
[15:13] <mterry> ogra_, which MP?  The one for maguro?  It landed in trunk
[15:13] <ogra_> annerajb, i guess watching the mailing list for an announcement from rsalveti would be best
[15:13] <ogra_> mterry, oh, ok
[15:13] <mterry> ogra_, or the session-manager-touch one that actually enables it?
[15:14] <ogra_> mterry, session manager is my job
[15:14] <mterry> yup
[15:14] <ogra_> i thought the u-s-c one was still waiting
[15:14] <rsalveti> annerajb: we're working to setup a gerrit instance as well together with the new repos
[15:14] <mterry> ogra_, it's waiting to actually land in trusty.  jenkins hasn't packaged it up yet
[15:14] <ogra_> https://code.launchpad.net/~mterry/unity-system-compositor/dbus-screen-fix/+merge/201211
[15:14] <annerajb> rsalveti, :D thanks
[15:14] <ogra_> still oending review
[15:14] <ogra_> *pending
[15:15] <ogra_> oh, but merged
[15:15]  * ogra_ needs to learn to look at the status, not the merge requests 
[15:15] <ogra_> s/merge/review/
[15:15] <mterry> :)
[15:22] <attente> bfiller, hi
[15:23] <bfiller> attente: hey
[15:23] <attente> bfiller, is there some way to determine the default osk layout if the gsettings value is empty?
[15:24] <bfiller> attente: can I ping you in a bit, on a hangout right now. have a bunch of htings I want to discuss with you actually
[15:24] <attente> bfiller, sure
[15:34] <balloons> ping mardy
[16:09] <om26er> how long should it take for unity to show up in the emulator ?
[16:09] <ogra_> om26er, 10-15min on the first boot
[16:09] <ogra_> subsequent ones are minimally faster
[16:10] <om26er> ogra_, so  phablet shell login is expected much sooner ?
[16:11] <ogra_> yeah
[16:18] <ChickenCutlass> pitti, hi there.  Is there a way to get EOF using g_io_watch?
[16:23] <pitti> ChickenCutlass: hm, I'm not familiar with that; perhaps it counts as G_IO_ERR condition?
[16:24] <pitti> didrocks: so I hear you give some landing training sessions, the next one tomorrow?
[16:26] <didrocks> pitti: waow, news are going fast ;) I'll send an email announcing the piloting program officially tomorrow morning, then asac and I defined some batchs by team to ramp up
[16:26] <pitti> didrocks: right, julian asked me to join
[16:26] <pitti> didrocks: I'll be AFK tomorrow afternoon, but if you do morning sessions, or one next week, could I join one?
[16:27] <didrocks> pitti: the QA team won't be part of the first batch, but you are welcome to join (but the first one will be on thursday, not tomorrow)
[16:27] <didrocks> tuesday*
[16:27]  * didrocks can't type
[16:27] <pitti> ah
[16:27] <pitti> perfect
[16:27] <pitti> didrocks: I'm happy to go later; I don't think it's that urgent
[16:27] <didrocks> pitti: I'll keep you posted ;)
[16:28] <didrocks> (first, email to the ML tomorrow ;))
[16:30] <mterry> ogra_, do you know anything about inducing android driver events?  (I want to induce power button press in autopilot tests)
[16:31] <ogra_> mterry, why would that be android ? you should be able to just get events from /dev/input/*
[16:31] <ogra_> mterry, on mako i get power button events on /dev/input/event0
[16:32] <mterry> ogra_, sure, I can go through udev...  Is there an example of simulating those?
[16:32] <ogra_> ah, no idea
[16:32] <asac> didrocks: nice. seems the management is getting better at forwarding/communicating :)
[16:33] <didrocks> heh
[16:36] <popey> ooh, emulator took 7 mins to get from "run" to unity appearing
[16:38] <ogra_> popey, yeah, subsequent boots get better with every boot
[16:42] <davmor2> I keep thinking I should setup the emulator then I remember I got to much other stuff going on :D
[17:00] <popey> how does one shutdown the emulator nicely?
[17:00] <tsdgeos> jhodapp: have you seen https://bugs.launchpad.net/ubuntu/+source/qtvideo-node/+bug/1267818 ?
[17:01] <ogra_> popey, the US way is to use a gun
[17:01] <ogra_> popey, the pacifist way is probably poweroff -f
[17:01] <popey> ☻
[17:03] <bfiller> attente: hey
[17:03] <attente> bfiller, hi
[17:04] <bfiller> attente: so to answer your question, we've introduced a new key in gsettigs called active-language and it defaults to "en"
[17:04] <bfiller> attente: it's in this branch that hasn't been merged yet: https://code.launchpad.net/~thomas-moenicke/ubuntu-keyboard/ubuntu-keyboard-active-language/+merge/199292
[17:05] <attente> bfiller, ok
[17:06] <bfiller> attente: also can you add the UI for the following as they are supported: auto-completion, key-press-feedback, spell-checking, predictive-text
[17:07] <bfiller> attente: as well as the keyboard languages, enabled-languages key
[17:08] <bfiller> attente: only open issue is all the keyboard layouts are separate debs now and we don't have a way to install them dynamically
[17:08] <bfiller> attente: so they may have to be installed by default on the image for the short term
[17:09] <attente> bfiller, ok
[17:09] <attente> bfiller, i'm wondering if the way we're finding those plugins is correct
[17:10] <attente> right now, we're looking in the /usr/share/maliit/plugins/com/ubuntu/languages directory
[17:10] <attente> which is basically a hardcoded path
[17:11] <bfiller> attente: your looking at trunk of ubuntu-keyboard right? (the plugin code hasn't been released yet but that's pending)
[17:11] <attente> bfiller, yes
[17:12] <bfiller> attente: any suggestions on how to better do it? would be awesome if the plugins could be click packages somehow and installed dynamically when the user selects that language
[17:13] <bfiller> attente: keep in mind they install hunspell and predictive text dictionaries as well as the plugins, not sure where those get installed
[17:14] <attente> bfiller, no idea. i'm not too picky about the current method but if there's a better way, we can change to it
[17:14] <attente> bfiller, if hunspell and predictive text dictionaries are installed in the same directory, that might be problematic though
[17:15] <seb128> bfiller, btw in case you didn't notice, the most recent settings landing (like a week ago) enabled some of the osk options
[17:15] <attente> bfiller, however we already do some filtering to make sure non-sensible plugins don't get listed as well
[17:17] <bfiller> attente: so do you dynamially build your keyboard language UI based on what plugins it finds in that directory? or is it just a hardcoded list?
[17:17] <attente> bfiller, we build it dynamically, but the directory path is hard-coded
[17:18] <attente> we try to do some filtering based on the contents of the xml, so things like the phonenumber plugin aren't added
[17:18] <attente> (somehow the showcase plugin made it through though)
[17:19] <bfiller> attente: so
[17:19] <bfiller> attente: looks like that is slightly changed in trunk as I just installed those packages
[17:20] <bfiller> attente: the language plugins are installed in /usr/share/maliit/plugins/com/ubuntu/lib/<language>
[17:20] <bfiller> attente: I think the xml in /usr/share/maliit/plugins/com/ubuntu/languages is not used anymore and will be removed
[17:21] <attente> bfiller, ok
[17:21] <attente> bfiller, what are the package names for the plugins?
[17:21] <bfiller> attente: ubuntu-keyboard-english, ubuntu-keyboard-german, etc..
[17:22] <ogra_> dont forget ubuntu-keyboard-klingon
[17:22] <ogra_> else pitti cant type
[17:22] <attente> ha
[17:23] <ogra_> (he speaks it fluidly)
[17:23] <pitti> nuQneH ?
[17:23] <ogra_> ++
[17:23] <bfiller> attente: if you install the debs from here you can see: http://jenkins.qa.ubuntu.com/job/ubuntu-keyboard-trusty-armhf-ci/120/artifact/work/output/*zip*/output.zip
[17:23] <pitti> nah, as for keyboard layouts, there are only two: "US" and "broken" :)
[17:23] <bfiller> attente: I'm requesting a release for ubuntu-keyboard trunk today (hopefully) that will contain this changes
[17:23] <bfiller> ogra_: lol
[17:24] <attente> bfiller, that link doesn't seem to work for me
[17:24] <bfiller> attente: right, let me get a you a new one
[17:25] <bfiller> attente: http://jenkins.qa.ubuntu.com/job/ubuntu-keyboard-trusty-armhf-ci/139/artifact/work/output/*zip*/output.zip
[17:25] <bfiller> attente: you'd need to install ubuntu-keyboard, ubuntu-keyboard-data, and whatever ubuntu-keyboard-<lang> packages you want to test
[17:27] <attente> bfiller, ok, sounds good, thanks
[17:27] <attente> bfiller, i guess at some point we might need a way to get the list of packages
[17:28] <attente> so that we can do installation on demand
[17:29] <bfiller> attente: agreed, but they'd need to be click packages as we can dynamically install debs because of r/o filesystem
[17:29] <bfiller> can't
[17:29] <attente> bfiller, ah, ok makes sense
[17:30] <Ambious> Hello
[17:30] <bfiller> attente: think for now we'll just preinstall some and if the user wants others they'll have to manually install additions until we figure it out
[17:31] <bfiller> attente: as long as your UI just dynamically gets the list of installed langs from /usr/share/maliit/plugins/com/ubuntu/lib/ should be ok for now
[17:33] <bfiller> attente: or another option: your UI shows all the planned supported languages and when the user selects one you check if it's installed and if not prompt them to install it (which would be manual currently)
[17:34] <bfiller> attente: ah, I see you already have the keyboard settings in the UI :) When did that land?
[17:36] <attente> bfiller, i'm not sure, it was a MP just sitting around for a while if i remember, it just needed merging (which i guess seb128 did recently)
[17:37] <bfiller> attente: looks like it's just missing spell-checking
[17:38] <attente> bfiller, how do we check what spell-checking plugins are available?
[17:38] <attente> or do we just assume that every display language is a spell-checking language?
[17:39] <bfiller> attente: I think we don't need the spell-checking-language thing anymore. when you switch to a different keyboard layout the spellchecking for that lang is automatically enabled
[17:40] <bfiller> it's actually a dependecie of the ubuntu-keyboard-<lang> package - it depends on the proper hunspell-<lang> package
[17:40] <bfiller> so the spell checking dynamically changes when you change the keyboard language
[17:41] <attente> ok, so it's just the check box then, it sounds like
[17:41] <attente> cool
[17:41] <bfiller> attente: exactly
[17:41] <attente> i'll add that in now then
[17:41] <bfiller> attente: thanks
[17:42] <bfiller> attente: one other thing - when the user changes the "Display Language", should we automatically select the corresponding keyboard layout and set the active-language key to it?
[17:43] <bfiller> attente: would be weird if the display language was switched to say German but the keyboard stayed english
[17:45] <attente> bfiller, good question... i guess if the display language was switched you'd assume the spell-checking would also switch
[17:45] <attente> and since that's tightly bound to the current keyboard layout, i guess you'd expect it to
[17:45] <bfiller> attente: yes, but most importantly you'd assume the keyboard layout to switch
[17:46] <bfiller> yup
[17:46] <bfiller> attente: so to make that happen just set the com.canonical.keyboard.maliit.active-language when switching the Display lang and it should just work (once these branches land)
[17:47] <attente> bfiller, ok, sounds good
[17:49] <bfiller> ogra_, pitti : do you know how we are supporting changing the display language? looks like we are only seeding language-pack-en
[17:50] <bfiller> are lang packs for the langs you switch to required to support them fully?
[17:50] <ogra_> blaroche, we seed a  lot of langpacks
[17:50] <ogra_> err
[17:50] <ogra_> bfiller, ^^
[17:51] <bfiller> ogra_: I don't see that in the seed
[17:51] <ogra_> bfiller, language is set by ~/.pam-environment
[17:51] <pitti> bfiller: merely installing the language pack doesn't set the default
[17:51] <ogra_> bfiller, http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20140115/trusty-preinstalled-touch-armhf.manifest
[17:51] <pitti> either that, or system-wide by localectl (or writing /etc/default/locale)
[17:51] <ogra_> search for language-pack
[17:52] <ogra_> pitti, we dont use that anywhere in the phone images
[17:52] <ogra_> its all per user via pam
[17:52] <pitti> ogra_: /etc/default you mean?
[17:52] <pitti> ok
[17:52] <bfiller> ogra_: where are the lang packs seeded? looking at lp:~ubuntu-core-dev/ubuntu-seeds/ubuntu-touch.saucy
[17:52] <ogra_> system should stay on english
[17:52] <pitti> then ~/.pam_environment it is
[17:52] <ogra_> yep :)
[17:53] <ogra_> bfiller, hmm, i see it here in my local branch
[17:53] <ogra_> ogra@styx:~/Devel/seeds/ubuntu-touch.trusty$ grep language-pack touch|wc -l
[17:53] <ogra_> 6
[17:53] <ogra_> 6 langs seeded
[17:53] <ogra_> en de es fr pt zh
[17:54] <bfiller> ogra_: which branch has that?
[17:54] <ogra_> bfiller, oh, i see, you pointed to saucy :)
[17:54] <bfiller> ogra_: arg, didn't mean too (:
[17:54] <bfiller> let me check trusty
[17:55] <ogra_> they even have their own section
[17:55] <bfiller> ogra_: sorry, my fault looking at old seed
[17:55] <ogra_> (in the seed file)
[17:55] <bfiller> I see them now
[17:55] <ogra_> :)
[17:56] <bfiller> ogra_: do we have plans to add others dynamically? I'm in same boat with OSK keyboard langs/plugins. I don't want to seed all of them but no way to dynamically install because they are debs
[17:56] <ogra_> bfiller, i suspect we wont, but i could imagine we start building regional images at some point so you only have a fraction
[17:56] <ogra_> asac, ^^ ideas ?
[17:58] <asac> maybe regionalizations could be a DLC plugin available in click store for OSK?
[17:58] <asac> i think its exactly the DLC concept
[17:58] <ogra_> asac, it would have to put a lot of stuff across the readonly filesystem
[17:58] <asac> you have an app (keyboard could also be an app), and you provide plugins/extensions also through the store
[17:59] <asac> ogra_: well, i guess that depends on the keyboard software
[17:59] <ogra_> or we need to change a lot of the system to accept it differenntly
[17:59] <asac> might need refactoring so it can live with plugins in click
[17:59] <ogra_> asac, thats about langpacks
[17:59] <ogra_> not just kbd
[18:00] <ogra_> if we use different places for locale stuff we have a lot to change in the rest of the system
[18:00] <asac> ogra_: can you download new languages in adndroid?
[18:00] <asac> or only whats installed by default?
[18:00] <ogra_> if we dont we end up with a ton more writable places
[18:00] <asac> anyway. really have to step out for 1h or so
[18:00] <asac> bbiab
[18:01] <ogra_> asac, i think they are preinstalled and there are regional images ... by continent or so
[18:01] <ogra_> asac, bfiller, one step we need to take is definitely to create touch specific langpacks ... that will shrink them a lot in size
[18:02] <ogra_> which might even enable us to ship them all
[18:02] <ogra_> (today we ship a lot of desktop translations we dont use at all)
[18:03] <bfiller> ogra_: good point
[18:03] <bfiller> ogra_: it might be possible for the osk plugins to be clicks, but we'd need to make some changes to support that
[18:04] <popey> #132 is built
[18:04] <bfiller> ogra_: the disk consuming size in the osk plugins is the spell checking stuff which gets pulled in by hunspell
[18:04] <popey> ogra_: do you have a maguro you can dogfood?
[18:04] <ogra_> right, i'm not too concerned about osk ... more about the whole langpack stuff
[18:04] <popey> unless davmor2 is still about?
[18:04] <bfiller> ogra_: and the predictive text dictionary, otherwise it's just a few qml files
[18:04] <davmor2> popey: I am but I'm about to go for tes
[18:04] <Ambious> Hi guys, quick question. I'm trying to build for deb and failing at the breakfast. There's obviously no "phablet" branch in the CM git, which only has cm11 and cm10.2, while the ubuntu touch git highest branch is 10.1. Is there any way around this?
[18:05] <ogra_> popey, not atm, my maguro has a ton of hacked up stuff i cant lose atm
[18:05] <davmor2> tea even
[18:05] <ogra_> (nested Mir sessions)
[18:05] <davmor2> I can do the dog food after that though
[18:05] <popey> ogra_: no worries
[18:05] <popey> davmor2: thanks
[18:05] <davmor2> and with that tea
[18:05] <ogra_> bfiller, right, and hunspell should even be dragged in by langpack deps
[18:05] <ogra_> davmor2, tea with tess ?
[18:05] <ogra_> does your wife know ?
[18:05] <bfiller> ogra_: that's true
[18:06] <pitti> bfiller, ogra_: no, langpacks don't depend on things like dictionaries; you want "check-language-support" from language-selector-common for that
[18:07] <ogra_> pitti, argh, right, they used to back in the days
[18:07] <pitti> ogra_: no, never language-pack-*; we used to have language-support-* metapackages, but they got too impractical
[18:07] <ogra_> right, thats what i meant
[18:07] <pitti> so we switched to a more dynamic way of "install everything that check-language-support says you are missing"
[18:08] <ogra_> pitti, right, wont work if we want to preinstall it
[18:08] <ogra_> i guess we just can seed the spellcheckers then
[18:09] <ogra_> i think the first step needs to be to generate langpack-touch-$lang for our stuff ... so we can drop the gnome ones
[18:09] <ogra_> and since thats a new package anyway we should probably discuss to simply add deps for osk packages and spellcheckers to them
[18:10] <ogra_> after all they are only needed at build time
[18:10] <ogra_> its not like you install anything dynamically on your phone
[18:10] <pitti> well, it seems easier to add check-language-support to livefs-build?
[18:11] <ogra_> pitti, well, it would have to learn about touch langpacks
[18:11] <pitti> that'll select the spell checkers, dictionaries etc. that we need based on what's installed, without the need to maintain a separate set of dependencies
[18:11] <pitti> ogra_: yes, touch langpacks is an independent matter
[18:11] <ogra_> is it able to run with something like --all ?
[18:12] <ogra_> or do we need to supply a list
[18:12] <pitti> you can iterate over all the languages that we install
[18:13] <pitti> for l in en de [...]; do check-language-support -l $l; done
[18:13] <ogra_> yeah
[18:13] <pitti> but if you don't call it with any arguments, it just prints out everything for "your" system
[18:13] <pitti> i. e. based on the locales and software you have installed
[18:14] <pitti> i. e. in livefs-build chroot, something like "apt-get install `check-language-support` should DTRT
[18:14] <ogra_> i have asked to get language stuff on the sprint agenda so it can be discussed there
[18:14] <ogra_> i'll come back to you once we have solved the langpack-touch- bit :)
[18:16] <pitti> ogra_: langpack-o-matic supports building different flavours (like -gnome, -kde, or now -touch)
[18:16] <ogra_> yay
[18:17] <pitti> we mostly need a heuristic to classify a package for "gnome", "kde", "touch", and "base" (aka "everything that's shared between flavours)
[18:17] <ogra_> pitti, i'll invite you to the discussion (via hangout or so) once it happens
[18:17] <ogra_> (or are you at the core spring end of the month)
[18:17] <ogra_> *sprint
[18:18] <pitti> ogra_: FYI, http://bazaar.launchpad.net/~ubuntu-langpack/langpack-o-matic/main/view/head:/lib/pkg_classify.py#L111 is that logic
[18:18]  * ogra_ looks 
[18:18] <pitti> it currently looks at the dependencies and anything gtkish or gnomeish goes into -gnome, etc.
[18:18] <ogra_> hmm
[18:19] <ogra_> we might rather need something like parsing the seeds or so ... i think think we have any such marker on the packaging level for touch
[18:20] <ogra_> *i don't think
[18:20] <ogra_> and even for that we would only need it for gui ... since we only translate the UI session
[18:20] <pitti> ogra_: something like "qt.*ubuntu" dependency?
[18:21] <pitti> e. g. qtdeclarative5-ubuntu-ui-toolkit-plugin
[18:21] <ogra_> hmm, perhaps ...
[18:21] <pitti> it could also be several heuristics which cover "QML", "platform-api", etc.
[18:21] <ogra_> yeah, that sounds like it
[18:22] <pitti> it also has a list of "overrides" which fix classification for particular packages where the heuristics is wrong
[18:22] <ogra_> click apps ship their translations themselves ...
[18:22] <ogra_> it should boil down to a really small set of translations in the end
[18:23] <pitti> unfortunately we don't use tasks for those packages, otherwise we could look at "Tasks:"
[18:23] <ogra_> yeah
[18:23] <pitti> well, anything which is in the apt package record, I'm sure we'll find something
[18:24] <ogra_> well, once the stuff is in main we can merge the touch seed into the normal ubuntu seed
[18:24] <ogra_> that should make tasks possible
[18:24] <ogra_> iirc tasks dont work atm because of the stuff being in universe
[18:24] <mterry> pitti, hello!  I'm looking at making an autopilot test for the shell that needs to simulate (or actually have) a power button press.  Is there an example of that in another package I could steal?  I looked at using udev, but I don't think it goes through udev?  That event might just be android-side
[18:25] <pitti> mterry: sorry, on my way out
[18:25] <mterry> pitti, no worries
[18:25] <pitti> mterry: how does it listen to the power button event?
[18:25] <pitti> i. e. dbus/binder/logind/etc/
[18:26] <pitti> mterry: can you mail me?
[18:26] <mterry> pitti, powerd gets it.  I think via android event system
[18:26] <pitti> good night everyone (sorry, need to run)
[18:26] <mterry> pitti, sure
[18:26] <pitti> mterry: ok, I don't think we have a ready-made solution for that; can you plase point me to the code that listens to it?
[18:27] <ogra_> pitti, events can be read from /dev/input/event* ... there is surely code that uses that
[18:27] <ogra_> in AP
[18:28] <ogra_> (note this is user readable on phones)
[18:32] <mterry> ogra_, but I was monitoring udevadm, and I didn't see any from it.  Are you sure that it's not just handled in android?  powerd listens directly to android
[18:34] <ogra_> mterry, i was cat'ing /dev/input/event0 and could see garbage for each button press
[18:35] <davmor2> and back
[18:35] <mterry> hm
[18:36] <ogra_> there should be an xev like way to get something useful from the garbage
[19:06] <sforshee> mterry: you might be able to synthesize a power button press by using uintput to create a new input device
[19:06] <sforshee> assuming that the input stack has the smarts to pick up new input devices as they appear
[19:15] <werty100> Hi
[19:16] <werty100> Is make sense to PORT ubuntu to my Xperia U?¿
[19:17] <jjohansen> jdstrand, sergiusens: hrmmm I'd need to see both profile dumps to have an idea why they are different
[19:19] <shiggitay_> ogra_, hello again... possibly obvious/stupid question: once the 4.4 HAL is completed and ported how difficult would a port of UT for the LG GPad 8.3 be to accomplish?
[19:33] <Fusl> hey guys... does someone know how long the i9100 takes to boot the ubuntu touch for the first time?
[19:33] <popey> |---------------------------------| That long
[19:33] <Fusl> in hours?
[19:33] <Fusl> :D
[19:34] <popey> ☻
[19:34] <popey> I don't know, but it's not a fast device, so I expect some minutes
[19:34] <Fusl> it already takes 20 minutes and it still showing the "Galaxy SII" screen
[19:34] <Fusl> (with the yellow warning triangle)
[19:35] <sergiusens> balloons, hey; I didn't add a calendar; the line is stopped ;-)
[19:35] <balloons> sergiusens, yes, I forget / didrocks reminded me
[19:37] <Fusl> what i exactly did was: flashing the cwm with heimdall, installing cm-10.1, did a factory reset and then installing saucy-preinstalled-armel-i9100.zip and then saucy-preinstalled-phablet-armhf.zip via clockworkmod... then i rebooted and thats when it already takes 20 minutes for this screen: http://goo.gl/X05Tew
[19:49] <boiko> awe_: is the ofono in the images supporting multiple calls already?
[19:50] <cwayne> stgraber: i hope i captured the 3 options correctly :)
[19:50] <rickspencer3> hey, for the first time in MONTHS, my phone froze, but I can shell into it
[19:51] <awe_> boiko, it should, the support landed in ofono 1.12+bzr6846-0ubuntu1
[19:51] <rickspencer3> anything I can do to help figure out what's up and log a good bug?
[19:51] <boiko> awe_: nice! I will flash today's image and try that one
[19:51] <awe_> boiko, ok!
[19:51] <boiko> awe_: thanks
[20:01] <sergiusens> rickspencer3, checking the unity8 logs would be my first grab
[20:02] <Fusl> reflashed it on my phone but still doesn't work :(
[20:02] <Fusl> can i somehow use the usb cable to grab useful information out of it? (it still stucks on the galaxy s2 boot logo)
[20:04] <rickspencer3> sergiusens, will do, can you tell me which logs, specifically?
[20:04] <rickspencer3> I don't see anything in /var/log
[20:04] <sergiusens> rickspencer3, $HOME/.cache/upstart/unity8.log
[20:05] <rickspencer3> ah
[20:05] <rickspencer3> no wonder :)
[20:05] <sergiusens> also grab a /system/bin/logcat dump
[20:05] <davmor2> meh sergiusens beat me to it :)
[20:06] <rickspencer3> sergiusens, just the latest unity log?
[20:06] <sergiusens> rickspencer3, yeah, the rotation thing should be from previous runs
[20:07] <davmor2> rickspencer3: the other one that might be useful is if you know what app was running just before the crash.  That will likely be under .cache/upstart/ too.  Also is there a crash report in /var/crash too?
[20:16] <rickspencer3> davmor2, there is no recent crash file
[20:17] <rickspencer3> but there are tons of files in .cache/upstart
[20:18] <sergiusens> rickspencer3, every app is started with upstart
[20:18] <rickspencer3> sergiusens, I know
[20:18] <rickspencer3> but there is no way for me to know from that list which one triggered the crash
[20:18] <rickspencer3> sergiusens, maybe we should do something with upstart where we start each app under some kind of confinement system
[20:19] <rickspencer3> I'll talk to jdstrand, maybe app armour can help here

[20:19] <sergiusens> rickspencer3, if there is no crash file it might not have been a crash though
[20:19] <sergiusens> lol
[20:19]  * jdstrand reads backscroll
[20:19] <rickspencer3> sergiusens, yeah, I got the files you suggested, I'll log a bug just in case
[20:19] <rickspencer3> jdstrand, sorry, didn't mean to ring you, I was teasing sergiusens
[20:19] <sergiusens> might be some deadlock; reason for suspecting unity8/mir
[20:20] <rickspencer3> need to go to a call
[20:20] <rickspencer3> biab
[20:20] <jdstrand> hah

[21:00] <rinaku> hi
[21:00] <rinaku> i'm using ubuntu touch for the first time and i'm wondering if there's any documentation about the basic usage of the phone
[21:01] <rinaku> such as how to import contacts that I exported from my previous phone
[21:01] <rinaku> i can't find that on the wiki
[21:25] <achiang> doanac: ping, around?
[21:25] <doanac> achiang: yes
[21:26] <achiang> doanac: hey, i'm looking at ubuntu-test-cases/touch and had some questions...
[21:26] <doanac> sure.
[21:26] <achiang> doanac: is it common for the packages you are testing to have a separate branch for their test cases, vs. as part of the package itself?
[21:27] <achiang> doanac: context is, i'm looking at our customization work, and we have a code branch (lp:savilerow) and a separate test case branch
[21:27] <achiang> doanac: i think the only consumer of the test case branch is ubuntu-test-cases...
[21:27] <doanac> achiang: its a little out of the ordinary, but your specific test is a little out of the ordinary
[21:27] <doanac> you thinking about moving it into our repo?
[21:28] <achiang> doanac: i'm wondering how much heartburn it would cause to co-locate our test cases into our code branch
[21:28] <doanac> achiang: i'd have no objections.
[21:28] <achiang> doanac: the idea being, someone would branch savilerow and have both code and tests
[21:28] <achiang> doanac: one drawback is that the code branch can take a bit longer to pull
[21:29] <achiang> doanac: maybe 30 seconds vs the 3 seconds it takes to pull the test branch
[21:29] <achiang> doanac: it also of course, takes more disk space
[21:29] <doanac> really? what's in the branch?
[21:29] <cwayne> but we'd still need the devices setup to run these tests anyway
[21:29] <achiang> doanac: we have images, etc. that are needed for the customizations in the code branch
[21:30] <cwayne> there's no super-simple way to say 'just run custom tests' on a pristine system
[21:30] <doanac> ah.
[21:30] <achiang> doanac: so i'm thinking what we'd do in the setup is to pull the entire branch with co-located code, data, and tests; and then just push the tests directory over to the SUT
[21:31] <cwayne> but the tests are essentially useless without the rest of the framework/utah/autopilot/et al
[21:31] <achiang> doanac: but before we go down that route, wanted to get a sense from you whether there are any environmental limitations about disk space where you do the bzr pull, etc.
[21:32] <doanac> achiang: not really. we could also switch to lightweight checkouts instead of running bzr-branch in our tests if needed.
[21:32] <achiang> cwayne: i'm really just talking about changing tests/customizations/setup.sh in the ubuntu-test-cases/touch package
[21:32] <doanac> plars: what do you think ^^^
[21:32] <cwayne> achiang: yeah, but i dont see a clear benefit to having the cases in our trunk though
[21:33] <cwayne> i agree that it's weird, but i don't know that it'll really fix anything to move them
[21:33] <achiang> cwayne: oh, now i am understanding your point... our test cases are very specific to utah/autopilot?
[21:33] <plars> give me a minute to catch up
[21:34] <cwayne> yeah. its not as simple as branch lp:savilerow and now youre all set up to run the custom tests
[21:34] <cwayne> you need to provision the device, install autopilot stuff, then push it over, then run it
[21:35] <achiang> cwayne: i mean, any downstreams would have to provision the device anyway
[21:35] <achiang> cwayne: so that part doesn't go away for our downstreams, whether it's an OEM customer or a community remix
[21:36] <cwayne> but they'd still need to then branch lp:ubuntu-test-cases/touch anyway
[21:36] <achiang> i see
[21:36] <cwayne> theres no option for simply just branching savilerow and having the tests run simply
[21:36] <cwayne> at least that i know of
[21:36] <plars> are these all autopilot tests?
[21:36] <cwayne> yeah
[21:36] <cwayne> i don't think they *need* to be per se
[21:37] <cwayne> but they are, as we were trying to get it to fit into the existing infrastructure easily
[21:37] <achiang> cwayne: well, i am also mixing up some other ideas in this conversation... i am actually more concerned about our own devs (or OEM/downstream devs) adding a customization and forgetting to add a test case
[21:37] <plars> most of the autopilot tests can be run locally without any of our stuff, the biggest difference is that you would have to unlock the screen yourself, and you wouldn't have all the results collected if you run them by hand
[21:37] <achiang> so having tests in a separate branch makes it easy to forget
[21:39] <plars> do the developers know how to build the image with their changes and run the tests?
[21:41] <achiang> plars: well, jenkins would spit out the image for a dev
[21:41] <achiang> presumably
[21:41] <cwayne> jenkins would spit out the custom tarball that is, right?
[21:41] <plars> but that's after it's merged
[21:43] <achiang> plars: we might have to write some docs for our downstreams on how to build an image with their changes and run tests, so you can assume that problem is theoretically solvable
[21:43] <plars> achiang: combined with that, I think it sounds useful
[21:44] <achiang> ok
[21:44] <achiang> i'm going to go for it then
[21:46]  * shiggitay_ pokes ogra_ 
[21:47] <achiang> doanac: plars: cwayne: thanks for the help. i'll see about sending up an MP to you guys soonish
[21:47] <doanac> achiang: thanks
[21:48] <cwayne> plars: while we're on the subject, there has been a quite high number of failures in touch_custom recently, any ideas why?
[21:48] <cwayne> at least a few of them with this:
[21:48] <cwayne> next_index = (current_index + 1) % self._get_number_of_tab_buttons() ZeroDivisionError: integer division or modulo by zero
[21:49] <plars> cwayne: there have been quite a bit in the other builds too on and off, but there have always been more in the custom builds - you were running down some bugs last we discussed it, or did those get addressed already?
[21:49] <cwayne> plars: so i have the ubuntu-ui-toolkit and gallery-app ones nailed down
[21:49] <cwayne> those are because of the way those apps are launched (i.e. not with the right environment, so it's not loading the custom theme)
[21:50] <cwayne> those *used* to be the only failures, now i'm seeing a lot of random, erratic ones
[21:50] <cwayne> almost all of them fromt he last run seem to be failures on getting self._get_number_of_tab_buttons()
[21:50] <plars> cwayne: I don't think I remember seeing that ZeroDivisionError in any of the non-custom builds
[21:53] <cwayne> plars: it looks like something happened at build 128
[21:54] <plars> cwayne: odd, both 127 and 128 used the same android and ubuntu?
[21:54] <plars> http://ci.ubuntu.com/smokeng/trusty/touch_custom/
[21:55] <cwayne> plars: must have been rebuilt because of the custom tarball then
[21:55] <cwayne> hmm
[21:55] <cwayne> are these fresh installs, or updates?
[21:55] <plars> cwayne: fresh installs
[21:56] <cwayne> huh there goes that theory then
[21:57] <cwayne> plars: would you be able to kick off a test run?
[21:57] <cwayne> there's something fishy, but i can't quite figure out what it would be
[21:57] <plars> cwayne: sure, it'll just rerun the latest image
[21:57] <plars> cwayne: and it will replace the results that are already there. Is that ok?
[21:57] <cwayne> plars: yep
[21:57] <cwayne> im going to try and set it up to run them locally here as well
[21:58] <cwayne> might give me more insight on wtf is happening :)
[21:58] <plars> cwayne: actually, no I can't
[21:58] <plars> cwayne: looks like there was a new build that just started
[21:58] <plars> cwayne: the tests just started on their own, so they should start showing up soon
[21:58] <cwayne> plars: well that's just as good i suppose :)
[21:58] <plars> yep
[21:59] <cwayne> plars: so to get this setup locally, all i'd need is lp:ubuntu-test-cases/touch right? and then just installing some deps and whatnot (utah et al)
[21:59] <cwayne> like is there any magic that's contained in jenkins, or does it just branch that and run the contained scripts
[22:00] <plars> cwayne: pretty much, you'll need utah from ppa:utah/stable
[22:00] <plars> cwayne: android tools, etc of course
[22:00] <plars> cwayne: there are two main scripts you would care about
[22:00] <plars> cwayne: provision.sh - look at the args to it, you'll also want to pass it the network config for your local network
[22:01] <plars> cwayne: the other is jenkins.sh, which you'll want to call with your device id (if needed) and the test to run (ex. camera-app-autopilot)
[22:01] <cwayne> plars: so there's no easy way to run *all* of them?
[22:01] <plars> cwayne: when you run a test that way with jenkins.sh, you'll end up with a directory called clientlogs with the logs, yaml of results, etc
[22:02] <plars> cwayne: not really, the tests don't all run in one go as it is
[22:02] <plars> cwayne: they do the provisioning, reboot, run the first set of tests, reboot, second set, reboot...
[22:02] <plars> cwayne: they are separate jobs
[22:03] <plars> cwayne: you could, of course, just construct a simple script that runs them all in succession, but if you want to save the results of each, make sure to backup the clientlogs directory between each run
[22:03] <cwayne> plars: now whats the difference between running jenkins.sh, and just running phablet-test-run
[22:05] <plars> cwayne: jenkins.sh does most of the same stuff, but it uses utah to kick off the test cases individually (which is how we see the individual testcase results in the dashboard). Eventually phablet-test-run will be called directly, there's some stuff in flight to make that happen
[22:05] <plars> cwayne: the biggest difference is that with jenkins.sh, your screen will get unlocked for you automatically, and it will pull the results off at the end
[22:06] <cwayne> plars: ah, ok
[22:06] <plars> cwayne: likewise, provision.sh is a wrapper around phablet-flash, phablet-click-test-setup, phablet-config, etc
[22:07] <cwayne> right
[22:07] <cwayne> does phablet-click-setup just install all of the -autopilot debs?
[22:07] <plars> cwayne: you can still use phablet-test-run directly once you've provisioned like this, there's nothing really magic about it, it just simplifies it down so that the jenkins jobs themselves don't contain a lot of magic
[22:08] <cwayne> ok cool, that's what i was hoping for
[22:08] <plars> cwayne: phablet-click-test-setup pulls bzr branches for the click package you specify and sets it up so that autopilot can be used to test against the right version. It's part of phablet-tools
[22:11] <cwayne> ah right, i feel like i knew that (or should've :P)
[22:11] <cwayne> plars: and these tests are run as the phablet user, correct?
[22:12] <plars> cwayne: yes
[22:57] <cwayne> plars: just in case your curious, i think the touch_custom suite should be fixed (it was a renaming/system-image issue that's now fixed) :)
[23:01] <achiang> cwayne: ooh, another dep on our naming? can you add it to the spreadsheet we've been working from?
[23:02] <achiang> plars: are the touch test cases in python2 or python3?
[23:03] <plars> achiang: python2 I believe.  I didn't write any of them, but last I heard the conversion of autopilot to python3 was still a wip due to some deps
[23:03] <plars> cwayne: awesome
[23:03] <achiang> plars: ok, thanks
[23:03] <plars> cwayne: so the next build should be improved?
[23:07] <sergiusens> achiang, plars it's all py2
[23:09] <achiang> sergiusens: thx
[23:13] <cwayne> plars: yes, it should be better
[23:14] <cwayne> achiang: it must have built right in the middle of the renaming stuff, as it got custom-sevilerow-trusty v1, but i just reflashed and it had the proper custom-savilerow-trusty v1
[23:14] <sergiusens> balloons, btw, I don't know enough qml to make that feed api mockable in shorts
[23:14] <achiang> cwayne: ok
[23:49] <jose> hey guys! I'm having some problems on trusty while trying to sync syncevolution with google contacts, external transport failure (local, status 20043) is what I get