[00:00] <rsalveti> there are quite a few development boards that are compatible
[00:00] <rsalveti> just not raspb pi
[00:00] <olli> rsalveti, know of any board that are compatible
[00:00] <thomi> barry: ok, so IIRC, cgoldberg's branch ships two binary packages, so you can choose which you want to install. doesn't that get you what you want anyway?
[00:00] <bschaefer> thomi, do you have a file to look at? I seem to be missing what file you're talking about :)
[00:00] <thomi> bschaefer: well, I'm asking because i thought it was in lp:unity, but I can't find it anymore
[00:00] <thomi> maybe it got deleted, or maybe I just dreamed the whole thing
[00:01] <bschaefer> haha, this would have been in the AP tests?
[00:01] <barry> thomi: if eventually we can drop python-windowmocker *and* /usr/bin/window-mocker is python3, then i can live with that for now
[00:01] <thomi> barry: well, I think it's probably /usr/bin/window-mocker3, but yeah :)
[00:01] <thomi> bschaefer: yeah
[00:02] <rsalveti> olli: beaglebone, beagleboard, wandboard, quickstart, pandaboard...
[00:02] <olli> rsalveti, thx
[00:02] <thomi> bschaefer: IIRC, we had some failures with the launcher and Gtk apps that had odd X11 window flags set
[00:02] <rsalveti> olli: http://www.cnx-software.com/development-kits/linux-development-boards/
[00:02] <bschaefer> thomi, right, we had an issue where umm gtk patched their calc program
[00:02] <thomi> bschaefer: so you wrote a window-mocker Gtk backend that allowed you to set those odd window-flags
[00:02] <bschaefer> to only allow 1 instance
[00:02] <thomi> no, this was different
[00:03] <thomi> ahh well, it seems like we'll keep the py2 version around for unity7 for a while anyway :)
[00:03] <barry> thomi: yeah, except that i don't think we want both.  but if that's the most expedient way to move this transition forward, then i can live with it for now.  we just need to get things unblocked :/
[00:03] <bschaefer> thomi, hmm
[00:03] <bschaefer> thomi, sadface, no bells are ringing at all in my head...
[00:03] <thomi> barry: I don't understand why we don't want both
[00:04] <thomi> bschaefer: no worries, thanks for the help anyway
[00:04] <thomi> barry: I can understand not wanting both installed (or either installed 99% of the time, TBH)
[00:04] <bschaefer> thomi, you're welcome!
[00:04] <barry> thomi: for the short term, if necessary, that's okay.  but in the long term, we need to get rid of the py2 version and move all the deps off of it, otherwise we'll still be pulling in python2
[00:04] <thomi> barry: but to cut off py2 support for no good technical reason (none that I can see, anyway)
[00:05] <thomi> barry: but only if you install the python2 package... if nothing uses it, then the worst case is there's a pakcage in the archive that nobody installs :)
[00:05] <barry> thomi: right, the point was whether anything imported windowmocker as a module.  if it's just an executable you run, then it doesn't matter.  if you import it, then yeah, we need both for now.  unity7 *does* import windowmocker, but for silly reasons that could be fixed ;)
[00:05] <thomi> yeah
[00:07] <barry> thomi: okay, i really don't care whose mp wins, as long as we have a path forward ;)  at worst, we'll carry py2 cruft around we don't need for a while.  let me review cgoldberg's branch and if there's anything i think missing, i will comment on his mp.
[00:07] <barry> thomi: eod for me now though.  i'll do this first thing in the morning
[00:07] <thomi> barry: thanks. I'll be on national holiday tomorrow
[00:08] <thomi> barry: I've already reviewed his branch, I think it's good to go
[00:08] <barry> thomi: then jfdi! :)
[00:08] <barry> thomi: i can always mp any repairs later, if necessary
[00:09] <thomi> heh
[00:13] <yanboyang> rom may flash stock recovery on boot.fix? I don't know i need choose yes-disable recovery flash or No?
[00:45] <matv1> question @anyone from canonical:
[00:45] <matv1> is it a designchoice to have apps start with the bottom menu open?
[00:45] <principiante> Hi everybody.
[00:48] <principiante> I have a question
[00:49] <matv1> @principiante go ahead and ask
[00:49] <principiante> Is possible install ubuntu touch on ipad 2?
[00:50] <nhaines> principiante: if it's not on https://wiki.ubuntu.com/Touch/Devices , no one has done it before.
[00:50] <matv1> I dont think so. not with very major recoding
[00:50] <nhaines> principiante: and if Android doesn't run on it, it's probably not possible.
[00:51] <nhaines> matv1: yes, they are testing toolbar discovery.  So at the moment, the toolbar starts opened, and then collapses after some seconds.  It's not the final decided solution.
[00:52] <matv1> ahah glad to hear you were waiting for my feedback to make the final decision :)
[00:52] <matv1> i dont like it btw
[00:53] <matv1> nhaines do u know if its an all or nothing choice?
[00:54] <matv1> i mean should it work for either all apps or none?
[00:54] <RAOF> principiante_: No, unless you can get an Android 4.3/4.4 build running on the iPad 2 first.
[00:55] <principiante_> Android?.  You mena Idroid?
[00:55] <principiante_> mean*
[00:59] <principiante_> I have an ipad 2, but it is a brick and I cant use it
[01:00] <DonkeyHotei> why is it a brick?
[01:00] <nhaines> matv1: it's a framework decision, so it is for all apps with toolbars.
[01:00] <nhaines> matv1: I don't think anybody likes it, but I don't think anything's been done about it since it was implemented as a test.
[01:01] <nhaines> principiante_: no, we mean Android 4.4.  Cyanogenmod, specifically.
[01:01] <matv1> nhaines can you briefly enlighten me about what the advantage would be?
[01:01] <RAOF> principiante_: I mean Android - (the current) Ubuntu Touch builds use the Android low-level infrastructure.
[01:02] <nhaines> matv1: that users can see that there is a toolbar with extra commands available, and that they can swipe up from the bottom of the screen to access it.
[01:02] <matv1> okay
[01:02] <matv1> anyone would have worked that out after 5 minutes imo
[01:02] <nhaines> matv1: it's the same reason when you launch a desktop application in Unity, the application's menu shows for 3 seconds and then fades to the application title.
[01:02] <RAOF> Only if they *try* for 5 minutes.
[01:03] <nhaines> matv1: what RAOF said.
[01:03] <matv1> mhm
[01:03] <matv1> alright. lets wait and see
[01:04] <nhaines> matv1: if you have some alternate ideas for how to improve toolbar discovery, please post on the mailing list.  :)
[01:04] <nhaines> (I don't like the current behavior, but I don't have any suggestions, either.)
[01:05] <matv1> nhaines I will think about it certainly
[01:05] <nhaines> matv1: great.  :)
[01:06] <matv1> still another Q : i was abraod the other day. I found no way of getting dataroaming to work. Is that a known bug? didnt see anything on LP but maybe i missed it
[01:06] <FuuqUmist> when is ubuntu touch finally going to be released?
[01:06] <FuuqUmist> like on new devices
[01:06] <principiante_> My ipad 2, just on and the setup screen appears and asks me to connect to itunes. I connect to itunes and asks me the apple id and password. This second ipad buy it online and not the apple id and password.
[01:07] <nhaines> FuuqUmist: that is up to each individual hardware vendor to announce and decide.
[01:08] <nhaines> matv1: that's a good question!  I just don't know about that one.  It's probably worth filing a bug or posting about on the ubuntu-phone mailing list, because it's easily overlooked but an important feature.
[01:09] <RAOF> Yeah. Data roaming is not going to be tested by everyday use :)
[01:09] <matv1> mhaines. okay i will. I did bug reports on LP before but they took ages to even get triaged though
[01:10] <matv1> is the mailing list better for that?
[01:10] <nhaines> matv1: this is a feature request, probably against ubuntu-system-settings.  It's just a tracking bug, but make sure to post about it too.  :)
[01:10] <matv1> nhaines okay
[01:11] <matv1> nhaines. a feature request?? are you sure?
[01:11] <matv1> all the settings to sugest it should work are there
[01:11] <matv1> They just dont work
[01:11] <matv1> for me
[01:12] <matv1> are those config settings just placeholders?
[01:12] <matv1> I thought we didnt do that anymore?
[01:12] <nhaines> Yes, place holders until they can be integrated into the backend, and not everything is even possible yet.
[01:13] <matv1> nhaines I see. thank you
[01:13] <nhaines> If it's important to you, I'd get on the mailing list and ask about it.
[01:15] <principiante_> Thank you guys.
[01:16] <matv1> i am assuming you live in the states :) when you live in europe dataroaming will be a must have for very many people imo
[01:16] <matv1> i will get it on the mailing list
[01:23] <nhaines> matv1: yes, the last time I was out of the country, I made sure data roaming was off (a very important feature!) but now that T-Mobile has free international roaming data, the next time I am out of country I will want to have it on (equally important feature! ;) ).
[01:27] <matv1> nhaines: agree! thnks again, I will get both points on the mailing list tomorow
[01:40] <GMAN> I'm running Ubuntu 13.10 64 bit. I tried installing the fastboot package for installing on the phone and got the following error
[01:40] <GMAN> ubuntu@ubuntu:~$ sudo apt-get install phablet-tools android-tools-adb android-tools-fastboot Reading package lists... Done Building dependency tree        Reading state information... Done Package android-tools-adb is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source  Package android-tools-fastboot is not available, but is r
[01:42] <GMAN> How do you install the phablet tools?
[01:48] <gnuts> News says nexus 7 (2013) will be supported, install page says nexus 7 (2013) is not supported, which is true?
[01:48] <nhaines> gnuts: both are true.
[01:48] <gnuts> righteous.
[01:49] <nhaines> Nexus 7 (2013) testing has been ongoing for two or three weeks now, and is not finished.
[01:49] <gnuts> I'm thinking of buying one for this, sounds like 2013 is the way to go.
[01:50] <gnuts> is there a preview to play with?
[01:50] <nhaines> If you are going to buy a tablet, yes, 2013 is the way to go.  (Also: the only one on sale.)
[01:51] <gnuts> yes, but one can always pick up older hardware
[01:51] <gnuts> nhaines: thank you.
[01:52] <nhaines> gnuts: yes, but I think they're dropping support for the original Nexus.  I know my Galaxy Nexus is about to go.  :(
[01:52] <nhaines> gnuts: https://lists.launchpad.net/ubuntu-phone/msg06116.html
[01:53] <nhaines> Please know that once it's really stable, it'll be featured, so that link will get you Nexus 7 (2013) support, but it may not work very well.
[01:53] <nhaines> Of course, you can always reflash Android at any time.  :)
[01:59] <gnuts> thanks, i found one on craigslist, will go get it and try this out!
[01:59] <nhaines> gnuts: great!  Good luck!  It should be really nice when Ubuntu 14.04 comes out.  :)  (the phone/tablet interface won't be an LTS)
[03:22] <rww> hihi. I followed the instructions at https://lists.launchpad.net/ubuntu-phone/msg06116.html . I sideloaded in (5) and rebooted, but I just get the Google logo and an unlocked padlock. What do?
[04:02] <rww> oh, I redownloaded trusty-preinstalled-touch-armhf.zip and got a different md5sum, let's try that again...
[04:04] <nhaines> rww: must be adaptive technology.
[04:25] <yanboyang_> INFO:phablet-flash:Device detected as /sbin/sh: getprop: not found
[04:25] <yanboyang_> ERROR:phablet-flash:Unsupported device, autodetect fails device
[04:30] <rww> Boo, still getting the Google logo screen with an open padlock, following the instructions at https://lists.launchpad.net/ubuntu-phone/msg06116.html , after step 5 (which I sideloaded in)
[05:37] <return0> Are there any tablets with ubuntu or ubuntu touch preloaded yet?
[05:37] <S-USA|Lubuntu> Nope.
[05:37] <return0> any non-samsung ones which I can easily install it on yet?
[05:39] <bef0rd> nexus 7 but not the last hw release, the older
[05:40] <return0> Dell's new tablet looks REALLY good for ubuntu but there's no driver suprt :-/
[05:41] <return0> And all those damn tegra things :-/
[05:41] <return0> BLACKBERRY WHY YOU LOCK PLAYBOOK? They was stupid, people would ewat those up for andriod and ubuntu
[06:01] <SonikkuAmerica> rsalveti: Long shot, but are you there?
[07:32] <tvoss> pitti, good morning :)
[07:33] <pitti> hey tvoss, wie gehts?
[09:35] <kaimast> can i disable haptic feedback somehow? it is pretty annoying
[09:53] <dikwan> hye
[10:06] <timppa_> latest trusty seems to buggy!? Cannot open any software, settings etc...
[10:07] <pitti> tvoss: I prepared a MP for the crash we discussed last week, now that location-api and platform-api are healthy again
[10:07] <pitti> https://code.launchpad.net/~pitti/platform-api/crash-without-hw/+merge/204838
[10:09] <ogra_> timppa, known and being fixed
[10:10] <timppa> ok, good! :) How can I update it once it is fixed?
[10:10] <ogra_> commandline ;)
[10:11] <timppa> ogra_: ok, it's fine
[10:11] <ogra_> system-image-cli -v (note that the download doesnt have any output, just wait patiently)
[10:11] <tvoss> pitti, yup, thank you ...
[10:12] <timppa> ogra_: any eta on new image?
[10:12] <ogra_> pitti, btw, your nbd issue ... what i did in the past was running an nbd server as a user with a port around 8000 and then connecting an nbd-client to localhost to the same port ...
[10:13] <ogra_> pitti, that used to give me full control over the device
[10:13] <pitti> ogra_: ah, I think I experimented with that, but it didn't get me that far; but thanks for pointing out, I'll try that again
[10:13] <ogra_> timppa, not yet, hopoefully throughout the day
[10:13] <pitti> ogra_: libguestfs is a rather heavy solution, I doubt that we can easily get it installed in DCs
[10:14] <ogra_> pitti, not sure if wouter hasnt probably locked that down nowadays though
[10:14] <timppa> ok, I think I'll need to swap my sim to another phone... :/ First time since 13.10 release...
[10:14] <ogra_> (seems rather like a security hole)
[10:15] <pitti> ogra_: how so?
[10:15] <pitti> ogra_: I mean, I have the raw image accessible to my user already; but it's compressed, so you need the qemu logic to decode that
[10:16] <ogra_> well i havent made up any attack idea :)
[10:16] <ogra_> just smells a bit fishy to be able to work around a system restriction (only root can mount nbd usually)
[10:17] <pitti> ogra_: yes; my guess is that with nbd-client you wouldn't mount them in the first place, but directly talk to the daemon
[10:17] <ogra_> nbd-client just creates a new node in /dev ...
[10:17] <tvoss> asac, just had the terminal tests passing
[10:17] <ogra_> but using the way above, owned by the user running nbd server
[10:26] <asac> tvoss: nice one
[10:31] <kaimast> anybody has an idea waht could be the cause of this: https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1276373
[10:32] <ogra_> kaimast, thats why we dont support dist-upgrade on the resdonly images
[10:32] <ogra_> *readonly
[10:33] <ogra_> (dpkg uses hardlinks when replacing files ... hardlinks dont work across partition boundaries)
[10:33] <kaimast> yeah i suppose i have to wipe the phone :/
[10:36] <ogra_> sorry, but i have to wontfix it ...
[10:37] <ogra_> (you could reopen it as whishlist against system-image perhaps, but since it is caused by a low level design decision i dont think there is any fix planned unless we probably change the image design)
[10:40] <kaimast> nah its okay
[10:40] <kaimast> i had this problem taht when i wanted to update cyanogenmod it always booted into ubuntu
[10:41] <ogra_> i think xnox told me there are future plans (probably in the far future though) to make it work by using a dpkg overlay
[10:41] <kaimast> i thought it may be resolved by a more recent version of ubuntu touch, but OTA updates didn work
[10:41] <kaimast> that would be cool. especially for unsupported devices
[10:41] <kaimast> thanks anways
[10:43] <kaimast> will install the update via fastboot and hope that this works
[10:43] <ogra_> kInOzAwA, regarding your other bug btw ... i think unity8 doesnt work with SF anymore
[10:43] <ogra_> err
[10:43] <ogra_> kaimast, ^^^^
[10:43] <ogra_> sorry kInOzAwA
[10:44] <kaimast> yeah i guess
[10:44] <kaimast> using mir on Gnexus is painful
[10:44] <ogra_> the wonderful world of PVR graphics
[10:44] <ogra_>  :)
[10:52] <kaimast> yay the cyanogenmod update worked. at least i can use android again (dist-upgrade also broke that :) )
[11:02] <davmor2> Morning all
[11:21] <mhr3_> ogra_, ehm, i just OTA updated and now the bootloader is asking me weird things, is that expected?
[11:22] <mhr3_> it's asking me "ROM may flash stock recovery on boot. Fix?"
[11:22] <ogra_> what does it ask you ? be careful if it wants to take you out to dinner or something ...
[11:22] <ogra_> via OTA ?
[11:22] <ogra_> thast weird
[11:23] <ogra_> i didnt have that on my upgrade 2h ago
[11:23] <mhr3_> the whole OTA process looks different though
[11:23] <mhr3_> but that is probably just UI change
[11:23] <ogra_> mhr3_, what device is that and from which image version did you come ?
[11:23] <mhr3_> mako, trusty-proposed from yesterday
[11:23] <ogra_> yeah, i had the nice new UI too here
[11:24] <mhr3_> ogra_, it's a new device though, first time OTAing on it
[11:24] <ogra_> the install should have put in the right recovery
[11:24] <ogra_> btw, the image you are upgrading to is broken
[11:24] <ogra_> (apps wont start at all)
[11:24] <mhr3_> ah.. great :P
[11:24] <tvoss> asac, didrocks, sil2100 found the issue: dbus-cpp is compiled with gcc 4.8 while location service is 4.7. Need to adjust dbus-cpp to compile against 4.7 now
[11:25] <ogra_> tvoss, why not the other way round ?
[11:25] <mhr3_> ogra_, anyway, i guess i just tell it that it's ok?
[11:26] <ogra_> mhr3_, well, if it breaks you need to re-flash ... no biggie i guess
[11:26] <tvoss> ogra_, because platform-api is stuck with 4.7
[11:26] <sil2100> tvoss: so, would it be enough that we rebuild location-service with gcc 4.8? Or do we need platform-api be rebuilt with 4.8 as well?
[11:26]  * ogra_ isnt sure what "stock recovery" means in that context ... you need the ubuntu recovery 
[11:27] <tvoss> sil2100, that would require platform-api to be transitioned to 4.8, too. Easier to adjust dbus-cpp to be compiled with 4.7
[11:27] <ogra_> sil2100, well, there might be a reason for platform-api keeping 4.7 (it stretches into the android side iirc)
[11:27] <ogra_> better wait for ricmm and rsalveti to be around
[11:27] <sil2100> ogra_: ok
[11:28] <mhr3_> ogra_, hm, well, things seem to work... minus the launching of the apps
[11:28] <ogra_> for the time being i think tvoss has the right plan ...
[11:28] <sil2100> tvoss: so... let's rebuild dbus-cpp then
[11:28] <ogra_> will just be one more package to transition
[11:28] <tvoss> sil2100, on my way
[11:28] <tvoss> sil2100, dpkg-buildpackage running on host
[11:28] <sil2100> tvoss: thanks! Nice catch!
[11:28] <tvoss> sil2100, asac, didrocks it is reproducible on the host, too
[11:28] <ogra_> mhr3_, for the next upgrade: adb shell system-image-cli -v ... and be patient, the download doesnt print anything
[11:29] <mhr3_> ogra_, does that enable some extra logging?
[11:29] <ogra_> mhr3_, -v does, but not for the download manager, only for system-image itself
[11:30] <mhr3_> ogra_, right, hopefully i won't forget :)
[11:35] <OttOmanTR> ogra_: Is there any Ubuntu Touch phone announced?
[11:36] <OttOmanTR> I was expecting something in CES 2014
[11:40] <asac> tvoss: thats the reason for the looping?
[11:40] <asac> do you know why?
[11:41] <asac> feels like it shouldnt cause troubles to combine 4.7 and 4.8 binaries
[11:41] <ogra_> OttOmanTR, nope, not yet
[11:43] <tvoss> asac, it's not looping, there is an abi mismatch for libstdc++, testing locally that building everything with gcc 4.7 actually fixes the issue
[11:44] <asac> tvoss: really? feels like something we might want to investigate
[11:44] <tvoss> asac, we already know about that issue, and yes, transitioning platform api to 4.8 is a long-standing task
[11:45] <asac> tvoss: who is "we" ?
[11:45] <asac> doko? steve?
[11:46] <tvoss> asac, we as in phonedations, and an abi mismatch and issues arising from mixing gcc versions is kind of expected
[11:46] <asac> i am not sure all agree with that :)
[11:46] <asac> we should run that through slangasek and doko
[11:46] <tvoss> asac, sure, happy to put that on my plate
[11:46] <asac> lets see when he gets on
[12:39] <asac> tvoss: #ubuntu-devel :)
[12:49] <nocomp> hi
[12:49] <nocomp> anybody here confident with the emulator?
[12:49] <nocomp> i have an issue when i run the mka command
[12:49] <nocomp> following these instructions
[12:50] <nocomp> https://wiki.ubuntu.com/Touch/Emulator
[12:50] <ogra_> in the ubuntu emulator ?
[12:50] <nocomp> hi ogra_
[12:50] <nocomp> i get this error
[12:50] <ogra_> note that wikipages might be outdated :)
[12:50] <nocomp> /usr/bin/ld: cannot find -lGL
[12:50] <nocomp> collect2: error: ld returned 1 exit status
[12:50] <nocomp> make: *** [/home/nocomp/ubuntutouch/emulator/out/host/linux-x86/obj/lib/libGLES_CM_translator.so] Error 1
[12:50] <FuLgOrE_> hi guys. I'm trying to get sound working on N5. I followed the porting guide on 'https://wiki.ubuntu.com/Touch/Porting' and created the right path with the correct named conf-file. i also copied the 'hifi' and 'voicecall' file. what should I do now? i guess I should modify the 'hw:....' sections. any ideas how I can set the right values? maybe one of the N5 guys here (Tassadar cwayne rsalveti shiggitay)?
[12:50] <nocomp> never had an error in the whole process before
[12:51] <nocomp> been ggogleing this error
[12:51] <nocomp> no logs nowhere
[12:51] <nocomp> :/
[12:52]  * ogra_ has never built the emulator ... i'm a lazy bastard and just use the binaries
[12:52] <ogra_> probably rsalveti can shed some ligt
[12:52] <ogra_> *light too
[12:52] <nocomp> you mean there is another alternative for run the emulator?
[12:52] <ogra_> err, indeed
[12:52] <nocomp> hmm
[12:53] <rsalveti> /usr/bin/ld: cannot find -lGL
[12:53] <rsalveti> that means you don't have a valid GL driver in your host
[12:53] <nocomp> :/
[12:53] <nocomp> i tried this
[12:53] <ogra_> http://davidplanella.org/ubuntu-emulator-quickstart-guide/
[12:53] <rsalveti> do you have a broken nvidia/ati driver installation?
[12:53] <rsalveti> otherwise that would be fixed by installing the mesa drivers
[12:54] <nocomp> sudo apt-get install ubuntu-emulator
[12:54] <rsalveti> libgl1-mesa-glx
[12:54] <nocomp> E: Unable to locate package ubuntu-emulator
[12:54] <nocomp> oki
[12:54] <nocomp> i try
[12:54] <nocomp> thxx ogra_
[12:54] <nocomp> Use 'apt-get autoremove' to remove them.
[12:54] <nocomp> 0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
[12:54] <nocomp> nocomp@pirebox:~/ubuntutouch/emulator$
[12:54] <ogra_> nocomp, hmm, i thought that was in some PPA for non-14.04 users
[12:55] <nocomp> hmmm
[12:55] <nocomp> lemme check
[12:55] <nocomp> thxxx
[12:55] <ogra_> "Alternatively, if you are running a stable release such as Ubuntu 13.10, you can install the emulator by manually downloading its packages first:
[12:55] <ogra_> "
[12:55] <ogra_> click on the "show me how"
[12:55] <ogra_> it will show you how ;)
[12:55] <nocomp> oki i ll have a look
[12:55] <nocomp> thxxx
[12:56] <nocomp> where do you see that ogra_  ?
[12:56] <ogra_> nocomp, on the blogpost
[12:56] <nocomp> k
[12:57] <ogra_> in the "installing the emulator" paragraph
[13:00] <FuLgOrE_> does anybody know how to exchange one word with another one in a text file in a very simple way?
[13:00] <nocomp> FuLgOrE_, with text editor find and replace
[13:01] <FuLgOrE_> ah, I'll do that with adb push and pull. should be the easiest way for me
[13:02] <FuLgOrE_> then I can use gedit for find&replace
[13:02] <ogra_> you could use sed ... but if you are not used to it it can cause more damage than being helpful
[13:05] <Tassadar> FuLgOrE_: did you manage to convince WiFi not to get new mac address every time?
[13:05] <ogra_> sergiusens, are you back today ? (i thought you were off til end of the week)
[13:07] <sergiusens> ogra_, nope, just yesterday; that's ji
[13:07] <sergiusens> jim
[13:07] <FuLgOrE_> Tassadar: no, I didn't. First try was to add the /persist path to fstab. It mounted correctly but I guess too late. Second I used an updated system and deleted everything below SWAP in fstab to let it recreate automatically. this made the same. It mounts too late. than I unmounted the /persist and created the /persist/wifi/.macaddr in the / mount point
[13:07] <FuLgOrE_> nothing helped
[13:08] <FuLgOrE_> but rsalveti is working on a fix
[13:08] <rsalveti> yup, still in progress
[13:08] <rsalveti> doing many things in parallel
[13:08] <ogra_> sergiusens, well, then i'll hand off fixing bug 1275690 to you (i was planning to look into it later today)
[13:08] <rsalveti> also trying to publish the entire source code
[13:08] <FuLgOrE_> my last try could have failed because I maybe used the wrong .macaddr file (I created one by myself, a simple text file)
[13:09] <FuLgOrE_> and my linux knowledge is very limited
[13:10] <sergiusens> ogra_, why is that critical anyways? It's a non supported use case and for read only only?
[13:10] <ogra_> sergiusens, well, the QA team hacked together weird scripts to work around it for their Qt 5,2 testing ...
[13:10] <ogra_> we should make sure to have the package DTRT ...
[13:11] <ogra_> and its a trivial task of renaming the files
[13:11] <rsalveti> would be nice to get that fixed for a clean QA and transition
[13:11] <sergiusens> oh well
[13:11] <ogra_> sergiusens, http://pastebin.ubuntu.com/6826187/
[13:13] <sergiusens> rsalveti, wrt to clean transition, shouldn't they be building an image with the ppa added?
[13:13] <ogra_> sergiusens, working on that
[13:13] <ogra_> there is no tool to do that atm
[13:14]  * ogra_ is finishing the rootstock system-image support today
[13:14] <ogra_> and i'll provide them images then
[13:15] <rsalveti> sergiusens: yup, but we need to make sure people can test it without any hacks before we do the switch
[13:15] <sergiusens> Sorry, something just went wrong in Launchpad.
[13:15] <ogra_> yeah
[13:15] <sergiusens> when opening the bug link :-P
[13:15] <rsalveti> it's giving a lot of timeouts
[13:15] <ogra_> db server upgrade
[13:15] <ogra_> the fallback machine is slow ... should be better soon
[13:16] <rsalveti> actually, it's down now
[13:18] <ogra_> sergiusens, well,, my comment just says that the postrm files need to be moved to prerm files ... (simple rename) since else the dpkg-divert --remove runs after the files are gone ... which will cause the diversion to stay
[13:18] <ogra_> (no need to open the bug for that ;) )
[13:19] <sergiusens> ogra_, right; I can't branch the pkg branch either :-P
[13:19] <ogra_> hah
[13:21] <om26er> sil2100, ping
[13:23] <om26er> didrocks, hey! is there a new image to test today ?
[13:23] <om26er> or are we testing a new image ?
[13:23] <FuLgOrE_> rsalveti: regarding the wifi bug on N5. do you already have an idea how to fix that? do you think to recursive copy the /persist mmc... to the / mount point would temporary fix that?
[13:25] <sil2100> om26er: hi!
[13:25] <FuLgOrE_> ups... I shouldn't have made updates today. now I also have the problem that no app can work anymore :-/
[13:25] <om26er> sil2100, same question, are we testing a new image ?
[13:26] <sil2100> om26er: so, actually the current image is badly broken, so no testing until we get a new one with all the fixes built
[13:26] <sil2100> om26er: we still wait for dbus-cpp fix from tvoss
[13:27] <om26er> sil2100, so in a few hours ? or tomorrow ?
[13:27] <sil2100> om26er: I would say in a few hours even (we hope)
[13:29] <om26er> sil2100, asked since its a national holiday here and I came in to check if there is an image to test, so I guess I can relax ;)
[13:33] <nocomp> raaaaaaaaaa can t find the bloody ppa
[13:33] <nocomp> drives me mad
[13:33] <mardy_> Laney: hi! Do you think there is a chance of getting the latest syncevolution (1.3.99.7) to Ubuntu Touch (I guess it will need to hit the desktop as well, then)?
[13:34] <ogra_> nocomp, what ppa ?
[13:35] <Laney> mardy: ummmmm is it a development release?
[13:37] <mardy> Laney: mmm... it actually seems to be unreleased, let me check...
[13:37] <nocomp> ogra_, for install the emulator
[13:38] <ogra_> nocomp, didnt you read the page i gave you ?
[13:38] <ogra_> http://davidplanella.org/ubuntu-emulator-quickstart-guide/
[13:38] <nocomp> you didn t gave me the page and couldn t find it
[13:38] <mardy> Laney: so, it has been released on January 22nd; it's the last release candidate before 1.4
[13:38] <nocomp> thxx i read
[13:38] <ogra_> scroll to "Installing the emulator"
[13:39] <nocomp> i check
[13:39] <ogra_> then click on "show me how"
[13:39] <nocomp> thxxxx
[13:39] <ogra_> follow the 11 steps that expand when you click on "show me how"
[13:39] <ogra_> (no PPA involved in that)
[13:43] <popey> dpm: du -a /var | sort -n -r | head -n 10
[13:44] <nocomp> perfect ogra_  seems to work
[13:44] <nocomp> thxx a lot!
[13:44] <ogra_> welcome
[13:46] <FuLgOrE_> simply to copy the 3 ucm config files and exchange the hardware name to the correct one was a stupid idea. it didn't work. Is there a way so copy something from android or cyanogenmod to get sound working? how knows something about the UCM files?
[13:46] <FuLgOrE_> -so+to
[13:46] <oSoMoN> Mirv, hey, seen my e-mail about a fix for the crash in QtWebKit 5.2 ?
[13:47] <ogra_> FuLgOrE_, the only person that knows UCM in and out is diwic ... and he is really busy with other stuff
[13:47] <ogra_> FuLgOrE_, and android uses a different sound system
[13:47] <ogra_> so copying anything over wont help
[13:48] <FuLgOrE_> ogra_ thanks for the information. what a pitty. so it will take a while for an unsupported device to get such things working, I guess :-/
[13:48] <ogra_> well, open a bug, attach amixer output etc to it ...
[13:48] <ogra_> (there is a debugging alsa wikipage somewhere)
[13:49] <ogra_> probably diwic finds the time to look into it if he has all data available easily
[13:49] <FuLgOrE_> so nobody will be unhappy if I open a bug special for unsupported hardware?
[13:49] <ogra_> nah
[13:49] <ogra_> open it against alsa-lib
[13:49] <ogra_> and mention UCM in the description
[13:54] <mardy> Laney: I talked to the maintainer now, he plans to release SyncEvolution 1.4 in 1-2 weeks
[14:02] <mardy> bfiller: hi! Do you have some minutes to chat about SyncEvolution (here in IRC is good)
[14:02] <sergiusens> rsalveti, https://code.launchpad.net/~sergiusens/phablet-extras/postrm_fix/+merge/204948
[14:02] <rsalveti> sergiusens: did you test doing the manual upgrade?
[14:03] <ogra_> sergiusens, i'm pretty sure you need to do it in prerm because else your files are gone
[14:03] <rsalveti> right
[14:03] <sergiusens> rsalveti, so want me to add the script ogra gave me without the force?
[14:03] <ogra_> script ?
[14:03] <rsalveti> the pastebin
[14:03] <rsalveti> but basically, yeah
[14:03] <nocomp> RAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[14:03] <ogra_> i only wanted to show you the gross hack they use :)
[14:04] <nocomp> emulator: Kernel parameters: qemu.gles=1 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.console=ttyS2 ndns=1
[14:04] <nocomp> emulator: Trace file name is not set
[14:04] <nocomp> qemu: could not load initrd ''
[14:04] <nocomp> emulator: User configuration saved to /home/nocomp/.android/emulator-user.ini
[14:04] <nocomp> exit status 1
[14:04] <nocomp> nocomp@pirebox:~/ubuntutouch/packages-emulator$
[14:04] <sergiusens> ogra_, rsalveti read my bug comment, postrm should be fine
[14:04]  * nocomp go hang himself
[14:04] <kgunn> hey guys..anyone having manta charging issues ?
[14:04] <rsalveti> kgunn: you need the right charger, that gives 2A
[14:04] <ogra_> kgunn, not with the right charger
[14:04] <kgunn> i'm using the one that came with it
[14:05] <rsalveti> sergiusens: just trying installing your newer package then and remove it right after
[14:05] <kgunn> ok, weird...just a bug...as soon as i unplugged the ui corrected to 100% :)
[14:05] <sergiusens> rsalveti, ogra_ also https://wiki.debian.org/Adding%20and%20removing%20diversions ... I guess I might need both for upgrade support
[14:05] <ogra_> sergiusens, well, that one failong --remove wouldnt explain why all the other diverts are still there
[14:05] <rsalveti> yeah
[14:05] <sergiusens> ogra_, let me run the pastebin without the hack
[14:06] <ogra_> ignore the pastebin ... they run it without the packages installed at all
[14:06] <ogra_> (they dpkg --force-all remove them)
[14:06] <sergiusens> ogra_, yea, was going to do it withtout that part
[14:07] <nocomp> ogra_,  if it s your website you linked me
[14:07] <nocomp> there is an error
[14:07] <sergiusens> ogra_, rsalveti there is no upgrade path for qtmultimedia-touch; we just need to remove it for using the newer qt stuff
[14:07] <ogra_> sergiusens, from the debian page: "In postinst and prerm, remove the diversion."
[14:07] <nocomp> replace ubuntu-emulator run myinstance by sudo ubuntu-emulator run myinstance
[14:07] <sergiusens> ogra_, yeah, that's what I said
[14:08] <ogra_> so just mv'ing your postrm files to prerm should do
[14:08] <sergiusens> ogra_, but prerm should be needed for upgades
[14:08] <ogra_> (and fixing the one false one)
[14:08] <sergiusens> ogra_, cping instead I suppose
[14:08] <ogra_> nocomp, its not mine ...
[14:08] <nocomp> ok
[14:09] <ogra_> nocomp, it is dpm owning that blog
[14:09] <ogra_> sergiusens, cping would leave the postrm ... you dont need it
[14:09] <bfiller> mardy: hey, sure what's up?
[14:09] <nocomp> i ve left a comment
[14:09] <nocomp> thxxx
[14:10] <mardy> bfiller: so, SyncEvolution 1.4 (which contains the patches we need) will be released in 1-2 weeks
[14:10] <mardy> bfiller: I believe that this means that it can be in 14.04
[14:10] <dpm> nocomp, ogra_, which blog?
[14:10] <mardy> bfiller: for the time being though, we need to find a way to let you and renato use it
[14:11] <ogra_> dpm, the emulator quickstart guide
[14:11] <dpm> ah, ok, what's up with it, something not working?
[14:11]  * ogra_ hasnt tried the non trusty stuff ... since i am on trusty where it works 
[14:11] <mardy> bfiller: do you have a PPA where I can put the package?
[14:11] <ogra_> dpm, nocomp says there are issues
[14:11] <ogra_> no idea which
[14:11] <dpm> ok, nocomp, let me know if I need to update anything
[14:12] <bfiller> mardy: yes
[14:12] <bfiller> mardy: how about phablet-team ppa
[14:12] <mardy> bfiller: if you don't want to rely on a PPA, I can try to backport the patches, but it might not be that easy, because there are several of them and I'm not sure if they rely on newer changes
[14:12] <bfiller> mardy: https://launchpad.net/~phablet-team/+archive/ppa
[14:12] <Laney> mardy: want to wait for that?
[14:12] <bfiller> mardy: think uploading to ppa would be great so it's easier for us to test
[14:13] <Laney> pre-release in a PPA, final in distro sounds good
[14:14] <mardy> Laney: yes, since bfiller seems to be fine with using a PPA for the time being, the best thing is probably to wait for the 1.4 release
[14:14] <Laney> nod, thanks
[14:15] <mardy> bfiller: OK, then I'll work on packaging it for the PPA
[14:16] <Tassadar> FuLgOrE_: putting that /persist/wifi/.somethingmacaddress file into initrd.img "fixes" the wifi, but it's just a workaround
[14:16] <xnox> http://developer.ubuntu.com/apps/qml/ appears to have broken icons.
[14:16] <bfiller> mardy: thank you
[14:16] <xnox> can i use qtcreator designer to drag and drop ubuntu qml components?
[14:18]  * ogra_ wouldnt have thought xnox is a drag'n drop programmer :)
[14:19] <xnox> ogra_: all changes i did to ubiquity i did in glade, no way i'm writting .xml by hand.
[14:19] <xnox> ogra_: qml by hand is not that hard, but still is a pain to layout.
[14:19] <xnox> ogra_: especially, when i don't know how it's going to look like.
[14:20] <ogra_> yeah, i guess if the UI is complex that makes sense
[14:20] <FuLgOrE_> Tassadar: thx. where to find the initrd.img? I have the 3 img-files boot recovery and system. and I also have the zip file with the shell script and the tar.gz container with the folder structure. I guess I should modify the ubuntu-touch zip, right?
[14:20] <Tassadar> no
[14:21] <Tassadar> one of the files is boot.img, right? Are you on Ubuntu system?
[14:21] <FuLgOrE_> yes
[14:21] <FuLgOrE_> twice yes :)
[14:21] <Tassadar> sudo apt-get install abootimg
[14:21] <Tassadar> you can unpack the boot.img by invoking abootimg -x boot.img
[14:23] <FuLgOrE_> thx for the idea. I will read the man page from abootimg. I'll have a look. right now I try to create a bug for the sound issue but I need internet. because the touch-keyboard is crashed I cannot enter my wifi code -.- because I don't want to modify the config file every reboot I will try to fix the wifi thing first, thx :)
[14:25] <Tassadar_> FuLgOrE_: random freezes, yaay. this notebook is probably dying already. What was the last message I sent in here?
[14:25] <FuLgOrE_> you can unpack the boot.img by invoking abootimg -x boot.img
[14:25] <nocomp> damm emulator is quite buggy :/ setting menu doesn t work :/
[14:26] <FuLgOrE_> that was my last message:
[14:26] <FuLgOrE_> thx for the idea. I will read the man page from abootimg. I'll have a look. right now I try to create a bug for the sound issue but I need internet. because the touch-keyboard is crashed I cannot enter my wifi code -.- because I don't want to modify the config file every reboot I will try to fix the wifi thing first, thx :)
[14:26] <sergiusens> Mirv, hey, word is we still need to maintain the qtmultimedia touch package; there is no upgrade path for that one since the amount of diversions needed is crazy; I'll work on a branch to get an upgrade path; in the meantime there's a patch so at least dist-upgrade doesn't break
[14:26] <Tassadar_> FuLgOrE_: it even has abootimg-unpack-initrd  and abootimg-pack-initrd, which you can use to edit the initrd
[14:27] <renato> mardy, this package will contains the service files?
[14:27] <ogra_> FuLgOrE_, to get your wlan settings from a laptop to the phone, use phablet-network
[14:27] <ogra_> it will push the existing setup over to the phone
[14:27] <Tassadar_> when you're done, just pack the initrd and then update the bootimg via abootimg -u boot.img -r initrd.img
[14:27] <ogra_> no need to rely on the onscreen kbd
[14:28] <FuLgOrE_> ogra_: phablet don't works for me now and I was not checking why, until now
[14:31] <cyphermox_> didrocks: https://code.launchpad.net/~mathieu-tl/dbus-cpp/properties-cpp-dev-depends/+merge/204959
[14:33] <FuLgOrE_> Tassadar: after extracting boot.img I also get zImage and a bootimg.cfg. don't I have to include them in the command to pack the boot.img again?
[14:35] <ogra_> FuLgOrE_, just use the abootimg update function (see manpage) to update the pieces in the boot.img
[14:35] <ogra_> ignore what you dont need
[14:35] <FuLgOrE_> so I guess the cfg-file is the kernel command line. so I could fix the long booting time with your instruction as well :D
[14:35] <FuLgOrE_> ogra_ i will check, thx :)
[14:37] <Tassadar_> FuLgOrE_: right)
[14:38] <Tassadar_> you might need to remove bootsize option from that .cfg file, abootimg is a bit unintuitive in this - it fails to create new boot image if the size differs, and well, it's gonna be different if you change it
[14:39] <FuLgOrE_> ok thx
[14:40] <Mirv> sergiusens: ah, ok, good to know. I did notice music playback wasn't seem to work (audiosink missing) with the new 5.2 stock qtmultimedia
[14:41] <FuLgOrE_> is there a reason to use maxcpus=2 on a quadcore cpu?
[14:43] <Tassadar_> FuLgOrE_: it may be just for boot or somethig, it certainly doesn't disable those two cores or something like that
[14:45] <sergiusens> Mirv, I was hoping we  wouldn't need an upgrade path for this package; but we're still not ready
[14:47] <mardy> renato: no. If you send me the link to the repository with your wrapper application, I can make a merge request with those files
[14:48] <renato> mardy, ok, I do not have it yet :D, but I will send it to you as soon I create it
[14:53] <FuLgOrE_> Tassadar: my boot.img is too small. Do you know how to make it bigger?
[14:53] <FuLgOrE_> boot.img: updated is too big for the Boot Image (10637312 vs 10629120 bytes)
[14:54] <Tassadar_> did you remove that bootsize from that .cfg file?
[14:57] <Tassadar> FuLgOrE_: you might need to add that bootimg.cfg to abootimg via "-f bootimg.cfg"
[14:57] <FuLgOrE_> I did that already
[14:59] <FuLgOrE_> I'm thinking about generating a new boot.img but the manpage tells me something about a stage2.img. I'm not sure if the boot.img can be too big or that I can simply create a new and bigger boot.img
[14:59] <Tassadar> okay, try it with create - bbootimg --create boot-new.img -f bootimg.cfg -k zImage -r initrd.img
[14:59] <Tassadar> abootimg is just silly like that - it probably takes old bootsize from the existing boot.img, even though it is not specified in that config
[15:00] <FuLgOrE_> ok, I will search for bbootimg :)
[15:01] <Tassadar> no, abootimg
[15:01] <Tassadar> sorry, typo)
[15:01] <FuLgOrE_> oh :D
[15:01] <Tassadar> I'm used to typing bbootimg, because that's what I use, but you should be fine with abootimg)
[15:01] <FuLgOrE_> I just also realized that while googling :D
[15:01] <FuLgOrE_> oh I didn't found any bbootimg
[15:01] <FuLgOrE_> I'll try --create with abootimg
[15:02] <Tassadar> I needed abootimg's functions as C library, so I wrote myself libbootimg, and bbootimg is a cli wrapper for it's functions. It is mostly compatible with abootimg, but uses that libbootimg I wrote.
[15:04] <SBS> I own Samsung Galexy GT-S7562. (S Duos). Can I install Ubuntu Touch on my phone?
[15:05] <SBS> Is any body there?
[15:05] <FuLgOrE_> SBS: !devices
[15:05] <FuLgOrE_> damn
[15:05] <FuLgOrE_> !devices
[15:06] <FuLgOrE_> Tassadar: sounds good, but I don't understand much from what you wrote ;)
[15:07] <SBS> There only Nexus mobile are listed. No other make is in the list
[15:07] <Tassadar> I simply rewrote abootimg because I needed to use it slighty differently and called it bbootimg, not that interesting really, just explaing why I typed bbootimg)
[15:08] <SBS> Does Ubuntu touch support Samsung Galexy GT-S7562?
[15:09] <ogra_> SBS, check the devices wikipage ... if it is not in the table there you might need to port it yourself
[15:12] <FuLgOrE_> nice :)
[15:12] <FuLgOrE_> booting is very fast now. thanks, Tassadar, ogra_ !
[15:13] <FuLgOrE_> I'll check the mac
[15:13] <Tassadar> (just a heads up: apt-get dist-upgrade can overwrite your initrd)
[15:13] <ogra_> Tassadar, i disabled that recently
[15:13] <FuLgOrE_> good to know
[15:13] <ogra_> shouldnt anymore
[15:14] <Tassadar> ogra_: so it doesn't flash boot image at all?
[15:14] <ogra_> right
[15:14] <FuLgOrE_> good for me :D
[15:14] <Tassadar> good, I like that)
[15:14] <ogra_> Tassadar, oh, sorry, that was only for the kernel part
[15:15]  * ogra_ just checked his changes ... i mis-remembered 
[15:15] <FuLgOrE_> nice, the mac keeps stable now :))
[15:16] <ogra_> what did you do ?
[15:16] <ogra_> compile the driver as module ?
[15:17] <FuLgOrE_> I copied the .macaddr to my laptop, extracted the boot.img, unpacked the ramdisk, created the path /persist/wifi/ and copied the .macaddr inside. than I packed the ramdisk and created a new boot.img. all according to Tassadars nice description :)
[15:17] <FuLgOrE_> it's just a temporary fix but it works at first :)
[15:18] <FuLgOrE_> at the moment I have 'wlan23' so I'm very happy about that :D
[15:19] <ogra_> ah, k
[15:20] <cwayne_> greyback, hi, are there any logs particularly useful for attaching to sidestage bugs?
[15:20] <mpt> Laney, are you still working on Brightness settings?
[15:21] <Laney> I submitted the merge
[15:21] <Laney> but in general
[15:21] <greyback> cwayne: the $HOME/.cache/upstart/unity8.log could be handy
[15:21] <pitti> ogra_: FTR:
[15:21] <pitti> $ nbd-server 2000 /tmp/overlay.img -d
[15:21] <pitti> Error: Could not set GID: Operation not permitted
[15:22] <ogra_> pitti, ah, as i thought, wouter added some checks
[15:22] <mpt> Laney, ok, I fixed the design for bug 1275699
[15:22] <ogra_> pitti, oh, wait, you need a higher port i think
[15:22] <pitti> 2000 is high
[15:23]  * ogra_ thought the range ends somewhere at 6000
[15:23] <pitti> and setgid() sounds unrelated to the port number
[15:23] <ogra_> indeed
[15:23] <pitti> ogra_: 0-1023 are privileged
[15:23] <ogra_> ah
[15:23] <ogra_> (its a long time that i have fiddled with such stuff)
[15:24] <pitti> ah, but qemu-nbd works as user
[15:25] <pitti> $ nbd-client -l 127.0.0.1 20000
[15:25] <pitti> Negotiation: .Error: It looks like you're trying to connect to an oldstyle server with a named export. This won't work.
[15:25] <pitti> Exiting.
[15:25] <pitti> ah, I slowly remember what made me discard that option back then :)
[15:25] <FuLgOrE_> ogra_: I will open a bug for the sound issue another day, because it's 23:24 in china and I just write down what I did so that I can share the information
[15:26] <ogra_> FuLgOrE_, yeah, no hurry with that
[15:29] <Laney> mpt: thanks
[15:29] <Laney> you chose the change that means I don't have to change anything
[15:33] <sam_> is the nexus 7 any good with ubuntu?
[15:35] <ogra_> sam_, the N7 2013 will soon be our default device
[15:36] <ogra_> (for the 7" class)
[15:36] <sam_> is that gen 2?
[15:36] <ogra_> the latest one, yes
[15:36] <sam_> are all apps available on it?
[15:37] <ogra_> the same apps as on the phone, yes
[15:37] <ogra_> (they use the same appstore)
[15:39] <sam_> so on 14.04 the ubuntu touch will be a stable release?
[15:41] <ogra_> it is already stable enough for daily use ...
[15:41] <ogra_> but still lacking features
[15:41] <sam_> got it.
[15:41] <sam_> thanks ogra_
[15:41] <ogra_> by 14.04 there will be more features :)
[15:43] <FuLgOrE_> so, tomorrow I can publish the instruction about the temporary fix for the wifi bug and the long booting time via mailing list (special thanks to Tassadar :)). Today I cannot send it because the chinese firewall blocks my email address -.-
[15:44] <Tassadar> FuLgOrE_: you live in china?
[15:44] <FuLgOrE_> yes
[15:44] <ogra_> how long was the "long booting" taking ?
[15:44] <FuLgOrE_> around 30 seconds longer, I would say
[15:45] <Tassadar> FuLgOrE_: I'm gonna go there for a week to attend some student competition, I was wondering - how is it with the firewall, can I bypass it via ssh tunnel and not get arrested?
[15:45] <ogra_> what did you do to fix it ?
[15:45] <FuLgOrE_> in dmesg I could see the last entry before the 'break' at around 5.xxx and the next one at around 30.xxx
[15:45] <Tassadar> ogra_: console=tty0 instead of ttyTheSerialConsole
[15:45] <ogra_> oha
[15:45] <Tassadar> UART driver in kernel blocks for 30s if nothing is connected to the physical port
[15:45] <FuLgOrE_> both fixes are from Tassadar (nicht mit fremden Feder schmücken ;-))
[15:46] <ogra_> rsalveti, ^^^
[15:46] <ogra_> we need to take that into account if we provide hammerhead
[15:46] <Tassadar> FuLgOrE_: I'm wondering about the legal aspect and not the technical (as in, I'm not asking if it works, I'm asking if I will get arrested if somebody finds out)
[15:57] <FuLgOrE_> Tassadar: I don't know about the legal aspect but I can tell you that I know no foreigner who was arrested because of bypassing the firewall. It's not made to 'protect' foreigners ;-)
[16:01] <SonikkuAmerica> rsalveti: I followed your call-for-testing instructions to the letter, and my device STILL boots into Android (flo)!
[16:12] <Laney> Could somebody please try to run /usr/share/ofono/scripts/scan-for-operators on their phone?
[16:12] <Laney> on the latest trusty-proposed, preferably
[16:14] <mhall119> bzoltan: dbarth: I put up a temporary warning on developer.u.c about the PPA breakage, please let me know as son as that's fixed so I can take the notice down
[16:14] <rsalveti> SonikkuAmerica: yeah, it's currently broken, trying to get that fixed later today
[16:14] <SonikkuAmerica> rsalveti: OK
[16:15] <bzoltan> mhall119: OK
[16:15] <dbarth> mhall119: will do
[16:17] <mhall119> thanks
[16:23] <josepht> Laney: I've run it on my phone.  Mako with latest trusty-proposed.  I got kicked out of 'adb shell' and my settings screen is solid white now
[16:23] <ogra_> josepht, yes, latest -proposed image is broken
[16:24] <ogra_> if you actually use proposed, i would suggest checking http://ci.ubuntu.com/smokeng/trusty/touch/ before upgrading
[16:24] <josepht> ogra_: Laney asked for someone to run a script, so I did. :)
[16:25] <Laney> josepht: umm!
[16:26] <ogra_> josepht, right, just saying, apps not starting is known for this image
[16:26] <Laney> your screen shouldn't have anything to do with it
[16:26] <ogra_> that too :)
[16:26] <Laney> ogra_: want to try for me?
[16:26] <ogra_> Laney, if i'm near a phone again
[16:26] <popey> Laney: how long does it take to run?
[16:26] <popey> taking a while here
[16:26] <Laney> if it works, like a little while
[16:27] <ogra_> Laney, in a meeting and i dont have the phones in my office
[16:27] <Laney> errors out for me
[16:27] <Laney> ok
[16:27]  * popey is running it
[16:27] <ogra_> in 30min or so i can do
[16:27] <popey> does it need to be run as phablet or root?
[16:27] <popey> ooh, finished
[16:27] <ogra_> root most likely
[16:27] <Laney> http://paste.ubuntu.com/6879940/
[16:27] <Laney> don't think root
[16:27] <popey> http://paste.ubuntu.com/6879941/
[16:28] <popey> \o/ consecutive pastes
[16:28] <josepht> Laney: http://paste.ubuntu.com/6879950/
[16:28] <Laney> so yours works
[16:28] <popey> thats on trusty though
[16:28] <Laney> and yours
[16:28] <ogra_> Laney, root vs phablet
[16:29] <FuLgOrE_> bye
[16:29] <Laney> ogra_: no, it breaks in both cases for me
[16:29] <ogra_> ow
[16:29] <Laney> and I think it worked a few images ago
[16:29] <Laney> (the u-s-s interface didn't though, that broke quite a while back)
[16:29]  * Laney wah
[16:30] <ogra_> shows me my provider just fine here
[16:30] <Laney> on $latest?
[16:30] <ogra_> (well, it did 1h ago)
[16:30] <ogra_> yes
[16:30] <ogra_> with manually installed libprotobuf from this morning
[16:30] <Laney> you mean system-settings -> cellular -> manual -> <click the next listitem>?
[16:30] <ogra_> no
[16:31] <ogra_> just cellular
[16:31] <Laney> oh right
[16:31] <ogra_> it shows my current provider
[16:31] <Laney> it's this page in particular
[16:31] <Laney> the scanning operation
[16:31] <ogra_> ah, k
[16:31] <popey> works on 161
[16:31] <Laney> UI?
[16:31] <davmor2> Laney: reports
[16:31] <davmor2> reported even
[16:31] <Laney> yes, I was looking into fixing it :P
[16:32] <Laney> but then the script stopped working :(
[16:34] <popey> Laney: broke on 162
[16:34] <Laney> the script?
[16:35] <popey> yes
[16:35] <Laney> nod, thanks
[16:35] <popey> np
[16:35] <ogra_> Laney, ofono didnt change in a while though
[16:35] <ogra_> i suspect thats py2 vs py3 or so
[16:36] <ogra_> (162 is from yesterday btw)
[16:36] <popey> Laney: http://paste.ubuntu.com/6879982/ fwiw
[16:38] <Laney> popey: okay, thanks, I'll see what changed
[16:39] <ogra_> Laney, http://people.canonical.com/~ogra/touch-image-stats/20140204.changes
[16:39] <ogra_> funnily nothing that looks relevant
[16:39] <Laney> funny that
[16:39] <Laney> could it be androidy things?
[16:40] <ogra_> no android upload in recent times
[16:40] <ogra_> (we pull from the package, you would see it on the -changes ML)
[16:41] <Laney> yeah...
[16:41]  * Laney groans
[16:41] <ogra_> werid stuff
[16:41]  * Laney looks for someone who works on ofono
[16:42] <ogra_> awe_, ^^^^
[16:42] <ogra_> awafaa, should the ofono scripts usually work reliable ?
[16:42] <ogra_> err
[16:42] <ogra_> awe_, ^^
[16:43] <awafaa> heh, sorry for muddying the waters ogra_ :)
[16:43] <ogra_> heh, sorry for the unrelated ping :)
[16:43] <awe_> Laney, what's the question??
[16:43] <ogra_> awe_, http://paste.ubuntu.com/6879982/
[16:43] <Laney> awe_: We noticed that the scan-for-operators script in ofono is broken
[16:44] <ogra_> awe_, it seems to work in image 161 ... but not in 162 ... http://people.canonical.com/~ogra/touch-image-stats/20140204.changes the changes do not actually indicate that any change could have broken it
[16:44] <awe_> hmmm, we have landed anything new in awhile...
[16:44] <ogra_> yeah
[16:45] <awe_> that's puzzling
[16:45] <ogra_> see the .changes file
[16:45] <ogra_> thats all that changed between the two images
[16:45] <awe_> ogra_, looks like ofono is crashing
[16:45] <ogra_> wow
[16:45] <ogra_> why would it though
[16:45] <awe_> Laney, could you open a bug?  I can certainly take a look at this today, however I have a meeting in 15m
[16:46] <ogra_> unliokely that mir or protobuf could cause that
[16:46] <awe_> ogra_, did we land a new dbus?
[16:46] <ogra_> no, see http://people.canonical.com/~ogra/touch-image-stats/20140204.changes
[16:46] <awe_> ogra_, without examing the crash file and/or syslog, I'd just be guessing
[16:46] <ogra_> that ius effectively the diff between the two images
[16:47] <Laney> awe_: okay, what shall I include?
[16:47] <ogra_> so it is either unreliable since a longer time or ... well ... cosmic rays ... pixiedust ... heisenbugs
[16:47] <awe_> sure, but it could be some kind of race condition, and an earlier change might have caused it
[16:47] <ogra_> yeah
[16:48] <awe_> Laney, device/image #, steps-to-reproduce, /var/log/syslog, and if there's a crash file, and you know how to get a backtrace, that'd be super helpful
[16:48] <Laney> there is no crash file
[16:48] <awe_> hhmmm
[16:48] <ogra_> Laney, do you see ofono running when you get the error ?
[16:48] <Laney> it's still running, yeah
[16:48] <Laney> can I run it in the foreground?
[16:48] <ogra_> (or right before/after)
[16:49] <Laney> root      1892  0.0  0.0   3788  1600 ?        Ss   Feb03   0:09 ofonod -p ril,rilmodem,provision,mbpi,nettime,mnclength,smshistory,push_notification
[16:49] <awe_> Laney, you can, but you need to use the "-n" parameter to prevent it from dropping into the background
[16:49] <Laney> okay, let me try that
[16:50] <Laney> awe_: ofonod[23701]: ril_cops_list_cb: can't allocate ofono_network_operator
[16:51] <awe_> sounds like memory starvation to me
[16:51] <awe_> ogra_, has anyone done any memory usage analysis on touch images recently?
[16:52] <Laney> Mem:          1871       1803         67          1        113        882
[16:52] <Laney> -/+ buffers/cache:        807       1064
[16:52] <ogra_> awe_, nope, but we want to drop swap with the switch to 4.4
[16:52] <ogra_> awe_, that kind of forces one upon us
[16:52] <awe_> yea, but sounds like dropping swap would make it worse, not better...
[16:52] <awe_> I know we have folks looking at performance, boot-time analysis, ...
[16:52] <Laney> woah
[16:52] <ogra_> http://paste.ubuntu.com/6880100/
[16:53] <Laney> I'm actually on image 160
[16:53] <awe_> me thinks someone needs to start watching memory consumption
[16:53] <ogra_> works fine for me on 164
[16:53] <cyb3r> Hello, quick question. Is there any support for the 4.4 radio image?
[16:54] <ogra_> cyb3r, not yet ... we are about to switch to a 4.4 base
[16:54] <ogra_> (then we will even use it)
[16:54] <cyb3r> Great, thanks!
[16:55] <cyb3r> I just installed and an trying to get into the project.
[16:56] <ogra_> cool, well stay around here then :)
[16:57] <cyb3r> Ok, sounds like a good idea.
[17:00] <Laney> awe_: bug #1276699
[17:00] <cwayne_> dpm, hi, just wondering if theres any update on the call for translations?
[17:00] <awe_> Thanks Laney!
[17:01] <Laney> np
[17:16] <cyb3r> Thanks ogra_. Just joined with my freenode account.
[17:23] <Laney> awe_: what's the API for getting/setting the APN information?
[17:23] <awe_> Laney, in a meeting... can I get back to you?
[17:23] <Laney> yup
[17:24] <dpm> hi cwayne_, I did the call a while ago do you mean if we have some stats about new translations that got done?
[17:25] <cwayne_> dpm, yeah, sorry that's what i meant :)
[17:27] <dpm> cwayne_, no worries, I was trying to get http://91.189.93.79:8081/stats/ to show stats for the phone (it's desktop-only right now), but it'll have to wait until at least next week
[17:27] <dpm> that should give us a good overview of the languages completed and the exact translations that need to get done
[17:51] <awe_> Laney, the APN information currently can be retrieved via the ofono DBus ConnectionManager interface
[17:51] <awe_> take a look at the script /usr/share/ofono/scripts/list-contexts for details
[17:52] <awe_> There are plans to expose the APNs via a Settings UI
[17:52] <awe_> but AFAIK, this work hasn't yet started
[17:52] <Laney> indeed, that's what I want to implement
[17:53] <Laney> can I set via this API?
[17:53] <awe_> Laney, have you discussed with Wellark?
[17:54] <awe_> Wish I'd know this, as we just had a meeting about MMS support, and how we're going to be re-working the way we provision APNs
[17:54] <Laney> nope
[17:54] <Laney> I didn't know he would be working on it
[17:54] <Laney> haven't done any work yet :-)
[17:57] <sergiusens> Laney, creating a context: /usr/share/ofono/scripts/create-internet-context
[17:58] <sergiusens> selecting is something we just talked about in the meeting with awe_ :-)
[17:58] <Laney> mmm
[17:58] <awe_> sergiusens, yes...just discussing with Laney on the other server
[18:27] <shnapper> @awe_: hi, what is the status on apn settings? I'm asking because I've got no data connection. Would love to use UT as a daily driver but without internet it doesn't make sense :-(
[18:41] <SonikkuAmerica> rsalveti: Also, will updates for flo be OTA?
[18:42] <ogra_> SonikkuAmerica, as soon as we build the official images they will
[18:42] <SonikkuAmerica> ogra_: And the official images will be labeled -armhf+flo ?
[18:43] <ogra_> the official images will be installable with phablet-flash
[18:43] <ogra_> (like all official ones)
[18:44] <rww> I followed the instructions on the mailing list to install on my Nexus 7 2013. I sideloaded the .zip file it mentions and then rebooted, but it got stuck on the google-logo-with-padlock screen. Pointers for where I went wrong?
[18:44] <ogra_> rww, did you adb shell touch /home/phablet/.display-mir ?
[18:44] <rww> ogra_: nope
[18:44] <ogra_> do that :)
[18:45] <ogra_> (and reboot)
[18:45] <rww> ah, okay. Will have a look in an hour or so when I'm reunited with it :)
[18:45] <rww> thanks
[18:46] <SonikkuAmerica> ogra_: I should've thought of that too... I didn't do that
[18:47] <ogra_> there will be armhf+flo files but you shouldnt consume them directly
[18:47] <SonikkuAmerica> ogra_: Got it. (I was referring to rsalveti 's instructions)
[18:47] <SonikkuAmerica> I didn't realize I needed to do that before I rebooted
[18:48] <ogra_> yeah, these images arent really what the official ones will look like
[18:48] <ogra_> its one step before the actual thing ...
[18:57] <awe_> shnapper, I don't have an ETA for the APN settings.  That said, if you're APN is not being automatically provisioned, filing a bug would be a good place to start
[19:00] <SonikkuAmerica> Another question: When it says to add the ppa:rsalveti/ppa, is that done on the host or the device?
[19:00] <ogra_> SonikkuAmerica, just sideload this zip http://people.canonical.com/~ogra/ubuntu-touch/ubuntu-touch-4.4.2-mir.rootfs-armhf.zip
[19:00] <ogra_> it has all bits needed already
[19:00] <SonikkuAmerica> ogra_: That has everything?
[19:00] <ogra_> yep
[19:01] <SonikkuAmerica> OK
[19:01] <SonikkuAmerica> :)
[19:01] <ogra_> touching the .display-mir file is still needed
[19:01] <ogra_> but nothing beyond that
[19:02] <shnapper> awe_: didn't mean to ask for an ETA - sorry. Just curious about the current development. How's it going?
[19:02] <SonikkuAmerica> ogra_: All right, if it works you've made my day :)
[19:03] <ogra_> using it happily here
[19:03] <shnapper> awe_: ...or maybe you're working on something different..
[19:04] <awe_> shnapper, I'm responsible for the low-level telephony stack, but need to coordinate with all of the other components
[19:04] <shnapper> awe_: okay. My android system is near perfect to my needs but I won't hesitate a minute to switch as soon as possible ;-)
[19:05] <awe_> ok
[19:05] <awe_> we're getting there...
[19:08] <shnapper> awe_: Take your time and good luck
[19:08] <awe_> thanks!
[19:20] <SonikkuAmerica> ogra_: OK, for some reason nothing is getting replaced when I sideload the image.
[19:21] <ogra_> hmm
[19:21] <ogra_> you did it from the ubuntu recovery that you fastboot flashed before ?
[19:21] <SonikkuAmerica> Oh derp that's probably the source of my problems, I'm using TWRP
[19:22] <SonikkuAmerica> (I did download the Ubuntu recovery from rsalveti's data area)
[19:22] <ogra_> right, flash it
[19:22] <ogra_> (no idea why TWRP wouldnt work though ... but i'm sure nobody tried it yet )
[19:26] <SonikkuAmerica> Well, we can now say that with the latest TWRP for flo it doesn't work to the best of our knowledge...
[19:26] <ogra_> yeah :)
[19:28] <Tassadar> SonikkuAmerica: define "doesn't work" - what does it do?
[19:29] <SonikkuAmerica> Oh, good point Tassadar - what happens is that it indicates that the ubuntu rootfs tarball is being copied and that UTouch is being deployed, it appears to complete, then I hit "Reboot system" and it loads Android at boot.
[19:29] <Tassadar> if you're flashing only that rootfs, it won't do anything - that one just creates /data/ubuntu folder
[19:30] <Tassadar> you have to flash the system ZIP too
[19:30] <SonikkuAmerica> OK...
[19:30] <ogra_> there is no system zip for the experimental images
[19:31] <SonikkuAmerica> I was about to say that...
[19:31] <Tassadar> or system.img, via fastboot
[19:31] <Tassadar> and boot.img too
[19:31] <ogra_> fastboot flash recovery, boot and system ... boot into recovery, pick "install zip from sideload" in the menu and adb sideload the rootfs zip from the url above
[19:32] <ogra_> then boot, adb touch /home/phablet/.display-mir, adb reboot and you should be golden
[19:32] <ogra_> *adb shell touch ...
[19:33] <SonikkuAmerica> Hm, if I only read the instructions...
[19:33] <Tassadar> anyway, I doubt that it's TWRP's fault, the android can't possibly boot if you flashed the boot.img
[19:42] <SonikkuAmerica> Boot, recovery and system flashed. Sideloading up...
[19:43] <SonikkuAmerica> ... complete. Now I reboot the system?
[19:45] <SonikkuAmerica> OK, it worked! I have Ubuntu Touch! :)
[19:45] <SonikkuAmerica> Thanks guys!
[19:46] <ogra_> enjoy :)
[20:01] <jibel> tvoss, hey can you look at bug 1276782 . It is not fixed with 0.0.2+14.04.20140204-0ubuntu1 it even seems to be worst than before.
[20:03] <tvoss> jibel, it's a different cause
[20:03] <tvoss> jibel, but yeah, I'm on that
[20:07] <jibel> tvoss, k, thanks
[20:10] <rww> ogra_: I must be missing something here...
 fastboot flash recovery, boot and system ... boot into recovery, pick "install zip from sideload" in the menu and adb sideload the rootfs zip from the url above
 then boot, adb shell touch /home/phablet/.display-mir, adb reboot and you should be golden
[20:11] <rww> ah, rootfs zip
[20:11] <ogra_> rww, ^^^
[20:11] <ogra_> thats essentially the process
[20:11] <ogra_> http://people.canonical.com/~ogra/ubuntu-touch/ubuntu-touch-4.4.2-mir.rootfs-armhf.zip
[20:11] <ogra_> use this rootfs zip
[20:12] <rww> yeah, I was using the one from the ML post instead. Downloading yours now :)
[20:26] <jdstrand> kgunn: chrisccoulson is seeing different bhavior on n4 and n10. on n4 eglCreateCrontext isn't creating the context and isn't setting the error
[20:26] <jdstrand> please feel free to discuss amongst yourselves :)
[20:27] <kgunn> AlbertA: kdub ^
[20:27] <kgunn> chrisccoulson: is this a specific application? or is this mir or X or ?
[20:33] <kgunn> chrisccoulson: ah, jamie filled me in...said this is oxide (chrome webkit)
[20:33] <chrisccoulson> kgunn, this is oxide. it fails to create an EGL context on the N4 for some reason (the check on line 71 of http://src.chromium.org/viewvc/chrome/trunk/src/ui/gl/gl_context_egl.cc fails)
[20:33] <chrisccoulson> with no error code
[20:36] <kgunn> chrisccoulson: ..will poke about for a moment
[20:39] <kgunn> chrisccoulson: not real familiar, but just want to ask you some really elementary questions...
[20:39] <ajalkane_> I'm trying to start-up the emulator, but I only get black screen. I get the emulator login terminal though, how could I fix or check what's wrong?
[20:39] <ajalkane_> For what it's worth, the emulator used to work
[20:39] <kgunn> chrisccoulson: so do you know for sure an egl lib is loaded under the hood ?
[20:40] <popey> ajalkane_: if you login, is unity running?
[20:40] <kgunn> e.g. you call create...but the lib might not even be there ?
[20:40] <kgunn> sorry if you've already done this part :)
[20:41] <chrisccoulson> kgunn, yes, that's done in http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/view/head:/shared/gl/gl_implementation_linux.cc#L125  and http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/view/head:/shared/ozone/oxide_ozone_surface_factory.cc#L72
[20:42] <chrisccoulson> if that fails, then we don't set the GL platform to EGL, which is what is used in http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/view/head:/shared/gl/gl_context_linux.cc#L30
[20:42] <kgunn> chrisccoulson:  so on the n10 you get a context and you see what you want rendered on the screen?
[20:43] <chrisccoulson> kgunn, we do
[20:43] <ajalkane_> popey: "ps -ef | grep unity" shows nothing, so I guess no
[20:43] <popey> ajalkane_: did you create the emulator image today?
[20:43] <popey> ajalkane_: have a look in ~/.local/share/upstart for errors?
[20:44] <chrisccoulson> kgunn, actually, i'm starting to think that the N10 is some sort of magicall fluke - we're passing an invalid display handle
[20:44] <chrisccoulson> i've just discovered ;)
[20:44] <ajalkane_> popey: nope, it's few weeks old. Should I recreate?
[20:44] <popey> ajalkane_: newer is always nicer ☻
[20:45] <kgunn> chrisccoulson: so this is oxide sitting on ozone sitting on ...Qt ?
[20:45] <chrisccoulson> kgunn, yep :)
[20:45] <kgunn> e.g. are they Qt surfaces ?
[20:45] <kgunn> ah ok
[20:45] <ajalkane_> popey: ok thanks, I'll try creating again.
[20:46] <chrisccoulson> kgunn, sooooooo, http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/view/head:/qt/core/common/oxide_qt_content_client.cc#L36 is returning 0x1 as a handle on both of my devices, which is what chromium passes to eglCreateContext
[20:47] <chrisccoulson> i'm a bit confused why this works at all on one device though
[20:49] <kgunn> chrisccoulson: that is super weird..both that a "random" handle seems to work & that you get no error in the other case
[20:49] <chrisccoulson> oh, we don't implement QPlatformNativeInterface::nativeResourceForScreen() in qtubuntu
[20:50] <chrisccoulson> so, i would definitely expect this to be broken. i'm just going to ignore the 1 device that works. we have 2 devices that don't work now
[20:51] <chrisccoulson> kgunn, so, i wouldn't spend any time thinking about this for now. i'll ping you again if it's still broken after i fix this
[20:51] <chrisccoulson> thanks :)
[20:52] <kgunn> chrisccoulson: ok...may poke anyway...feel free to spew in #ubuntu-mir
[20:52] <kgunn> they'll find it fascinating and probably get totally distracted :)
[20:55] <rww> ogra_: while sideloading that zip: "Lost connection to Vold -- did it crash?"
[20:56] <korla> hi folks! i'm trying to install to a nexus 4 from Fedora using the manual instructions at wiki.ubuntu.com/Touch/Install -- having troubles, so first of all can someone confirm that those instructions do, in fact, work?
[20:56] <ogra_> rww, vold ? that should not run in recovery at all
[20:56] <rww> ogra_: then two E: lines and it went back to the recovery menu
[20:56] <kgunn> chrisccoulson: wrt "oh, we don't implement QPlatformNativeInterface::nativeResourceForScreen() in qtubuntu" makes you wonder how anything works
[20:56] <kgunn> :)
[20:57] <ogra_> rww, are you sure you fastboot flashed the three files first ?
[20:57] <chrisccoulson> kgunn, i guess not many people use this, as it's a private class anyway. we only use it because we have to ensure the EGL contexts used by the qml scenegraph and chromium's compositor get the same display handle, in order for context sharing to work
[20:58] <rww> ogra_: yep, I guess something on the other .zip might have confused it. re-doing
[21:03] <rww> ah, this looks more promising
[21:03] <ajalkane_> popey: the .local/share/upstart should be in the phablet login right? There was no such file/directory. Same problem with black emulator screen with recreated instance
[21:06] <ogra_> ajalkane_, the logs are in .cache/upstart/
[21:06] <popey> ajalkane_: yes, unity runs as the phablet user, so in /home/phablet/.local/share is where you find all kinds of app (and unity) start logs
[21:06] <popey> oh, sorry, my bad
[21:07] <ajalkane_> phablet@ubuntu-phablet:~/.cache/upstart$ less window-stack-bridge.log
[21:07] <ajalkane_> Window Stack Bridge: Incorrect QPA environment for Ubuntu platform API
[21:07] <ajalkane_> Could that be the problem?
[21:07] <popey> I'd be looking at the most recently written logs in there
[21:07] <korla> I guess i'll assume they do, for now. Next question: after running 'adb push trusty-preinstalled-touch-armel+mako.zip /sdcard/autodeploy.zip', it says to run adb reboot recovery. It appears to install the zip, but it has been sitting on the "Google" screen for 15 minutes. Is this expected?
[21:08] <ajalkane_> All the timestamps in the various files are the same, and the log entries themself do not have timestamps
[21:09] <ajalkane> Argh... drives me crazy. Doing "less" in phablet and hitting Ctrl+C in there shuts down the emulator :P
[21:10] <popey> oof
[21:10] <popey> does adb shell not work?
[21:10] <ajalkane> popey: adb shell should be run from host or inside phablet?
[21:10] <popey> separate window
[21:11] <popey> on host
[21:11] <popey> just minimise the one that has a phablet logon prompt
[21:12] <ajalkane> popey: oooh cool... doing that got the emulator working. Doh... so user error once again.
[21:12] <popey> hehe
[21:13] <ajalkane> Emulator seems faster than the last time I remember. Good job
[21:13] <popey> yay
[21:14] <popey> we'll have an x86 version soon
[21:14] <popey> which should make this pain go away
[21:14] <ajalkane> yay, sounds great
[21:15] <ajalkane> This seems pretty usable already. I'm impressed.
[21:16] <popey> thats good to hear
[21:16] <kaimast> if you have modern hardware the emulator runs fine. on my i5 it is hardly slower than running natively on the gnexus
[21:17] <kaimast> but on my old athlon machine it was painful :D
[21:17] <ajalkane> I'm running inside VM so that brings another level of slowness
[21:18] <kaimast> a vm inside a vm. inception
[21:18] <ajalkane> yeah, one could make an action movie about this stuff
[21:19] <ajalkane> So install a new click package with pkcon install-local, do I need to restart unity in the emulator or something for it to be visible as runnable app?
[21:20] <popey> it should be visible if you search for it
[21:20] <popey> using the search at the top
[21:20] <ajalkane> popey: umm... the search doesn't seem to be accepting my keyboard input :P
[21:21] <ajalkane> And there's no touch screen keyboard opened
[21:22] <popey> oof
[21:22] <popey> it should
[21:23] <popey> the emulator can be a bit buggy, a bit like the galaxy nexus
[21:24] <ajalkane> where do the .desktop files install from click packages? I tried looking at /usr/share/applications but didn't see the desktop file there
[21:24] <popey> /home/phablet/.local/share/applications
[21:25] <popey>  /usr/share/applications is used by pre-installed clicks
[21:25] <ajalkane> popey: not there either
[21:25] <popey> odd
[21:25] <ajalkane> hmm... of course I installed as root so perhaps it went to root
[21:25] <popey> ah
[21:25] <popey> you should "sudo -u phablet -i"
[21:26] <popey> and then use pkcon
[21:26] <ajalkane> Thanks, that did it
[21:37] <ajalkane> popey: is there some application in the image that uses Content-Hub that I can test File Manager with?
[21:42] <ajalkane> I must say the Ubuntu touch UI seems really nice coming from N9. Seems really promising and something I'd like
[21:44] <popey> ajalkane: seems there's a bug in the latest image
[21:46] <charles> nik90: ping
[21:46] <ajalkane> popey: would you mind I send you the File Manager click package that *might* work for testing? Most likely it won't though.
[21:46] <nik90> charles: pong
[21:46] <popey> sure ajalkane
[21:47]  * popey updates his phone to #165 which should be working
[21:48] <ogra_> yeah, 165 looks fine here
[21:55] <ajalkane> popey: sen the mail. I'm out for today, let me know of the failures with e-mail with logs if possible
[21:55] <ajalkane> * sent
[21:57] <popey> ajalkane: will do
[22:01] <charles> nik90: as per the discussion of alarmModel's index, looks like in ubuntu-ui-toolkit that's literally a row index number, so it's just a temporary
[22:01] <charles> so there's no uid that both ubuntu-clock-app and indicator-datetime can both see, afaik
[22:01] <tedg> popey, Did we have someone down to add a URL property to alarms?
[22:01] <tedg> It seems that it's not there in the docs: http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.Alarm/
[22:02] <tedg> We need nik90 to set it in the clock app so that charles can get back to him in indicator-datetime
[22:02] <nik90> tedg: I am here as well
[22:03] <nik90> charles: yeah..shouldn't the url be generated by the alarm model to ensure that it is unique and also passed on to the EDS?
[22:04] <nik90> charles: It will result in me changing how I access a particular alarm's details but that shouldn't be an issue
[22:04] <tedg> nik90, I don't think it can do that by itself as it doesn't really know which app, and what URLs that app is registered for.
[22:04] <tedg> nik90, I think that means the app has to do it itself.
[22:05] <nik90> tedg: atm there isn't an url property exposed by the Alarms API for clock app to set.
[22:05] <nik90> tedg: but I agree
[22:06] <nik90> tedg: but I would rather prefer an approach where the app can send the appName to the Alarms API and then it generates the url
[22:07] <tedg> nik90, Yeah, I think we need to fix that :-)
[22:07] <dobey> does anyone know how to get the list of applications from /usr/share/applications with qt?
[22:07] <tedg> nik90, The URL wouldn't include any extra information like which alarm then.
[22:07] <dobey> does qt even have a way to do that? (i'm having trouble finding it if so)
[22:07] <charles> ya. the agreement was for datetime to be a simple passthrough using the uris that it pulled from EDS, and filtering for "alarm:///"
[22:07] <popey> dobey: you sure you want to get them from there? (there may also be .desktop files in ~/.local/share/applications)
[22:07] <dobey> popey: well, that was an example. i want to get them from all the xdg dirs
[22:08] <popey> k
[22:08] <dobey> popey: glib has a really nice api for doing this, but i don't see a way to do it in qt
[22:08] <nik90> tedg: but it wouldn't be difficult for the Alarms API to prepend the app name to the url. Something like "Clock-App-Alarm#10" etc..
[22:08] <dobey> which is leading me to the "i'm just going to have to use glib inside a qt app to do it"
[22:09] <nik90> tedg: one other reason why I prefer that, to maintain the same url structure across all apps that can create alarms
[22:09] <tedg> nik90, You shouldn't need to do that.  If you register for a url scheme, then that'll connect for free.  So you could register for "alarm" and then the URL could be "alarm:///10"
[22:10] <nik90> tedg: ok
[22:11] <tedg> popey, Can you find someone to add a URL property for us?
[22:11] <popey> $someone?
[22:11] <tedg> popey, SDK team
[22:11] <nik90> tedg: zsombi is the one who works on the Alarms API, however I am guessing he will want to contact renato about the implementation
[22:11] <popey> +1
[22:11] <tedg> popey, Are both those folks in beer bribing distance for you?  ;-)
[22:12] <popey> they are indeed
[22:12] <nik90> popey: since you are all in the same place, can you reach out to zsombi about this? or should I?
[22:12] <nik90> tedg: good point ;)
[22:12] <popey> nik90: can you, and I'll poke him to take notice.
[22:12] <popey> bzoltan: see above, can you please have zsombi look at this?
[22:12] <popey> (pretty please)
[22:12] <nik90> popey: alright. I will do that tomorrow morning, since I cannot find zsombi online
[22:14]  * popey goes and slaps him
[22:15] <popey> he's in a meeting, will poke after
[22:15] <nik90> ok
[22:22] <korla> thanks anyway, i guess i'll try flashing it with twrp
[22:54] <dbarth> mhall119: pong; you can remove the warning on d.u.c; the SDK is installable again on all supported releases
[23:51] <achiang> plars: ping?